Backup guide
WordPress Multisite Backup on SiteGround
Back up Multisite networks on SiteGround with chunked, resumable jobs — beyond host snapshots alone.
Free
How to back up Multisite on SiteGround
On SiteGround (shared 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. PHP max_execution_time and memory ceilings are often tight on shared plans.
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. Inode and tmp-disk limits can abort oversized archives mid-job.
What a complete Multisite backup on SiteGround 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 SiteGround creates “successful” archives that still fail a real restore drill. Exclude cache, tmp, and other regenerable noise so jobs finish faster on shared plans.
WordPress cron may be delayed unless a real system cron hits wp-cron.php. 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 SiteGround 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 SiteGround, 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 SiteGround
Before you trust a SiteGround 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 import fails on SiteGround, raise upload_max_filesize and post_max_size only as far as needed, free disk, then retry with chunked resume.
Retention, encryption, and support hygiene
For wordpress multisite backup on siteground, 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.
Separate schedule failures from restore failures in your runbook so on-call staff do not rebuild a finished archive unnecessarily.
Why this matters
Network-aware archives
Capture the whole SiteGround Multisite install — not only one blog’s tables.
Survives PHP limits
Jobs in Chunks fit typical shared constraints on SiteGround and resume after interrupts.
Offsite when you need it
Plus uploads to Drive, Dropbox, S3-compatible storage, or SFTP — your credentials, your bucket.
Restore paths that match ops
Same-server restore, import, or Pro empty-server / Staging flows after a verified archive.
Steps
-
1Install and open Network Admin
Network-activate Multisite Migrate on SiteGround. Open the backup screen from Network Admin for fleet jobs, or from a subsite when you only need one site.
-
2Choose 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.
-
3Run a chunked job
Start the job and let it resume if PHP time limits interrupt on SiteGround. Do not stack overlapping schedules that collide on locks.
-
4Store 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.
-
5Prove recovery on Staging
Import or restore once away from production. Check URLs, media, logins, and mapping before you call the SiteGround routine production-ready.
Frequently asked questions
Quick answers for this Multisite backup topic. Still stuck? Open the docs or contact support.
Are SiteGround snapshots enough for Multisite?
Snapshots are safety netting — portable Multisite plugin archives still matter for import and Staging drills.
Can a subsite admin back up only their site?
Yes. Users with manage_options on a subsite can run site-level backup/restore in Free.
Which cloud destinations work?
Native Plus targets: Google Drive, Dropbox, S3-compatible storage, and SFTP. No proprietary vault. OneDrive is not native.
What usually breaks Multisite backups on shared hosts?
Long PHP workers get killed, inodes fill up, or security plugins block AJAX. Chunked resume and log-first diagnosis are the durable pattern.