How to Back Up a WordPress Multisite Network

admin

3 hours ago

How to Back Up a WordPress Multisite Network backup tutorial showing files database offsite storage and restore verification

How to Back Up a WordPress Multisite Network is for network admins, schools, agencies, franchise sites, and organizations running several sites from one WordPress install. Use this method when protecting a network where one database and shared files can affect many subsites.

A good WordPress backup includes the website files and the database. The files carry themes, plugins, uploads, configuration, and custom code. The database carries posts, pages, users, settings, WooCommerce orders, booking records, form entries, menus, and plugin data. Before you change WordPress core, PHP, DNS, plugins, themes, checkout, or a page builder, make sure you know which backup contains both halves.

When this backup method makes sense

WordPress multisite backup workflow is a good fit when you already have that tool available and need a practical restore path. It is especially useful before updates, redesign work, hosting migrations, malware cleanup, PHP changes, database work, and plugin troubleshooting.

Before you begin

Confirm the WordPress URL and document root so you back up the right site.
Find the database name in wp-config.php or the hosting panel.
Check free disk space; many backup failures start with a full account.
Pause risky work until the backup finishes and you can see the file.
For stores and booking sites, note the last order, booking, or form entry before the backup.

Backup steps

Confirm whether the network uses subdomains, subdirectories, domain mapping, or a custom structure.
Back up the whole WordPress database, including network tables and subsite tables.
Back up wp-content/uploads/sites, plugins, themes, mu-plugins, and configuration files.
Record network settings, mapped domains, DNS, SSL, and sunrise/domain-mapping requirements if used.
Choose a plugin or host backup path that explicitly supports multisite recovery.
Test restoring to staging before assuming a single subsite can be cleanly extracted.

Automated backups and cron

Multisite backup schedules should account for the busiest subsite, not the quietest one. A network restore can affect many teams at once.

For WordPress plugin backups, remember that WordPress scheduled tasks often depend on WP-Cron. WP-Cron runs when WordPress receives traffic and notices a task is due. That is fine for many small sites, but low-traffic sites can run late. For business-critical sites, pair plugin schedules with a real server cron, hosting-panel backups, or provider backups where available.

How to test restore readiness

Restoring a multisite network is different from restoring a single site. Plan whether you are restoring the whole network, one subsite, or a file/database subset.

Do not test your only restore for the first time during an outage. Use a staging copy, temporary subdomain, local development environment, or provider restore preview when available. After restore, check login, home page, important pages, media, forms, checkout, email delivery, permalinks, and cache behavior.

Common mistakes

Using a single-site-only backup tool on a multisite network.
Forgetting uploads/sites data.
Breaking mapped domains after restore.
Rolling back every subsite to fix one subsite.

Where to store the backup

Keep at least one copy outside the web server. Good destinations include your own Google Drive, Dropbox, OneDrive, S3-compatible storage, Backblaze B2, Wasabi, SFTP, a provider backup vault, or a secure internal backup server. The exact tool matters less than the restore test, retention policy, and separation from the production account.

Fix I.T. Phill recommendation

Use WordPress multisite backup workflow as one layer, not the whole plan. Keep a second backup path for important sites, especially WooCommerce, bookings, memberships, and agency-managed sites. Before major updates, take a fresh manual backup even if automatic backups are already scheduled.