How to manage backups for multiple WordPress sites

List every site, its owner, hosting provider, database size and how often its content changes. A brochure site may need a weekly full backup, while a WooCommerce or publishing site usually needs more frequent database backups.

Keep several backup points rather than only the newest copy. Store them away from the web server, and keep at least one copy that the hosting account cannot delete. Back up before WordPress, plugin or theme updates as well as on your normal schedule. A complete backup contains both files and the database; downloading the WordPress directory alone does not include the database.

For each site, download the WordPress files with SFTP or the host’s file manager, including wp-content, the configuration file and any custom files. Then export the correct MySQL or MariaDB database from phpMyAdmin, or run wp db export if WP-CLI is available. Name both parts with the site name and date, then keep them together as one backup set.

This manual route is fine for one or two low-change sites, but it becomes easy to miss a site, overwrite a backup or forget the database. It also gives you no central schedule, failure report or one-click restore.

Send backups to storage that is separate from the hosting account, such as object storage or a supported cloud drive. Use a different folder or bucket for each site, restrict access, and enable encryption or server-side protection where available.

Set a retention rule, such as keeping daily copies for a week and weekly copies for several months. Do not assume that a successful upload means the backup is usable; retain logs and check that both the database and files were created.

Set schedules according to how often each site changes. Keep database backups more frequent for stores and membership sites, and include full files often enough to capture uploads, plugins, themes and configuration changes.

Review the backup log after the first run and after major hosting or plugin changes. Watch for timeouts, low disk space, blocked remote connections and backups that contain files but no database. Stagger large sites if simultaneous jobs overload the server.

Restore one backup to a staging site or separate test installation before you need it. Confirm that pages load, media opens, forms work, users can sign in and site-specific integrations still connect.

For a manual restore, restore the files first and then import the database. If the database credentials or domain changed, update the site configuration and handle URL replacement carefully. Keep a written record of the restore steps so a Friday-night recovery does not depend on memory.

The fast way for multiple sites is MainWP UpdraftPlus. Install and activate UpdraftPlus on each child site, connect those sites to a MainWP Dashboard, install the MainWP UpdraftPlus extension, and configure remote storage and schedules from the central interface. The extension can create and restore backups, adjust settings and manage schedules across child sites.

Start with one site, run a backup, inspect its log and perform a test restore before applying the settings to the rest. Do not assume every site should use the same schedule, storage account or retention period. Also verify the actual run times: support discussions note that exact clock-time control is not available in some MainWP and UpdraftPlus scheduling workflows.