We configure backup and restore specifically for a multisite network, which needs a genuinely different approach than a single-site backup — since the shared database tables mean restoring one subsite in isolation isn’t as simple as restoring a standalone site’s own, self-contained database.
Multisite backup & restore configuration
Backup and restore configured for multisite's actual shared structure, tested with a real restoration.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- Access to your network admin dashboard and hosting
- Confirmation of your backup destination preference
- Confirmation of whether you need whole-network restore capability, per-subsite restore, or both
This or something else?
| You want backup and restore configured specifically for your multisite network’s shared structure | This fix covers it |
| You want a standard, single-site backup system, not multisite-specific configuration | Backup system setup & schedule configuration, in the Backups, Staging & Migration Ops category |
| You need an actual restoration performed right now, not the system configured | Worth describing your urgent situation directly, since that’s a different, time-sensitive need |
| You want one subsite restored in isolation from a network backup | We’d confirm this is technically feasible for your specific backup approach, since it’s more complex than a standalone site’s restore |
What we do
- Confirm your backup and restore requirements for the network (whole-network, per-subsite, or both)
- Configure a backup solution built for multisite’s shared database structure
- Set an appropriate schedule and destination
- Test a restoration in an isolated environment to confirm it actually works for your network’s structure
- Verify per-subsite restoration capability if that’s part of your requirement
- Document the configuration and restoration process for future reference
What is included
- Backup configured appropriately for your multisite network’s structure
- A tested, verified restoration process
- Per-subsite restoration capability configured, if required
- Written documentation of the configuration and restoration process
Not included
- Standard, single-site backup configuration, a different, simpler scope
- Performing an actual restoration right now, if that’s an urgent, separate need
- Ongoing backup verification as a standing service — a separate, related fix if you want that automated
- Extracting a subsite to standalone as part of a restoration process, a separate, larger undertaking
Questions about this fix
Why can't I just use a standard WordPress backup plugin for my network?
Many standard backup plugins aren't built with multisite's shared table structure in mind, which can mean an backup that looks complete but doesn't actually restore correctly for a network — this fix specifically confirms your solution handles that shared structure properly.
Can I restore just one subsite without affecting the rest of the network?
This depends on your specific backup approach and multisite's own constraints — we'd confirm what's genuinely feasible for your setup and configure for it if per-subsite restoration is something you need.
How do I know the backup will actually work if I never test it?
We test an actual restoration in an isolated environment as part of this fix specifically to confirm it works, rather than assuming a backup that completes successfully is automatically the same as one that restores correctly.
Is whole-network restore more reliable than trying to restore just one subsite?
Generally yes, since it doesn't require untangling shared and subsite-specific data — if your primary need is disaster recovery for the whole network, that's often the more straightforward and reliable capability to prioritise.
Should I also get ongoing backup verification set up?
That's a separate, related, ongoing fix worth considering, since a backup that worked once isn't automatically guaranteed to keep working as your network and its content continue to grow and change.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.