How to Back Up a Multisite WordPress Network

Backing up a WordPress multisite network is different from backing up a single site. Standard plugins often only capture one subsite’s tables or miss network‑specific settings. One corrupted table can break every site on the network. Here’s the reliable way to back up your entire multisite.

What Makes Multisite Backups Unique

In a multisite network, the database uses shared tables for users, blogs, and site meta. Each subsite adds its own set of tables (e.g., wp_2_posts, wp_3_options). If you only export a single subsite’s tables, you lose cross‑site data and network configuration. The same goes for files—uploads are centralized in /wp-content/uploads/sites/, and themes/plugins are shared.

So a true multisite backup must include:

• Entire database: all network tables plus every subsite’s tables.
• Full file system: core, themes, plugins, uploads, .htaccess, and wp-config.php.

Skip any part and restores become impossible or partial.

Method 1: Using a Multisite‑Compatible Plugin

The easiest approach for most site owners is a backup plugin that explicitly supports multisite. You need to network‑activate it so settings and schedules apply to the whole network, not just one subsite.

UpdraftPlus (Free + Premium)

UpdraftPlus works well with multisite. Network‑activate it, then configure backup schedules and remote storage (Dropbox, Google Drive, S3, etc.). It will back up the entire network database and file system. The premium version adds incremental backups and more storage options.

Other Options

BackWPup, BlogVault, and Jetpack VaultPress Backup also handle multisite. Always check the plugin’s documentation to confirm multisite network support—some free versions only back up the main site.

Be aware of a common mistake with plugin backups: they often exclude large upload directories by default. Verify your settings include /wp-content/uploads/sites/. If you’ve made this error before, read our article on 5 Common WordPress Backup Mistakes to avoid it again.

Method 2: Manual Backup via SSH (No Plugin)

If you prefer a plugin‑free approach, manual backups give you full control. You’ll need SSH or cPanel file manager and database access.

Step 1: Back Up Files

1. SSH into your server and navigate to the web root (e.g., /var/www/html/).
2. Create a compressed archive of the entire WordPress installation:
   tar -czf multisite-backup-$(date +%F).tar.gz .
3. Download the archive to a secure off‑site location using SCP or rsync.

Step 2: Back Up the Database

Use mysqldump with the entire database (not just a single subsite):

mysqldump -u username -p databasename > multisite-db-$(date +%F).sql

If you’re unsure about the database name, check wp-config.php. Compress the SQL file and store it alongside your file archive. For more on database specifics, see our Beginner’s Guide to WordPress Database Backup.

Method 3: Automating Backups with WP‑CLI

WP‑CLI is perfect for scripting consistent multisite backups. It can export the entire database and create file archives in a single command.

Example cron‑ready script:

#!/bin/bash
# Backup multisite files
wp db export --add-drop-table --set-gtid-purged=OFF ./backups/multisite-db.sql
wp package install wp-cli/restful  # optional for custom endpoints
# Tar the whole site
tar -czf ./backups/full-multisite-$(date +%I%M%p).tar.gz .
# Upload to remote (e.g., S3 using awscli)

Run this script daily via cron. WP‑CLI’s db export dumps every table, which is exactly what multisite needs. You can also use wp search-replace during restores to adjust URLs.

Multisite Backup Best Practices

Plan for more than just taking backups. These practices keep your network safe:

• Test restores quarterly. A backup you can’t restore is worthless. Restore to a staging environment and verify every subsite works.
• Use multiple storage locations. Keep one copy on a remote cloud service and another separate location.
• Monitor backup logs. Plugins and scripts log successes and errors. Check them after each scheduled run.
• Consider incremental backups for large networks. Full daily backups of a 10 GB network strain resources. Incremental tools like rsync or UpdraftPlus premium reduce load.

Common Pitfalls in Multisite Backup

Even experienced developers miss these:

• Partial database dumps: Some tools only export the main site’s tables. Always verify you have tables for every subsite ID.
• Missing uploads per site: Not all backup tools traverse the /sites/ directory inside uploads. Double‑check.
• Ignoring network‑only plugins: Network‑activated plugins are stored globally. Losing them means all subsites malfunction.
• Overwriting a subsite’s database accidentally: When restoring, never import a single subsite’s backup directly—it could break table relationships.

If you run WooCommerce subsites, learn from our WooCommerce Backup Guide for preserving order and customer data across the network.

Comparison: Plugin vs. Manual vs. WP‑CLI

Method	Ease of Setup	Automation	Database Scope	Best For
Plugin (e.g., UpdraftPlus)	High	Built‑in scheduler	Full network	Non‑technical users
Manual via SSH	Low	Requires cron	Full network	Developers who need full control
WP‑CLI	Medium	Script‑driven cron	Full network	Automation‑first setups

When Things Go Wrong

Despite careful backups, problems happen. If a restore fails, check these first:

• Database connectivity: Ensure your wp-config.php DB credentials match the restored database.
• File permissions: After restoring from tar, file ownership and write permissions may be wrong. Run chown -R www-data:www-data and set folders to 755, files to 644.
• Domain mismatch: If you restore to a different domain, use WP‑CLI or a search‑replace plugin to update URLs across all subsites.

Running a multisite network adds complexity, but with the right backup strategy you can sleep soundly. Pick the method that fits your workflow and automate it. Then sleep on the knowledge that your entire network is safe.

Frequently asked questions

Can I use a single‑site backup plugin on a multisite network?

It’s not recommended. Most single‑site plugins only back up the main site’s tables and ignore subsites. They may also miss network‑level settings. Always use a backup plugin that explicitly supports multisite network backups, and network‑activate it.

Do I need to back up each subsite separately?

No. Back up the entire multisite database at once. The database contains all subsites in shared tables. Individual subsite backups are only useful for exporting a single site’s content, not for full disaster recovery.

How often should I back up my WordPress multisite network?

Frequency depends on update activity. Daily backups are a good minimum for most networks. If your network has heavy content changes or e‑commerce, consider hourly or real‑time backups via plugins that offer incremental backups.

What should I restore first if my multisite network crashes?

Restore the database first, then the files. The database holds the structure and content. After restoring files, verify your wp‑config.php and .htaccess are correct, then test a few subsites before putting the site live.

Does backing up multisite use more server resources than a single site?

Yes, because you’re backing up a larger database and file system. Full backups can be heavy. To reduce resource usage, schedule backups during low‑traffic hours and use incremental backups for files and database where possible.