How-to guide
Subdirectory Vs Subdomain Multisite Backup
Practical steps for subdirectory vs subdomain multisite backup with Multisite Migrate — Multisite-aware, chunked, and restore-tested.
Free
How to: Subdirectory Vs Subdomain Multisite Backup
Subdirectory Vs Subdomain Multisite Backup is a common Multisite operations need. Networks share core files and users while each site keeps its own tables and uploads/sites paths, so single-site plugins often miss network scope.
Multisite Migrate backs up full networks or individual subsites with include/exclude scope, Jobs in Chunks for shared hosting, Free local scheduling, Plus BYO cloud (Drive/Dropbox/S3-compatible/SFTP), and Pro tools for remote import, empty-server installs, Staging, network split, extract-one-site, shared-users merge, and migration verify. For “subdirectory vs subdomain multisite backup”, start in Network Admin (or the subsite dashboard when appropriate), pick the right profile, run or schedule, store offsite on Plus, then prove recovery on Staging before production pressure.
Why “Subdirectory Vs Subdomain Multisite Backup” is different on Multisite
Shared themes/plugins, network tables, and per-site media mean a “complete” backup is a network decision — not a single blog export. Host snapshots help, but they are not the same as an importable Multisite plugin archive you can verify on Staging.
When operators search for subdirectory vs subdomain multisite backup, they usually need a repeatable path: correct scope, a job that survives PHP limits, an offsite copy when Plus is available, and a restore drill that checks URLs, media, and logins.
Product path: Free, Plus, and Pro
Map “subdirectory vs subdomain multisite backup” to the right tier. Free covers core network/subsite backup and restore plus one local schedule. Plus adds BYO cloud upload and cloud schedules. Pro adds remote import, empty-server installer, Staging, WP-CLI, network split, and related migration tools.
This workflow aligns with Free where those capabilities appear. Do not invent destinations the product does not ship: native Plus targets are Google Drive, Dropbox, S3-compatible storage, and SFTP — not OneDrive and not a proprietary Multisite Migrate vault.
Operational checklist
1) Confirm role (Network Admin vs subsite manage_options). 2) Set scope and exclusions. 3) Run or schedule with chunked resume. 4) Keep a local archive; push offsite on Plus. 5) Restore once on Staging and verify HTTPS, mapping, media, and users.
If cloud upload fails after a good local archive, fix destination auth/quota and retry upload without rebuilding the whole network archive.
Retention, encryption, and support hygiene
For subdirectory vs subdomain multisite backup, 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.
Why this matters
Multisite-correct scope
Network-wide or per-subsite — not a single-site blind export.
Chunked reliability
Jobs resume instead of dying on PHP timeouts on shared hosts.
Clear tier fit
This workflow maps to the Free feature set where applicable.
Docs-linked next steps
Deep links into the official backup/restore guides for screenshots.
Steps
-
1Confirm role and scope
Network Admin for fleet jobs; subsite admin for one site. Decide whether “subdirectory vs subdomain multisite backup” needs the whole network or a subset.
-
2Configure the job
Set options that match subdirectory vs subdomain multisite backup — schedule, cloud destination, encryption, or split — without packing unrelated noise into the archive.
-
3Run or schedule with chunks
Watch progress. Allow Jobs in Chunks to resume on large networks instead of restarting from 0% after a PHP kill.
-
4Store a recoverable copy
Keep local retention. On Plus, confirm the Drive/Dropbox/S3-compatible/SFTP object exists and is readable.
-
5Verify recovery
Import or restore on Staging. Check URLs, media, logins, and critical plugins before DNS or production cutover.
Frequently asked questions
Quick answers for this Multisite backup topic. Still stuck? Open the docs or contact support.
Does Free cover subdirectory vs subdomain multisite backup?
Local Multisite backup and one schedule stay Free. Cloud upload/schedules need Plus; remote import and Staging need Pro.
Is this only for Multisite?
It works on single-site too — this page highlights Multisite scope, shared users, and sites/ uploads.
Where are official docs?
Official backup/restore documentation is linked on this page — start there for step screenshots.
What should I verify after restore?
Mapping, media, logins, and critical plugin data. A backup is only proven after a Staging restore drill.