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
Restore Considerations
In addition to the prerequisites consider the following requirements and limitations when restoring from a Continuous Cloud Backup.
If the
DefaultRWConcernvalue on the source snapshot differs from theDefaultRWConcernvalue 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 theDefaultRWConcernon the target cluster, Atlas keeps the value ofDefaultRWConcernfrom 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.
Recommendations to Optimize Restore Times
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 themongotprocesses 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.Note
The Atlas Search index definitions captured at the snapshot time specified for the point in time restore replace any existing Atlas Search index definitions.
General Optimizations
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.
Required Access
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.
Procedure
Atlas deletes all existing data on the target cluster prior to the restore. The target cluster is unavailable for the duration of the restore.
Restore a Cluster
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.
Restore a Serverless Instance
To start a restore job for your serverless instance using the Atlas CLI, run the following command:
atlas serverless backups restores create [options]
To watch the specified backup restore job until it completes using the Atlas CLI, run the following command:
atlas serverless backups restores watch [options]
To learn more about the syntax and parameters for the previous commands, see the Atlas CLI documentation for atlas serverless backups restores create and atlas serverless backups restores watch.
You can enable Continuous Cloud Backups for dedicated clusters when you create or scale a cluster.
In Atlas, go to the Clusters page for your project.
If it's not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar.
If it's not already displayed, select your desired project from the Projects menu in the navigation bar.
If it's not already displayed, click Clusters in the sidebar.
The Clusters page displays.
Go to the Backup page for your cluster.
Click your cluster's name.
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 you scale the cluster.
The Backup page displays.
Select either the Date & Time or Oplog Timestamp tab.
Note
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.
Enter the desired point in time to restore from.
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.
Click the Next: Select Cluster button.
Choose a project and cluster to restore to from the dropdown menus.
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.
Click the Restore button.
Select the Date & Time from which you want to restore data. The date and time must be within the last 72 hours. You can specify the time of restore with one minute of granularity.
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.
Click the Next: Select Cluster button.
Choose a project and cluster to restore to from the dropdown menu.
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.
Click the Restore button.
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.