A Multisite backup plan must cover shared network components as well as each subsite's content and media. Restoring the entire network is different from recovering one customer's site, and the backup method should support the recovery scenarios you actually need.
IN THIS ARTICLE
01 Inventory shared and site-specific data
The network shares core, installed plugins, themes and user identities. Subsites have their own content tables and settings, while plugins may store data in site tables, shared tables or external systems. Upload paths also vary between the main site and other sites, particularly on older networks. Document the actual layout rather than guessing table names from a site URL.
02 Create the backup plan
- Record every subsite, mapped domain and important integration.
- Choose a backup method that explicitly supports the installed Multisite configuration.
- Include the full database, site files, uploads, configuration and relevant server routing.
- Set frequency and retention according to how often the busiest site's important data changes.
- Keep an independent protected copy and monitor failures or storage limits.
- Rehearse both a full-network restore and the most likely individual-site recovery.
Can I restore one site's tables only?
Sometimes a carefully designed recovery can transfer selected data, but table copying alone is not a general solution. Users, network settings and plugin relationships may be shared. A plugin can also keep business data outside the obvious site tables. Identify all dependencies and test on an isolated copy before changing production.
Will a network restore overwrite other sites?
A full database restore can replace newer data across the network. If one subsite is damaged while others continue accepting orders or edits, recover the required content from an isolated backup copy instead of automatically rolling the whole network back.
03 Verify recovery conditions
Protect the restored test network and disable live mail, payments and scheduled integrations. Check several subsites with different themes and plugins, including mapped domains and uploads. Record restore duration and any manual steps needed for certificates or external services. Review the plan whenever new subsites or plugins introduce different storage requirements. A successful backup status is useful, but a documented restore rehearsal provides much stronger evidence that the network can recover.