Restore Your Database Deployment

Restore Restrictions

• The target cluster must run the same or the next major release version of MongoDB as the snapshot MongoDB version.

  Example

  You can restore a MongoDB 4.2 snapshot to an Atlas cluster running MongoDB 4.4. If you try to restore a MongoDB 4.2 snapshot to an Atlas cluster running MongoDB 5.0, you receive the following error:

  Error: The requested restore could not be started: The source and destination
  mongoDB versions are incompatible.
• Atlas can only restore to a replica set or sharded cluster that uses the same encryption provider as the source snapshot cluster.
• Atlas can't restore a sharded cluster snapshot to a replica set.

Fallback Snapshots

If a scheduled snapshot fails for any reason, Atlas attempts to repeat the snapshot process. If necessary, you may use the resulting fallback snapshot to restore the cluster. This isn't recommended: fallback snapshots use a different process from regular snapshots. They may contain inconsistent data.

Fallback snapshots are marked in the UI with a warning icon, and a warning message appears in the restore modal window if the restore uses a fallback snapshot.

Prerequisites

Procedure

Restore a Snapshot of a Cluster with Encryption at Rest

1. Click Databases in the top-left corner of Atlas.
2. From the Database Deployments view, click on the cluster name.

3. Click the Backup tab.

   If the cluster has no Backup tab, then Atlas backups are disabled for that cluster and no snapshots are available. You can enable backups when modifying the cluster.

4. Click Restore in the Actions column for the snapshot you want to restore.
5. From the Restore dialog, select the target Atlas Project to which you want to restore. You can restore to any Atlas project for which the authenticated Atlas user has the Project Owner role.

6. Select the Cluster to restore to. You can only restore to an Atlas replica set running Encryption at Rest. The target cluster must run the same or greater version of MongoDB as the MongoDB Version of the snapshot.

   After the restoration procedure, Atlas triggers a key rotation for MongoDB encryption key. Atlas then encrypts the new MongoDB encryption keys based on the configured Encryption at Rest provider for the target cluster.

7. Restart your application and ensure it uses the new target cluster.

View Status of Snapshot Restorations

Atlas provides a detailed list of completed and in-progress snapshot restorations, including when Atlas took the snapshot and the snapshot's delivery type. To view this list, from a cluster's Backup tab, click the Restores & Downloads tab.

The Status column of the table displays the results of completed snapshots, and the progress of snapshots currently being restored.

• For manually downloaded snapshots, the Status column displays progress while Atlas prepares the download link. Once the download is ready, the column displays the link to download the snapshot.
• For automated restores and Continuous Cloud Backup restores, the Status column updates as the restoration progresses on each node in the cluster. When the restoration completes, the column displays the time of completion and the cluster to which Atlas restored the snapshot.

Restore Restrictions

• Atlas can restore M2 and M5 snapshots only to a replica set that does not use Encryption at Rest.
• The target cluster must run the same major release version of MongoDB as the snapshot MongoDB version. For example, you can restore a snapshot using MongoDB 4.0 only to a target cluster running MongoDB 4.0.

• Starting with MongoDB 5.0, you can restore snapshots of clusters that run only the two most recent major versions of MongoDB to M2 and M5 clusters.

  Example

  • You can restore snapshots taken from clusters that run MongoDB 4.2 to an M2 or M5 cluster that runs MongoDB 5.0.
  • You can't restore snapshots taken from clusters that run MongoDB 4.0 to an M2 or M5 cluster that runs MongoDB 5.0.

Prerequisites

1. You must ensure that the target Atlas cluster does not receive client requests during restoration. You must either:
   • Restore to a new Atlas cluster and reconfigure your application to use that new cluster once the new deployment is running, or
   • Ensure that the target Atlas cluster cannot receive client requests while you restore data.
2. To download your snapshot via HTTPS, you must add the IP or CIDR addresses of the client downloading the snapshot to your Atlas project access list.

Procedure

1. Click Databases in the top-left corner of the {atlas-ui+}.
2. From the Database Deployments view, click the {+cluster_} name.
3. Click the Backup tab.
4. Find the desired cluster snapshot to restore.
5. For the desired cluster, click Restore or Download.

6. Follow the prompts to restore your cluster. You may choose to one of the following actions:

   • Download your snapshot via HTTPS.
   • Restore your snapshot to an Atlas cluster.

Restore Restrictions

• You can restore from only the two most recent snapshots of a serverless instance.
• You can't restore snapshots from shared clusters, dedicated clusters, or from Cloud Manager to serverless instances.

Prerequisites

Procedure

1. Click Databases in the top-left corner of the Atlas UI.
2. From the Database Deployments view, click your serverless instance.
3. Click the Backup tab.
4. Select a cluster snapshot to restore.
5. Click Restore.
6. Follow the prompts to restore your serverless instance snapshot.

View the Status of Snapshot Restorations

Atlas provides a detailed list of completed and in-progress snapshot restorations, including when Atlas took the snapshot and the snapshot's delivery type. To view this list, from a serverless instance's Backup tab, click the Restores tab.

The Status column of the table displays the results of completed snapshots, and the progress of snapshots currently restoring.

The Status column updates as the restoration progresses on the serverless instance. When the restoration completes, the column displays the time of completion and the serverless instance that Atlas restored the snapshot to.

Procedure