> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mainwp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# MainWP Built-In Backups

> Back up and restore Child Sites directly from MainWP Dashboard. Configure schedules, incremental backups, storage destinations, encryption, and retention.

MainWP Built-In Backups lets you back up and restore Child Sites directly from MainWP Dashboard, without a backup add-on or third-party backup plugin.

[MainWP Built-In Backups - Video Tutorial](https://www.youtube.com/embed/AOY72CdvfL4)

MainWP Child creates the backup archive. Your MainWP Dashboard downloads it, stores it locally, and uploads copies to the selected storage destinations. Backups do not upload directly from the Child Site to cloud storage.

> [!NOTE]
>
> MainWP Built-In Backups is available in MainWP 6.4 and later. Keep MainWP Dashboard and MainWP Child updated, and test backups and restores on a staging site.

To manage your hosting provider's backups, use [API Backups](https://docs.mainwp.com/sites/backups/api-backups.md). For third-party backup plugins, see [Backup Add-ons](https://docs.mainwp.com/add-ons/backups.md).

## What You'll Learn

* Create your first backup and confirm where it is stored
* Schedule full, database, files-only, and incremental backups
* Connect storage destinations and protect backups with encryption
* Restore a site and roll back using a safety backup
* Manage retention and investigate failed jobs

## Prerequisites

* MainWP Dashboard 6.4 running PHP 8.3 or higher
* The matching MainWP Child 6.4 release or later, running PHP 7.4 or higher
* A connected Child Site that syncs successfully
* An administrator account to enable and configure backup settings
* A private backup directory on the Dashboard server, writable by its PHP process and outside publicly served folders. See [Set Up the Private Backup Directory](#set-up-the-private-backup-directory).
* Enough free disk space on the Child Site and Dashboard for backup and restore files
* Working WordPress cron on the Dashboard for schedules and background tasks
* Storage credentials if you want copies outside the Dashboard

For the full list of what MainWP checks on each machine, see [What a Site Needs Before a Backup Can Run](#what-a-site-needs-before-a-backup-can-run).

Keep a separate backup of your MainWP Dashboard installation, including its database and backup encryption keys.

## Find the Backup Screens

Open **MainWP > Sites > Backups** after enabling built-in backups.

| Screen | Use it for | Relative URL |
| - | - | - |
| MainWP menu (three lines, top right) > MainWP Settings > Backup Settings | Enable built-in backups, encryption, diagnostics, and on-demand retention | `/wp-admin/admin.php?page=BackupSettings` |
| Backups > Manage Backups | View schedules, run tasks, and inspect errors | `/wp-admin/admin.php?page=ManageBackups` |
| Backups > Add New | Create a scheduled backup task | `/wp-admin/admin.php?page=ManageBackupsAddNew` |
| Backups > Storage | Connect and test storage destinations | `/wp-admin/admin.php?page=ManageBackupsStorage` |
| Backups > Snapshots & Restore | Create an on-demand backup, download, restore, or clean up snapshots | `/wp-admin/admin.php?page=ManageBackupsSnapshots` |

A **task** defines what to back up, which sites to include, and when to run. A **snapshot** is a backup of one site at a particular time. One task can create snapshots for several sites.

## Create Your First Backup

**1. Enable built-in backups**

Open **MainWP menu (three lines, top right) > MainWP Settings > Backup Settings** (`/wp-admin/admin.php?page=BackupSettings`).

If **Select primary backup system** is shown, select **Built-In Backups**. Turn on **Enable Built-In Backups** and click **Save Settings**.

**2. Choose where to store the backup**

The backup stays on your Dashboard server unless you add another destination.

For an additional copy, open **Backups > Storage**, add and test a destination, and select **Use as default destination**. See [Configure Storage](#configure-storage).

**3. Select the site and start the backup**

Open **Backups > Snapshots & Restore** (`/wp-admin/admin.php?page=ManageBackupsSnapshots`) and select your test site.

Read the destination message, then click **Back Up Now**. This creates a full backup. To run a different backup type, create a task and use **Run Now** instead.

![Snapshots & Restore in dark mode, with the selected site, backup destinations, Back Up Now button, and existing snapshots.](https://mintcdn.com/mainwp/Ep7JpkcO6W0zb6qi/images/sites/built-in-backups/snapshots-and-restore.jpg?fit=max\&auto=format\&n=Ep7JpkcO6W0zb6qi\&q=85\&s=ac8e7f98e9e73610db5e96b4c8c3f396)

**4. Confirm the result**

Wait for the backup to finish and confirm that a new snapshot appears with the expected date, type, and size. Review any **files not backed up** warning before relying on the backup.

If you selected remote storage, wait for the upload to finish. See [Check Backup Status](#check-backup-status).

> [!NOTE]
>
> **Back Up Now** uses the destinations selected on the site's scheduled tasks. If those tasks have no destinations, the backup stays on the Dashboard. The default destination applies only to sites without a scheduled task.

## Set Up the Private Backup Directory

MainWP Dashboard needs a private directory on its own server to store downloaded backups and working files, even when you use remote storage. This is separate from the temporary backup files MainWP Child creates on each Child Site.

MainWP attempts to create the directory automatically. If you see **Private backup directory is unavailable**, configure a writable private location on the **Dashboard server**:

1. Create a directory outside the Dashboard's WordPress and `wp-content` directories, in a location that no website serves over the web. Make it writable by the PHP process running your Dashboard.
2. Back up your Dashboard's `wp-config.php`, then add or update `MAINWP_BACKUP_PRIVATE_DIR` before the line that loads `wp-settings.php`:

   ```php theme={null}
   define( 'MAINWP_BACKUP_PRIVATE_DIR', '/absolute/path/to/private/mainwp-backups' );
   ```

   Replace the example path with the directory's actual absolute path on your Dashboard server. On Windows, MainWP Dashboard 6.4.2 and later accepts drive-letter paths such as `D:/private/mainwp-backups`. Edit `wp-config.php` on the Dashboard server.
3. Retry the backup and confirm that it completes and appears under **Backups > Snapshots & Restore** (`/wp-admin/admin.php?page=ManageBackupsSnapshots`).

A folder outside one WordPress installation may still be publicly served by another website. This matters when the Dashboard is in a subdirectory, on an addon domain, or inside another site's folder. Choose a location outside every website's public folders.

> [!WARNING]
>
> **Confirm your private backup directory**
>
> If you see this notice in **MainWP menu (three lines, top right) > MainWP Settings > Backup Settings**, MainWP could not verify that the Dashboard's backup directory is private. Backups that use this directory stop before writing files. This includes existing scheduled backups.
>
> Ask your host to verify that no domain or web server alias serves the directory shown. Once your host confirms it is private, click **Confirm private directory** and retry the backup. You only need to confirm that directory once. If your host cannot verify that it is private, set up a different private directory using the steps above.

If backups already exist and you change this setting, move the existing `sites/` folder into the new private backup directory so older backups remain visible and included in retention. See [Preserve Built-In Backup Files](https://docs.mainwp.com/advanced/how-to-migrate-the-mainwp-dashboard.md#preserve-built-in-backup-files).

## What a Site Needs Before a Backup Can Run

A backup uses two machines. MainWP Child builds the backup on the Child Site. Your Dashboard then downloads it, keeps it on the Dashboard server, and copies it to any storage destinations you add.

In MainWP Dashboard 6.4.2 and later, this list also appears under **Back Up Now** on **Snapshots & Restore** and on **Backups > Add New**. Click **What a site needs before a backup can run** to open it.

**On the Child Site:**

* [ ] MainWP Child is a version that supports Built-In Backups. If it is too old, the backup stops and asks you to update MainWP Child and sync the site.
* [ ] The site is connected to the Dashboard. Disconnected and suspended sites cannot be backed up.
* [ ] The web server can write to the MainWP backup folder in the site's uploads folder, usually `wp-content/uploads`. MainWP Child keeps its working files there.
* [ ] The disk has room for the backup plus a reserve: a tenth of the disk, at least 100 MB and at most 1 GB. The Dashboard also will not start a backup when the site reports less than 50 MB free. Some hosts turn off the PHP functions that report disk space; MainWP then skips this check.
* [ ] For file backups, the `wp-content` and uploads folders are inside the WordPress folder. Hosts that move them, such as Pressable, WordPress.com, and Bedrock installs, can run database backups but not file backups yet.
* [ ] For backups that include the database, the site uses one database server. Sites that spread the database across several servers with a `db.php` drop-in, such as HyperDB or LudicrousDB, can only run a **Files Only Backup**.

**On the Dashboard server:**

* [ ] PHP has the cURL and OpenSSL extensions.
* [ ] The Dashboard has a private folder that the web server can write to and no website serves. By default, it creates a `mainwp-private` folder beside the WordPress folder. On hosts that provide a `private_html` or `private` folder, it can use that instead. If none of these work, see [Set Up the Private Backup Directory](#set-up-the-private-backup-directory).
* [ ] The disk has room for the backups the Dashboard downloads.

## Configure Storage

Completed backups are stored in the Dashboard's private backup directory, organized by Child Site. Storage destinations receive copies uploaded by the Dashboard. A **Local Path** destination also refers to a path on the Dashboard server. Keep enough free space on both the Dashboard and Child Site to create and process backups, even when using [Remove local archives after upload](#retention-and-cleanup).

When moving the Dashboard, [include its private backup directory in the transfer](https://docs.mainwp.com/advanced/how-to-migrate-the-mainwp-dashboard.md#preserve-built-in-backup-files).

**1. Add a destination**

Open **Backups > Storage** (`/wp-admin/admin.php?page=ManageBackupsStorage`) and click **Add Storage Destination**. Enter a descriptive **Destination name**, then choose a **Provider**.

**2. Enter the provider details**

Enter the details listed below for your provider. The account needs permission to upload, read, and delete backup files at that destination.

![Add Storage Destination form with S3 Compatible Storage selected and example destination and bucket names.](https://mintcdn.com/mainwp/Ep7JpkcO6W0zb6qi/images/sites/built-in-backups/storage-destination.jpg?fit=max\&auto=format\&n=Ep7JpkcO6W0zb6qi\&q=85\&s=483833af08bbb2516ef1a66808d23128)

**3. Test and save**

Click **Test Connection & Save**. Resolve any connection error before assigning the destination to a backup task.

For Dropbox, use **Connect Dropbox** to approve the connection. A successful connection tests and saves the destination. For pCloud, [authorize the account](https://docs.mainwp.com/sites/backups/connect-pcloud.md) before saving.

**4. Assign the destination**

On each backup task, select one or more destinations under **Upload to storage**.

Choose **Use as default destination** or **Make Default** to preselect a destination for new tasks. Update existing tasks separately if you want them to use it.

| Provider | Details to enter |
| - | - |
| S3 Compatible Storage | Bucket, Region, Access key, and Secret key. Leave Endpoint empty for Amazon S3; enter your service's endpoint for other S3-compatible storage. Enable [Path style addressing](#s3-bucket-names-with-dots) when your service requires it. |
| Google Cloud Storage | Bucket, HMAC access key, and HMAC secret from your storage interoperability settings. |
| Dropbox | App key, App secret, and an optional Folder. Register the exact Redirect URI shown in MainWP in your Dropbox app, then use Connect Dropbox. The app needs `files.content.write`, `files.content.read`, and `files.metadata.read` permissions. |
| pCloud | Optional Folder and a one-time authorization code. See [Connect pCloud](https://docs.mainwp.com/sites/backups/connect-pcloud.md). |
| SFTP | Host, Port, Username, and an existing absolute Directory path. Use a Password or a PEM Private key. When a private key is supplied, Password is its passphrase. |
| Local Path | An absolute Directory path on the Dashboard server, such as a mounted storage directory. It must be writable by the Dashboard. |

For SFTP, you can supply the server's **Host key fingerprint** to verify its identity. If left empty, the first key received is trusted and pinned. Obtain the fingerprint from your server administrator when possible.

**Local Path** does not count as offsite storage, even on a mounted drive, and cannot satisfy **Require an offsite-verified backup**.

Set **Minimum retention (days)** on a destination to protect its copies from automatic cleanup for a minimum period. The default is zero, which disables this protection. See [Minimum Retention at a Destination](#minimum-retention-at-a-destination).

### S3 Bucket Names with Dots

By default, MainWP places the bucket name before the storage endpoint in the request hostname. If the bucket name contains a dot, such as `example.com`, HTTPS requests can fail with an SSL certificate hostname mismatch.

For Amazon S3 or Wasabi buckets containing dots, enable **Path style addressing**. This places the bucket name in the URL path instead. Other S3-compatible services may have different addressing requirements; follow your provider's guidance.

Open **Backups > Storage** (`/wp-admin/admin.php?page=ManageBackupsStorage`) and configure the destination. In MainWP Dashboard 6.4.1 and later, MainWP enables **Path style addressing** by default for new destinations with dotted bucket names on recognized Amazon S3 and Wasabi HTTPS endpoints. Existing destinations keep their saved setting. Verify **Path style addressing** is enabled, then click **Test Connection & Save**.

For example, use these settings for a Wasabi bucket in `eu-central-1`:

| Field | Example |
| - | - |
| Endpoint | `https://s3.eu-central-1.wasabisys.com` |
| Region | `eu-central-1` |
| Bucket | `example.com` |
| Path style addressing | Enabled |

The **Endpoint** must match the bucket's region. Enter the bucket name in the separate **Bucket** field; do not include it in the endpoint. Check [Wasabi's regional service URLs](https://docs.wasabi.com/docs/service-urls-for-wasabis-storage-regions) for your bucket's region.

For background, see [Amazon S3's dotted-bucket certificate limitation](https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html) and [Wasabi's path-style recommendation](https://docs.wasabi.com/apidocs/rest-api-introduction).

### Share a Bucket Between Sites

You can use one private Amazon S3 or Backblaze B2 bucket for multiple Child Sites connected to the same MainWP Dashboard. For B2, select **S3 Compatible Storage** and enter the bucket's S3-compatible endpoint.

MainWP stores each site's snapshots under separate paths in the bucket. The Dashboard uploads the backups and keeps the storage credentials; it does not send those credentials to Child Sites. Sharing a destination does not give a Child Site permission to browse or download another site's backups.

For eligible restores of unencrypted backups, the Dashboard can send the Child Site temporary download links for the required backup files. These links expire after one hour and grant access only to the specified files. Encrypted backups are downloaded and decrypted on the Dashboard before being transferred to the Child Site.

Keep the bucket private and do not share its credentials with Child Sites. Separate paths organize the backups but do not create independent storage permissions. Anyone with bucket-wide access can access the backups, and anyone with a temporary download link can use it while it remains valid.

### Understand the Cloud Backup Layout

In MainWP Dashboard 6.4.2 and later, new remote backup folders include the site ID and a version of the site name, followed by the snapshot ID. For example, `12-client-site/34/` contains snapshot 34 for Child Site 12. Existing backups keep their original paths, such as `12/34/`. Renaming a site does not rename its existing backup folders.

Inside a snapshot folder, you may see:

| Item | Purpose |
| - | - |
| `chunks/` | Backup data split into hashed `.bin` files. The default chunk size is 4 MiB, approximately 4.2 MB. |
| `files/` | Small backup files uploaded whole instead of split into chunks. |
| `manifest.json` | Archive names, site and snapshot details, and the information needed to reconstruct the backup from its chunks. |

Splitting larger archives into chunks lets interrupted uploads resume. A large backup can produce many chunk files; seeing `.bin` files instead of a ZIP or Tar GZip archive is expected. The **Backup file name** tokens do not change these cloud folder paths or hashed chunk names.

Use [Snapshots & Restore](#restore-a-backup) to find backups by site and date and restore a completed remote copy. For a downloadable archive, see [Download a Backup](#download-a-backup).

### Encrypt Backup Archives

Open **MainWP menu (three lines, top right) > MainWP Settings > Backup Settings** (`/wp-admin/admin.php?page=BackupSettings`):

1. Turn on **Encrypt backup archives** to show the **Backup recovery passphrase** fields.
2. Set a recovery passphrase. The first setup also asks for your WordPress password. Use at least 12 characters; a long, unique passphrase of 20 characters or more is recommended. Store it separately from the Dashboard.
3. Click **Save Settings** and confirm that encryption remains enabled.

![Backup Settings with archive encryption enabled and fields for the current and new recovery passphrases.](https://mintcdn.com/mainwp/Ep7JpkcO6W0zb6qi/images/sites/built-in-backups/backup-encryption.jpg?fit=max\&auto=format\&n=Ep7JpkcO6W0zb6qi\&q=85\&s=89c0568b037f61525e85e50b25072861)

MainWP encrypts new archives before uploading them. Existing snapshots remain unchanged. To change the recovery passphrase, enter the current and new passphrases. Leave the fields blank to keep the existing passphrase.

> [!WARNING]
>
> Keep the recovery passphrase and your Dashboard's encryption keys safe. The passphrase can recover a lost encryption key, but you still need backups of the Dashboard database and backup files.

S3 **Server-side encryption** encrypts the stored copy at the provider. You can use it alongside MainWP's archive encryption. To stop requesting provider-side encryption from MainWP, select **None** and click **Test Connection & Save**. Your bucket's own encryption settings still apply.

## Create a Scheduled Backup

Open **Backups > Add New** (`/wp-admin/admin.php?page=ManageBackupsAddNew`).

**1. Name the task and select its sites**

Enter a **Backup task name** that describes its purpose, such as "Daily client sites". Select the Child Sites to include. If MainWP flags a site running MainWP Child older than 6.4, update the plugin on that site and sync it before adding it to the task.

**2. Choose the backup type and schedule**

Select a **Backup type** from the table below. Choose **Daily**, **Weekly**, **Monthly**, or **Every N hours**.

Times use the Dashboard WordPress site's timezone. Monthly schedules accept days 1 through 28. Leave the optional time empty to run the task at the next scheduler check after its interval has elapsed.

If tasks share a start time, use [Spread scheduled backup starts](https://docs.mainwp.com/sites/management/mainwp-dashboard-settings.md#spread-scheduled-backup-starts) to stagger daily, weekly, and monthly tasks. Check the adjusted time under **Next Run**.

**3. Choose storage, exclusions, and retention**

Select destinations under **Upload to storage**, review **Backup Excludes**, and set **Backup Retention**.

Leave storage empty to keep backups only on the Dashboard. Set retention limits to control storage use.

**4. Save and run a first test**

Click **Schedule Backup**. On **Manage Backups**, click **Run Now** for the task to test its configured type and destinations.

Check the result for each site, then confirm the task's **Next Run**.

![Scheduled backup form configured for daily full backups at 02:00, with three sites and offsite SFTP storage selected.](https://mintcdn.com/mainwp/Ep7JpkcO6W0zb6qi/images/sites/built-in-backups/scheduled-backup.jpg?fit=max\&auto=format\&n=Ep7JpkcO6W0zb6qi\&q=85\&s=ecd7243d2ca487850511457afa448a24)

### Choose a Backup Type

| Type | What it contains | Restore behavior |
| - | - | - |
| Full Backup | Site files and database, subject to exclusions | Restores files and database |
| Database Backup | Database content, such as posts, settings, and users | Restores the database without replacing files |
| Files Only Backup | Site files without the database, subject to exclusions | Restores files while keeping the current database, when the Child Site supports files-only restore |
| Incremental Backup | A full first backup, then changed files and a fresh database dump on each later run | Reconstructs the selected point in time using its backup chain |

An incremental **chain** includes the initial full backup and the later incremental backups that depend on it. Keep the chain together so MainWP can restore the selected snapshot.

The first incremental task run is full even when started with **Run Now**. If a Child Site lacks incremental support, MainWP takes full backups and records a note on the task. Keep MainWP Child updated and sync the site after updating.

### Database and Disk Usage

Built-in backups use database space for task and snapshot records, and disk space for backup files and file inventories. Incremental tracking does not create a database row for every site file.

| Location | What is stored |
| - | - |
| Child Site database | Backup and restore task status, progress, and information needed to resume interrupted work |
| Child Site disk | Backup archives, working files, and the file inventory used for incremental comparisons, including file paths, sizes, and modification times |
| Dashboard database | Snapshot records, links between incremental snapshots, archive details, storage settings, upload and restore progress, upload chunk details, and run history |
| Dashboard disk | Downloaded backup archives and file inventories, plus working files used during transfers and restores |

Database usage varies with backup frequency, the number of snapshots and storage destinations, archive and upload chunk counts, and restore activity. There is no fixed database-space figure per site or backup.

Retention removes backup files and their associated upload records, but keeps snapshot records so removed backups can appear in the removal history. Background cleanup removes run history older than 90 days. The **Storage cap (MB)** setting applies to backup files; it does not set a database size limit.

### Archive Format and Exclusions

**Archive type** can use the site setting, the global setting, or an explicit format. The available formats are Zip, Tar, Tar GZip, and Tar BZip2.

For large sites, use **Tar GZip**. MainWP can switch large Zip backups to Tar GZip unless **Keep Zip even when the site is large** is enabled.

Review the exclusion switches for known backup locations, known cache locations, non-WordPress folders, and ZIP archives. In MainWP Child 6.4.2 and later, **Known backup locations** covers the standard backup folders for All-in-One WP Migration, UpdraftPlus, and Duplicator. Excluding old backup archives avoids repeatedly backing up earlier backups. Do not exclude files you expect to recover.

Enter **Custom excludes** as paths relative to the Child Site's WordPress directory, separated by newlines or commas. For example, `wp-content/cache`. To exclude the standard WordPress uploads folder, use `wp-content/uploads`. To exclude only a form upload folder, enter that folder's actual relative path. Excluded files will not be available from that backup during restore.

### Database Dumps and the Clone Folder

The database portion of a backup contains a separate `.sql.php` file for each table. Each file starts with `<?php exit(); ?>`, followed by SQL. The `.php` extension allows a PHP-enabled web server to run this guard and stop before displaying the database contents if the file is requested over HTTP. MainWP reads this format automatically during a restore.

In a full backup archive, the database dump files are placed under `wp-content`. This location is part of MainWP's archive format. There is no setting to move them to the archive root or another subfolder.

The `clone` folder contains `config.txt`, which holds metadata used by MainWP's backup/cloning format, including the original site URLs, WordPress path, database table prefix, and lists of plugins and themes. Built-in file restores skip this metadata file.

### Performance on Larger Setups

Backup work uses resources on both the Child Site's server and the MainWP Dashboard. The Child Site creates the database dump and archive. The Dashboard downloads and stores the backup, encrypts it when enabled, and uploads copies to the selected storage destinations. Remote storage still requires disk space and transfer bandwidth on the Dashboard.

Completion times depend on database size, file count, archive size, server resources, and transfer speeds. Site count alone does not determine the resources your setup needs.

* Create separate scheduled tasks for groups of sites and give them different start times. Spread backups throughout the day, especially for sites that share a server.
* Start with a small, representative group that includes a larger site. Check backup and upload completion times, server load, free disk space, and bandwidth use on the Dashboard and Child Site servers before expanding to more sites.
* Consider [incremental backups](#choose-a-backup-type) to reduce the file data saved after the initial full backup. Each run still includes a fresh database dump.
* Review [archive formats and exclusions](#archive-format-and-exclusions) to avoid repeatedly archiving caches, old backups, and other folders you do not need to recover. Use [retention limits](#retention-and-cleanup) to control storage use.

Keep [Dashboard cron](https://docs.mainwp.com/customization/manage-wp-cron-on-low-traffic-mainwp-dashboard.md) working so scheduled backups and background uploads can continue. Check that both backup creation and storage uploads finish within the time available before the next run.

## Check Backup Health

View **Backup Health** in **MainWP > Sites > Manage Sites** (`/wp-admin/admin.php?page=managesites`) or **MainWP > Operations** (`/wp-admin/admin.php?page=mainwp_tab`). The summary appears when built-in backups are enabled and your account has permission to run backups.

![Backup Health widget with counts for Protected, At Risk, Critical, and No Backup.](https://mintcdn.com/mainwp/Ep7JpkcO6W0zb6qi/images/sites/built-in-backups/backup-health.jpg?fit=max\&auto=format\&n=Ep7JpkcO6W0zb6qi\&q=85\&s=695cc14dd30e8772e7cb2c5cdfb7ddfb)

Each site is classified using its latest completed built-in backup snapshot:

| Status | Meaning |
| - | - |
| Protected | The snapshot is no more than 24 hours old and its offsite copies are verified. |
| At Risk | The snapshot is over 24 hours old but no more than 7 days old, or is no more than 24 hours old without verified offsite copies. |
| Critical | The latest completed snapshot is more than 7 days old. |
| No Backup | No completed built-in backup snapshot is recorded. |

Click a status to filter Manage Sites to the matching sites. For **At Risk**, check the backup schedule and storage uploads. For **Critical** or **No Backup**, run a backup and confirm it completes.

A recent backup stored only locally shows **At Risk**. **Protected** confirms backup age and offsite verification; it does not confirm a successful restore test. See [Check Backup Status](#check-backup-status) for upload and restore-test results.

## Check Backup Status

Open **Manage Backups** (`/wp-admin/admin.php?page=ManageBackups`) to check **Last Run**, **Next Run**, destinations, and errors. Hover over **Last run reported errors** or **Last run notes** to read the details. These badges show tooltips; they do not open a copyable log. Use [Export Diagnostics](#export-diagnostics) for a downloadable report.

Starting a task with **Run Now** opens a progress window. Use **View Progress** or **View Result** to inspect the run. Closing the progress window leaves the backup running.

Click **Cancel Backup** in the task's progress window to stop the current run. Completed sites keep their backups, and the task's schedule stays unchanged.

For an on-demand backup, use **View progress** on **Snapshots & Restore** to reopen its progress window or **Cancel backup** to stop the current run.

Use the task's action menu to **Edit**, **Pause**, **Resume**, or **Delete** it. When deleting a task, clear **Also delete this task's snapshots** if you want to keep its backups. This option is selected by default.

A later **Clean Up** for the site deletes these retained snapshots and their cloud copies. See [Retention and Cleanup](#retention-and-cleanup).

On **Snapshots & Restore**, select a site and check **Available from** and the upload details.

If a snapshot shows **files not backed up**, click the warning to inspect the listed paths. A completed backup can still omit files. Resolve any unexpected omissions and create another backup before relying on it.

| Status | Meaning |
| - | - |
| Uploading / Waiting to Upload | The copy has not finished reaching its destination |
| Partially Uploaded | Some configured remote copies completed, but others have not |
| Retrying | A temporary upload error occurred. MainWP will try again in the background. |
| Upload Failed / Re-enter Credentials | Inspect the error and test or update the affected storage connection |
| Offsite Verified | All remote uploads for this snapshot completed and passed verification |
| Damaged Archive | A backup archive failed an integrity check. Review the reported error and create a new full backup. |

**Offsite Verified** includes remote file size checks. It does not confirm that the backup can restore the site.

### Read Test Restore Results

The **Test Restore** column shows the results of automatic checks on selected backups. MainWP tests them in a temporary environment on the Dashboard. Hover over the result for details, including the reason a test failed or could not run.

If **Couldn't test here** mentions database permissions, ask your hosting provider to let the Dashboard database account create and drop its own temporary `mainwp_tr_` databases and import and read the tables in them. Permissions on the Dashboard's existing database alone are insufficient. The same status can indicate an unsupported backup format or a missing server extension. Check the tooltip to distinguish these cases.

Test a full restore on a staging site before relying on a backup for recovery.

### Read Backup Errors

In MainWP Dashboard 6.4.2 and later, a backup error shows a short label with the full error below it.

When you click **Back Up Now**, the **Backup Progress** window opens. If the backup fails, the short label appears on the progress bar and the full error appears in the red box under it.

After you close the window, a message on **Snapshots & Restore** keeps the short label and adds a **View details** link. Click it to reopen the **Backup Progress** window and read the full error. You can also reach the link with the Tab key and open it with Enter. While a backup is still running, the same link reads **View progress**. If cancellation fails, the message on **Snapshots & Restore** keeps the full cancellation error while progress updates continue.

| Label | What it means | What to do |
| - | - | - |
| Backup could not start. | MainWP stopped before the backup began. For example, a restore is already running on the site, or Built-In Backups was turned off after the page loaded. | Read the full error, fix what it names, and click **Back Up Now** again. |
| Backup failed. | The backup started but did not finish. | Read the full error. If it names a folder, see [Find Where a Folder Error Comes From](#find-where-a-folder-error-comes-from). |
| Backup failed on the Dashboard server. | The Dashboard could not use its private backup folder. | See [Set Up the Private Backup Directory](#set-up-the-private-backup-directory). |
| Could not cancel the backup. | MainWP could not stop the backup. | Read the full error, then reopen the progress window to see whether the backup is still running. Try **Cancel backup** again if it is. |
| Full cleanup error | **Clean Up** could not finish removing leftover files. The banner shows the full reason with no **View details** link. | Fix the issue named in the banner and try **Clean Up** again. |

### Errors in Run Now

When you click **Run Now** on **Manage Backups**, the progress window lists each site in the task. In MainWP Dashboard 6.4.2 and later, a site that fails shows its error in red under the site name. If MainWP received no details, the line reads **Backup task failed.** Screen readers announce the error when it first appears and again only if it changes.

### Find Where a Folder Error Comes From

A folder error can come from the Child Site, the Dashboard server, or an SFTP server you added as storage. The folder can be missing or locked on any of them. In MainWP Dashboard 6.4.2 and later, folder errors name the machine:

| The error says | The folder is on | What to do |
| - | - | - |
| on the child site | The WordPress site you are backing up | Check folder permissions and free disk space on that site, or ask its hosting provider. The MainWP backup folder is in the site's uploads folder, usually `wp-content/uploads`. |
| on the Dashboard server | The server that runs your MainWP Dashboard | Check the [private backup directory](#set-up-the-private-backup-directory), or the **Directory path** of a **Local Path** destination on **Backups > Storage**. |
| on the SFTP server | Your SFTP storage server | Create the folder on the SFTP server, or change the destination's **Directory path** to a folder that exists. |

These are the folder errors you may see, grouped by machine:

* **Child Site:**
  * "The MainWP backup folder in the uploads folder on the child site is not writable."
  * "Could not create the ZIP archive on the child site."
  * "Could not write to the backup archive on the child site."
* **Dashboard server:**
  * "The folder ... does not exist on the Dashboard server." or "The web server cannot write to the folder ... on the Dashboard server." These come from testing a **Local Path** destination.
  * "Backup directory ... on the Dashboard server cannot be used." Check the **Directory path** of the **Local Path** destination.
  * "Private backup directory ... is unavailable." Check the [private backup directory](#set-up-the-private-backup-directory).
* **SFTP server:**
  * "The folder does not exist on the SFTP server."

One error can point to either machine: "Could not create a backup file or folder." It appears when the backup folder on the Child Site or the private backup folder on the Dashboard server cannot be written to. Check both.

### Backup Notification Emails

Review **Send email when backup starts** and **Send email when backup fails** under **MainWP menu (three lines, top right) > MainWP Settings > Backup Settings** (`/wp-admin/admin.php?page=BackupSettings`). Confirm that your Dashboard can send email before relying on these alerts.

Scheduled backup alerts normally go to the WordPress profile email of the account that last saved the task. To change that account's address, sign in as that user and open **WordPress Users > Profile** (`/wp-admin/profile.php`). A previously saved MainWP notification address from an older setup can take precedence. There is no separate recipient list for backup alerts on Backup Settings, and the recipient lists on Email Settings do not control these alerts.

The failure alert covers errors while executing the scheduled backup task. A later failure during a remote upload does not trigger that alert; also check the snapshot's upload status.

### Download a Backup

Click **Download** beside a snapshot when its archive is available on the Dashboard.

Incremental backups cannot be downloaded as one archive. Use **Restore** to restore the selected point in the chain. Backups stored only on remote storage can be restored, but cannot be downloaded through the Dashboard.

## Retention and Cleanup

Each scheduled task has its own **Backup Retention** settings, applied separately to each Child Site. For example, **Keep last** set to seven is a separate count for each site in that task, not a shared total across all selected sites. Another task for the same site has its own policy.

![Backup Retention settings in dark mode, including count, age and storage limits, Remove local archives after upload, and Remove cloud copies too.](https://mintcdn.com/mainwp/-h4a0E-NloTl-3RX/images/sites/built-in-backups/backup-retention.jpg?fit=max\&auto=format\&n=-h4a0E-NloTl-3RX\&q=85\&s=7442be8a3408381889cd66b299a89d8b)

| Setting | Effect |
| - | - |
| Keep last | Retains the selected number of backups or complete incremental chains |
| Remove backups older than (days) | Makes older backups or chains eligible for removal |
| Storage cap (MB) | Removes older backups or chains when their combined size exceeds the cap |
| Remove local archives after upload | Removes Dashboard archives from new backups after every selected destination has a verified upload; requires at least one remote destination |
| Start a new chain after (backups) | Creates a new full base after an incremental chain reaches this length, including its initial full backup |
| Remove cloud copies too | Also deletes the corresponding remote copies when task retention removes a backup |

When task retention removes a backup, it removes the Dashboard's backup files. Enable **Remove cloud copies too** to include the corresponding remote copies in that cleanup. If it is off, the remote copies remain.

Enable **Remove local archives after upload** to save disk space on the Dashboard after uploads finish. It applies to new backups created by the task, including runs started with **Run Now**, and leaves existing backup archives unchanged. MainWP keeps the file inventories needed for incremental backups. Snapshots whose archives are available only remotely show **Remote only** and can still be restored, but cannot be downloaded through the Dashboard. Normal task retention still applies.

Leave a retention limit blank or enter zero for no limit. Each enabled limit can make older backups eligible for removal. For example, **Keep last** set to seven can remove an older backup before a 30-day age limit is reached. For age-based cleanup alone, leave **Keep last** and **Storage cap (MB)** blank. The age limit is a cleanup threshold, not a guaranteed minimum storage period.

Scheduled retention keeps the newest complete, restorable backup or chain for each task and site, even if it exceeds the storage cap. Incremental chains are kept or removed together, so **Keep last** counts chains rather than individual snapshots.

For **Back Up Now**, set **On-demand backups to keep** under **MainWP menu (three lines, top right) > MainWP Settings > Backup Settings** (`/wp-admin/admin.php?page=BackupSettings`). The default is five per site, with a minimum of one.

> [!NOTE]
>
> **Leftover backup files to keep** in **Backup Settings** controls cleanup of older downloaded files in each site's backup folder on the Dashboard. It applies to files that are not protected by completed snapshots or active runs. The default is one; zero keeps all leftover files. It does not limit completed snapshots or copies at storage destinations.

On **Snapshots & Restore**:

* Use **Delete** to remove a backup. Select **Also delete cloud copies** to remove its copies from storage destinations.
* Use **Clean Up** to remove leftover files from interrupted backups, prune on-demand backups beyond the keep count, and delete snapshots whose task was deleted.
* Enable **Show removed backups** to see removal history and reasons.

**Delete** and **Clean Up** appear only for users who can delete backups. With [Team Control](https://docs.mainwp.com/add-ons/agency/team-control-extension.md#backup-permissions), this can be a separate permission from running backups.

> [!WARNING]
>
> **Clean Up** also deletes cloud copies of snapshots whose task was deleted, even if you kept those snapshots when deleting the task. Deleted backups can no longer be restored.
>
> Use the Dashboard controls for cleanup. Do not delete individual incremental chain files or the entire Child Site `wp-content/uploads/mainwp` directory. That directory can contain other MainWP data and encryption material.

### Minimum Retention at a Destination

Open **Backups > Storage** (`/wp-admin/admin.php?page=ManageBackupsStorage`) and add or edit a destination. Set **Minimum retention (days)** to the minimum time its copies should remain before automatic cleanup can remove them. Set it to zero to disable this protection.

The period starts when the upload is verified. For older backups without a recorded upload time, MainWP uses the snapshot's creation time. Task count, age, and storage limits do not override this minimum. A protected snapshot can also keep its incremental chain from being removed automatically.

Manual deletion can override the minimum. Review the confirmation before deleting a snapshot or its cloud copies.

## Restore a Backup

You can restore a snapshot to its original Child Site. Connect the site and wait for any running backup or restore to finish before starting.

**1. Select the site and snapshot**

Open **Backups > Snapshots & Restore** (`/wp-admin/admin.php?page=ManageBackupsSnapshots`). Select the site, check the snapshot date and type, and click **Restore**.

MainWP can use an available local or completed remote copy. For incremental backups, the required chain must be available.

**2. Review what will be replaced**

A full or incremental restore replaces files and database content. A database restore changes the database only; a files-only restore leaves the database in place.

Changes made after the snapshot may be lost. Review any warnings before proceeding.

See [How Files and Database Tables Are Restored](#how-files-and-database-tables-are-restored) for cleanup rules and exceptions.

**3. Keep the safety backup enabled**

Leave **Create a safety backup first** selected. This backup stays on the Child Site and lets you roll back if the restore fails or you need to undo it.

Confirm **I understand this replaces the current site content**, then click **Start Restore**.

![Restore Backup confirmation with the replacement warning, safety backup enabled, consent checkbox, and optional WooCommerce order preservation.](https://mintcdn.com/mainwp/Ep7JpkcO6W0zb6qi/images/sites/built-in-backups/restore-confirmation.jpg?fit=max\&auto=format\&n=Ep7JpkcO6W0zb6qi\&q=85\&s=0e8dadcdfd307784f07328bad3b1f360)

**4. Check the restored site**

Wait for **Restore completed**, then click **Visit site**. Check key pages, sign-in, and other site functions. Review any warnings and the **Recent restores** list.

### How Files and Database Tables Are Restored

MainWP restores the snapshot in place. It does not delete the entire site and database before restoring.

**Files:** MainWP restores the backed-up files, then compares the site against a file inventory saved automatically with the backup. It removes files that are absent from that inventory within the backup's scope, with these exceptions:

* `wp-config.php` and `wp-content/object-cache.php`
* MainWP Child and MainWP's data and backup directories
* Existing `mu-plugins` files that are absent from the backup
* Paths excluded from the backup, symbolic links, and certain files required by the site's configuration
* Files that could not be archived during the backup

Files-only restores also keep additional files in the uploads directory because the current database remains in use.

If the backup's file inventory is unavailable or cannot be verified, MainWP skips the additional-file cleanup and displays a warning. Review restore warnings even when the restore completes.

**Database tables:** MainWP replaces restored tables with the backup's version instead of merging their contents with current rows. Existing tables that are absent from the backup are not automatically deleted.

> [!WARNING]
>
> A built-in restore is not a complete site wipe or a guaranteed malware cleanup. Malicious files or database tables can remain in preserved or excluded areas.

### Cancel or Roll Back a Restore

**Cancel Restore** stops further processing but does not undo files already replaced. If a safety backup is available, use **Roll Back** to return to the site's state before the restore.

In 6.4.2 and later, rollback can remove files introduced by the restore when they fall within the safety backup's scope and MainWP can verify its file inventory. Review any rollback warnings and check the site afterward.

If the restore finished on the Child Site but the Dashboard cannot reconnect, click **Stop Checking** to end the connection checks. This marks the restore as failed without rolling it back. Visit the site to check its state.

After a failed database restore, resolve the reported database problem before removing maintenance mode.

### Restore From the Command Line

If WordPress Admin or the Dashboard is unavailable, you can restore a built-in backup directly on the Child Site server with WP-CLI. This path does not create a safety backup. See [Restore a Built-In Backup](https://docs.mainwp.com/advanced/miscellaneous/mainwp-wp-cli-commands.md#restore-a-built-in-backup) for the command and [destination URL behavior](https://docs.mainwp.com/advanced/miscellaneous/mainwp-wp-cli-commands.md#restore-to-a-different-domain).

```bash theme={null}
wp mainwp-child backup restore backup-1718900000.zip --type=full --yes
```

> [accordion] Restoring a WooCommerce store
>
> Restoring a database normally replaces orders, customers, and other data with the snapshot's version.
>
> When available, select **Preserve orders placed since the backup** to keep live order tables and reapply recent customer and stock data. This requires High-Performance Order Storage (HPOS), order-table synchronization turned off, an HPOS backup, and a matching WooCommerce database version. Older order-table contents from the backup are not restored.
>
> If those conditions are not met, the restore stops with an explanation. Review order, customer, and stock data after any store restore.

## Require a Backup Before Updates

In **MainWP menu (three lines, top right) > MainWP Settings > General Settings > Updates Settings** (`/wp-admin/admin.php?page=Settings`), enable **Require a backup before an update** and set **Days without a full backup (tolerance)**.

Use this setting to require a recent backup before updating from **Manage Sites**. In MainWP Dashboard 6.4.1 and later, the same check also applies when starting updates from the **Updates**, **Plugins**, and **Themes** pages.

Built-in backups accept completed full, database-only, or incremental backups within the allowed age. Files-only backups do not qualify.

Enable **Require an offsite-verified backup** to also require verified copies on remote storage. Local Path destinations do not count as offsite storage. Wait for remote uploads to finish before retrying the update.

For recovery after a failed update, see [Safe Updates & Rollback](https://docs.mainwp.com/sites/updates/does-mainwp-have-safe-updates.md).

## Automate Backups

MainWP Dashboard 6.4 includes 32 [backup abilities](https://docs.mainwp.com/api-reference/abilities-api/backups.md) for reading status, managing tasks and destinations, running backups, and restoring snapshots. Use the WordPress Abilities API directly or connect an assistant through the [MainWP MCP Server](https://docs.mainwp.com/mcp-server/overview.md).

Actions support a preview before confirmation. Backup and restore jobs continue in the background, so follow their progress until completion.

## Troubleshooting and Limitations

| Symptom | What to check |
| - | - |
| Backup screens are missing | Enable built-in backups, check the primary backup system, and confirm your account has the relevant permissions |
| `Private backup directory` is unavailable or could not be created | Configure a writable private directory on the Dashboard server. See [Set Up the Private Backup Directory](#set-up-the-private-backup-directory). |
| An error names a folder on the child site, the Dashboard server, or the SFTP server | See [Find Where a Folder Error Comes From](#find-where-a-folder-error-comes-from) |
| A site cannot be backed up | Check [What a Site Needs Before a Backup Can Run](#what-a-site-needs-before-a-backup-can-run) |
| Backup stays on the Dashboard | Check Upload to storage on the task, or read the destination message before Back Up Now |
| Upload fails | Use Test on the destination, check credentials, available space, and access to the configured bucket or directory |
| S3 storage test returns `cURL error 60` with "no alternative certificate subject name matches target hostname" | Check whether the bucket name contains a dot. If it does, see [S3 Bucket Names with Dots](#s3-bucket-names-with-dots). Other cURL error 60 messages can have different causes. |
| Scheduled work or background uploads stall | Check Dashboard cron, server loopback requests, and the task error. See [Cron configuration](https://docs.mainwp.com/customization/manage-wp-cron-on-low-traffic-mainwp-dashboard.md). |
| Restore is unavailable | Check that the site is connected and the backup files are available. Update MainWP Child and sync again when prompted. |
| Large backup is slow or times out | Check free disk space, use Tar GZip, and review cache and old-backup exclusions |
| Backup or restore fails with "This request uses a newer backup format than this version of MainWP Child supports" | The Child site runs an older MainWP Child version. Update MainWP Child on that site, sync it, and start the backup or restore again. MainWP Child makes no changes to the site when it rejects the request. |
| Backup or restore fails with "The site layout changed" | The site's folder layout changed after the task started. Start the backup or restore again. |
| Restore stops partway through a large backup | The restore inactivity timer resets while backup data is transferring to the Child site. A stalled transfer or an expired restore time limit can stop it. Read the reported error and check disk space on the Child Site before trying again. |
| File backup is refused because content is outside the WordPress folder | Built-in backups do not support this layout for file backups or restores. Use database-only tasks and your host's file backups. |

Sites with `wp-content` or uploads outside the WordPress core directory, including symlinked folders, cannot use file backups or restores. Create a **Database Backup** task for these sites; **Back Up Now** always creates a full backup.

Database-only backups and restores remain supported. A database-only restore can stop before making changes if **Create a safety backup first** is enabled, because that safety backup includes files. Keep an independent database backup, then restart the database-only restore with **Create a safety backup first** turned off.

### Export Diagnostics

Export diagnostics from **MainWP menu (three lines, top right) > MainWP Settings > Backup Settings** (`/wp-admin/admin.php?page=BackupSettings`).

1. Enable **Backup run diagnostics** and click **Save Settings**. The **Export diagnostics data** button appears after saving.
2. If diagnostics was not enabled when the problem occurred, run the affected backup task again to record it. If it was already enabled, you can export the existing data.
3. Click **Export diagnostics data** to download the report to your computer. Attach the downloaded file to your support request with the task name, backup type, storage provider, and time of the failed run.

The report normally downloads as a ZIP. Extract it and open `tasks.json` in a text editor to read the stored task errors under `backup_errors` and notes under `backup_notices`. Detailed run events are in the `events/` folder as `.jsonl` files. If ZIP support is unavailable on the Dashboard, the report downloads as a JSON file instead.

This is a diagnostics package for troubleshooting, not an on-screen log viewer. Detailed run logs are recorded only while diagnostics is enabled and are kept on the Dashboard for up to two weeks.

## API Backups

To create and restore backups through your hosting provider, see [API Backups](https://docs.mainwp.com/sites/backups/api-backups.md). Provider setup instructions include:

* [cPanel backups](https://docs.mainwp.com/sites/backups/api-backups.md#cpanel-backups)
* [DigitalOcean setup](https://docs.mainwp.com/sites/backups/api-backups.md#connect-digitalocean)
* [Kinsta setup and downloads](https://docs.mainwp.com/sites/backups/api-backups.md#connect-kinsta)

## Self-Check Checklist

* [ ] Built-in backups are enabled and the test Child Site syncs successfully
* [ ] A first backup completed and appears under Snapshots & Restore
* [ ] The expected storage copies completed, including Offsite Verified when required
* [ ] Scheduled tasks have the intended sites, destinations, exclusions, and retention
* [ ] The recovery passphrase is stored separately if encryption is enabled
* [ ] A restore has been checked on a test site
* [ ] The Dashboard itself has a separate backup

## Related Resources

* [API Backups](https://docs.mainwp.com/sites/backups/api-backups.md) - Hosting-provider backup integrations
* [Backup Add-ons](https://docs.mainwp.com/add-ons/backups.md) - Third-party backup plugin integrations
* [MainWP Dashboard Settings](https://docs.mainwp.com/sites/management/mainwp-dashboard-settings.md) - General configuration
* [Cron configuration](https://docs.mainwp.com/customization/manage-wp-cron-on-low-traffic-mainwp-dashboard.md) - Keep scheduled work running


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.