Backup guide
WordPress Multisite Backup on AlmaLinux VPS
How to back up and restore a WordPress Multisite network on AlmaLinux VPS: what the archive must contain, how to stay within the host's PHP limits, and how to test a restore.
How to back up Multisite on AlmaLinux VPS
On AlmaLinux VPS (vps 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. You control PHP-FPM and Nginx/Apache timeouts — raise them, then still use chunked jobs.
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. Object storage or SFTP offsite pairs well with local schedules.
What a complete Multisite backup on AlmaLinux VPS must include
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 AlmaLinux VPS creates “successful” archives that still fail a real restore drill. Exclude cache, tmp, and other regenerable noise so jobs finish faster on vps plans.
Disk I/O spikes during full network archives; schedule off-peak windows. 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 AlmaLinux VPS control panel.
How Multisite Migrate runs jobs on this host class
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 AlmaLinux VPS, 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.
Restore drill checklist for AlmaLinux VPS
Before you trust a AlmaLinux VPS 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 AlmaLinux VPS, fix destination auth/quota and re-upload — or restore from the local copy.
Steps
- Install and open Network Admin
Network-activate Multisite Migrate on AlmaLinux VPS. Open the backup screen from Network Admin for fleet jobs, or from a subsite when you only need one site. - Choose Multisite-correct scope
Select full network or include/exclude subsites. Exclude cache/tmp noise. Confirm you need shared users and sites/ media — not a single-site blind export. - Run a chunked job
Start the job and let it resume if PHP time limits interrupt on AlmaLinux VPS. Do not stack overlapping schedules that collide on locks. - Store offsite when Plus is available
Keep a local copy. On Plus, push to Google Drive, Dropbox, S3-compatible storage, or SFTP and verify the remote object exists. - Prove recovery on Staging
Import or restore once away from production. Check URLs, media, logins, and mapping before you call the AlmaLinux VPS routine production-ready.
Frequently asked questions
Are AlmaLinux VPS snapshots enough for Multisite?
They help as an extra layer, but they are not a Multisite-scoped restore workflow. Keep plugin archives you can import and verify.
Can a subsite admin back up only their site?
Yes — manage_options on the subsite unlocks site-level backup/restore in Free.
Which cloud destinations work?
Plus supports Google Drive, Dropbox, S3-compatible endpoints, and SFTP — not a proprietary Multisite Migrate vault.
What usually breaks Multisite backups on vps hosts?
PHP timeouts, low memory, full tmp/disk, blocked admin-ajax, and cloud auth/quota failures. Jobs in Chunks plus a clear job log fix most of these.
Sources
Related guides and comparisons
Make your first restorable network backup for free.