Backup guide
WordPress Multisite Backup on ScalaHosting
Back up Multisite networks on ScalaHosting with chunked, resumable jobs — beyond host snapshots alone.
Free
How to back up Multisite on ScalaHosting
On ScalaHosting (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 ScalaHosting 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 ScalaHosting 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 ScalaHosting 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 ScalaHosting, 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 ScalaHosting
Before you trust a ScalaHosting 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 a job restarts at 0% on ScalaHosting, check locks, tmp cleanup, and whether a new job ID was created before re-running.
Retention, encryption, and support hygiene
For wordpress multisite backup on scalahosting, 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.
When opening a support ticket, include the last job log lines, hosting class, PHP limits, free disk, and whether a local archive already exists.
Why this matters
Network-aware archives
Capture the whole ScalaHosting Multisite install — not only one blog’s tables.
Survives PHP limits
Jobs in Chunks fit typical shared constraints on ScalaHosting 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 ScalaHosting. 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 ScalaHosting. 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 ScalaHosting routine production-ready.
Frequently asked questions
Quick answers for this Multisite backup topic. Still stuck? Open the docs or contact support.
Are ScalaHosting snapshots enough for Multisite?
Useful on ScalaHosting, but snapshots are not a Multisite-aware restore drill. Keep importable plugin archives.
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.