Skip to content

Backup guide

WordPress Multisite Backup on A2 Managed WordPress

How to back up and restore a WordPress Multisite network on A2 Managed WordPress: what the archive must contain, how to stay within the host's PHP limits, and how to test a restore.

Multisite Migrate team4 min readChecked against the plugin docs

How to back up Multisite on A2 Managed WordPress

On A2 Managed WordPress (managed hosting), a WordPress Multisite backup is more than copying wp-content. You need shared core files, network tables, per-site tables, and uploads under sites/ — or restore will miss users, settings, or media. Managed platforms optimize front-end caching; long backup AJAX runs still need chunking.

Multisite Migrate runs chunked, resumable jobs from Network Admin (full network) or from a subsite dashboard when the role has manage_options. Free covers core network/subsite backup and restore plus one local schedule. Plus adds BYO cloud upload (Google Drive, Dropbox, S3-compatible, SFTP) and cloud schedules. Pro adds remote import, empty-server installer, Staging, WP-CLI, and network split. Provider snapshots help, but they are not a Multisite-aware restore drill.

What a complete Multisite backup on A2 Managed WordPress must include

Capture the network tables (wp_blogs, wp_site, wp_sitemeta, and related), each subsite’s tables, shared themes/plugins, and the sites/ upload tree. Skipping any of those on A2 Managed WordPress creates “successful” archives that still fail a real restore drill. Exclude cache, tmp, and other regenerable noise so jobs finish faster on managed plans.

Staging tooling varies — plugin-level archives remain useful for portable recovery. Treat provider snapshots as an extra layer — not a Multisite-scoped import workflow. Keep a plugin archive you can move, import, and verify independently of the A2 Managed WordPress control panel.

How Multisite Migrate runs jobs on this host class

Shared and managed hosts often kill long PHP workers. Multisite Migrate therefore uses Jobs in Chunks that resume instead of restarting from zero after a timeout. On A2 Managed WordPress, start from Network Admin for fleet backups, or from a single site when a subsite admin only needs their site. Watch the job log for the last completed chunk, disk/inode warnings, and cloud auth errors on Plus.

For schedules: Free keeps one local schedule; Plus can push finished archives to Drive, Dropbox, S3-compatible storage, or SFTP. Wasabi, Backblaze B2, Cloudflare R2, DigitalOcean Spaces, and MinIO are S3-compatible endpoints — not separate proprietary vaults. OneDrive is not a native destination.

Restore drill checklist for A2 Managed WordPress

Before you trust a A2 Managed WordPress backup routine, restore once on Staging (or a throwaway site): check siteurl/home, HTTPS, domain mapping (sunrise.php if used), media under sites/, logins, and any WooCommerce or membership data. Confirm rewrite rules and purge CDN/object-cache drop-ins if the front end still shows stale content.

If import fails on A2 Managed WordPress, raise upload_max_filesize and post_max_size only as far as needed, free disk, then retry with chunked resume.

Steps

  1. Install and open Network Admin
    Network-activate Multisite Migrate on A2 Managed WordPress. Open the backup screen from Network Admin for fleet jobs, or from a subsite when you only need one site.
  2. Choose Multisite-correct scope
    Select full network or include/exclude subsites. Exclude cache/tmp noise. Confirm you need shared users and sites/ media — not a single-site blind export.
  3. Run a chunked job
    Start the job and let it resume if PHP time limits interrupt on A2 Managed WordPress. Do not stack overlapping schedules that collide on locks.
  4. Store offsite when Plus is available
    Keep a local copy. On Plus, push to Google Drive, Dropbox, S3-compatible storage, or SFTP and verify the remote object exists.
  5. Prove recovery on Staging
    Import or restore once away from production. Check URLs, media, logins, and mapping before you call the A2 Managed WordPress routine production-ready.

Frequently asked questions

Are A2 Managed WordPress snapshots enough for Multisite?

They help as an extra layer, but they are not a Multisite-scoped restore workflow. Keep plugin archives you can import and verify.

Can a subsite admin back up only their site?

Yes. Subsite admins with manage_options can back up and restore their own site without Network Admin.

Which cloud destinations work?

Use Drive, Dropbox, S3-compatible, or SFTP on Plus. Wasabi/B2/R2/Spaces/MinIO go through S3-compatible endpoints.

What usually breaks Multisite backups on managed hosts?

Interrupted PHP, disk pressure, and destination auth. Raise safe limits, free space, fix credentials, then resume the chunked job.

Sources

  1. Backup guideMultisite Migrate · checked November 9, 2026
  2. WordPress Multisite / NetworkWordPress Developer Resources · checked November 9, 2026

Make your first restorable network backup for free.

14-day money-back on Plus & Pro · Read the backup guide →