Docs Menu
Docs Home
/ /
/ / /

Restore from Continuous Cloud Backup

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.

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

    Note

    The MongoDB Search index definitions captured at the snapshot time specified for the point in time restore replace any existing MongoDB 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 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.

  • For target clusters with AWS nodes created before March 27, 2024, enable faster cross-project restores by clicking the Faster Restore button in the Backup details for your project in the Atlas UI. This button doesn't appear for MongoDB Atlas for Government clusters.

    When you activate Faster Restore, Atlas replaces each node in the target cluster one at a time during your target cluster's scheduled maintenance windows. If a node doesn't start its replacement before a maintenance window ends, it will be replaced in the next window. Secondary reads and analytic nodes are unavailable during this change.

    Faster cross-project restores are automatic for clusters with Google Cloud or Microsoft Azure nodes, or with AWS nodes created after March 27, 2024. If the Faster Restore button is missing or disabled, you already have faster cross-project restores enabled.

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

To restore an encrypted or unencrypted snapshot created in an Atlas project to the same project, you require the Project Backup Manager role.

To restore an encrypted or unencrypted snapshot created in a source Atlas project to a different target project, you require the Project Owner role in the target project.

Atlas deletes all existing data on the target cluster prior to the restore. The target cluster is unavailable for the duration of the restore. As part of the restore, Atlas also restores any indexes.

To start a restore job for your project and cluster using the Atlas CLI, run the following command:

atlas backups restores start <automated|download|pointInTime> [options]

To watch for a specific restore job to complete using the Atlas CLI, run the following command:

atlas backups restores watch <restoreJobId> [options]

To learn more about the syntax and parameters for the previous commands, see the Atlas CLI documentation for atlas backups restores start and atlas backups restores watch.

Tip

See: Related Links

You can enable Continuous Cloud Backups for dedicated clusters when you create or scale a cluster.

1
  1. If it's not already displayed, select the organization that contains your project from the Organizations menu in the navigation bar.

  2. If it's not already displayed, select your project from the Projects menu in the navigation bar.

  3. In the sidebar, click Backup under the Database heading.

    The Backup details display.

  4. Click the cluster link.

2

Click the Point in Time Restore button on the far right side of the screen.

3

If you select the Date & Time option, you can specify the time of restore with one minute of granularity. If you select the Oplog Timestamp option, you can specify the time of restore with one second of granularity.

4

Important

You can restore a cluster from any time during its continuous cloud backup window except between when you initiated a restore and when Atlas completes a snapshot after the restore.

5
6

Important

Atlas might create a host rollback alert due to differences in the data between the source and target clusters. You can ignore this alert.

7

Back

Restore from Snapshot

On this page