Backup WordPress Multisite su WPMU DEV Hosting

Come fare backup Multisite su WPMU DEV Hosting

On WPMU DEV Hosting (managed hosting), a WordPress Multisite backup is more than copying wp-content. You need shared core files, network tables, per-site tables, and uploads under sites/ — or restore will miss users, settings, or media. Managed platforms optimize front-end caching; long backup AJAX runs still need chunking.

Multisite Migrate runs chunked, resumable jobs from Network Admin (full network) or from a subsite dashboard when the role has manage_options. Free covers core network/subsite backup and restore plus one local schedule. Plus adds BYO cloud upload (Google Drive, Dropbox, S3-compatible, SFTP) and cloud schedules. Pro adds remote import, empty-server installer, Staging, WP-CLI, and network split. Provider snapshots help, but they are not a Multisite-aware restore drill.

Cosa deve includere un backup Multisite completo su WPMU DEV Hosting

Capture the network tables (wp_blogs, wp_site, wp_sitemeta, and related), each subsite’s tables, shared themes/plugins, and the sites/ upload tree. Skipping any of those on WPMU DEV Hosting creates “successful” archives that still fail a real restore drill. Exclude cache, tmp, and other regenerable noise so jobs finish faster on managed plans.

Staging tooling varies — plugin-level archives remain useful for portable recovery. Treat provider snapshots as an extra layer — not a Multisite-scoped import workflow. Keep a plugin archive you can move, import, and verify independently of the WPMU DEV Hosting control panel.

Come Multisite Migrate esegue i job su questa classe di host

Shared and managed hosts often kill long PHP workers. Multisite Migrate therefore uses Jobs in Chunks that resume instead of restarting from zero after a timeout. On WPMU DEV Hosting, start from Network Admin for fleet backups, or from a single site when a subsite admin only needs their site. Watch the job log for the last completed chunk, disk/inode warnings, and cloud auth errors on Plus.

For schedules: Free keeps one local schedule; Plus can push finished archives to Drive, Dropbox, S3-compatible storage, or SFTP. Wasabi, Backblaze B2, Cloudflare R2, DigitalOcean Spaces, and MinIO are S3-compatible endpoints — not separate proprietary vaults. OneDrive is not a native destination.

Checklist drill di restore per WPMU DEV Hosting

Before you trust a WPMU DEV Hosting backup routine, restore once on Staging (or a throwaway site): check siteurl/home, HTTPS, domain mapping (sunrise.php if used), media under sites/, logins, and any WooCommerce or membership data. Confirm rewrite rules and purge CDN/object-cache drop-ins if the front end still shows stale content.

If cloud upload fails but the local archive exists on WPMU DEV Hosting, fix destination auth/quota and re-upload — or restore from the local copy.

Retention, cifratura e igiene support

For wordpress multisite backup on wpmu dev hosting, keep enough archive generations to roll back a bad deploy or failed migration. Optional .venc AES-256 encryption on Multisite Migrate archives protects copies at rest when you store offsite on Plus destinations. Document credentials, schedule windows, and who may run Network Admin jobs.

Do not delete the last known-good archive until the new Staging restore drill passes and production looks correct for a full business day.