Docs Menu
Docs Home
MongoDB Atlas
/ /

Restore from Continuous Cloud Backup

On this page

  • Restore Considerations
  • Recommendations to Optimize Restore Times
  • Required Access
  • Procedure

Atlas lets you restore data from a Continuous Cloud Backup by specifying one of the following options:

  • A specific date and time to which you want to restore

  • A specific oplog entry from which you want to restore

In addition to the prerequisites consider the following requirements and limitations when restoring from a Continuous Cloud Backup.

  • If the DefaultRWConcern value on the source snapshot differs from the DefaultRWConcern value on the target cluster, Atlas overrides the value on the source snapshot with the value on the target cluster. If there is no value configured for the DefaultRWConcern on the target cluster, Atlas keeps the value of DefaultRWConcern from the snapshot without explicit configuration. This may differ from the default value for that MongoDB version.

  • This feature is only available for M10+ dedicated clusters and serverless instances.

  • If you are restoring from Serverless Continuous Backup, you can only use a Date & Time within the last 72 hours. Serverless instances don't support restoring from an oplog entry.

  • For M10+ dedicated clusters running MongoDB 4.2 or higher, Atlas will restore Atlas Search index definitions from a Cloud Backup snapshot. Atlas doesn't restore the index data, so the mongot processes perform initial syncs for all restored index definitions. If you've defined large search indexes on your cluster, you might experience delays during snapshot restorations.


    The Atlas Search index definitions captured at the snapshot time specified for the point in time restore replace any existing Atlas Search index definitions.

To optimize performance and reduce the amount of time it takes to restore, follow these principles where applicable:

  • Select a target cluster that isn't global or multi-cloud.

  • Select a multi-region cluster only if copies of the snapshot you plan to restore exist in every region of that cluster.

  • Select a target cluster that belongs to the same Atlas project and the same cloud provider region as the snapshot.

  • Select a cluster tier with the same storage capacity as the capacity of the original volume used by the source cluster.

  • If the target cluster runs on AWS with configured IOPS, select the configured IOPS to fall within the configured range.

  • Select a cluster that is not configured to use NVMe storage. NVMe storage degrades restore performance.

To start a restore job, you must have Project Owner access or higher to the project.

To watch a backup restore job until it completes, you must have Project Read Only access or higher to the project.

Atlas deletes all existing data on the target cluster prior to the restore. Depending on the type of restore taking place, the target cluster may be unavailable for the duration of the restore.

After the restore completes, Atlas takes a snapshot of the restored cluster. This snapshot has a retention period equal to the cluster's continuous cloud backup window.

← Restore from a Scheduled or On-Demand Snapshot