Docs Home → Launch & Manage MongoDB → MongoDB Atlas
Restore a Cluster from a Legacy Backup Snapshot
On this page
Important
Legacy Backup Deprecated
Effective 23 March 2020, all new clusters can only use Cloud Backups.
When you upgrade to 5.0, your backup system upgrades to cloud backup if it is currently set to legacy backup. After this upgrade:
All your existing legacy backup snapshots remain available. They expire over time in accordance with your retention policy.
Your backup policy resets to the default schedule. If you had a custom backup policy in place with legacy backups, you must re-create it with the procedure outlined in the Cloud Backup documentation.
Note
This feature is not available for M0 free clusters, M2, and
M5 clusters. To learn more about which features are unavailable,
see Atlas M0 (Free Cluster), M2, and M5 Limits.
Atlas lets you restore data from a scheduled legacy backup snapshot or from a selected point between snapshots.
Note
You must have the Project Owner role for the Atlas
projects that contain the source and target clusters to restore
data from one Atlas cluster to another.
For replica sets, you can restore from selected points in time within the last 24 hours.
For sharded clusters running:
FCV of 4.2 or earlier, you can restore from checkpoints between snapshots within the last 24 hours.
FCV of 4.2 or later, you can restore from selected points in time within the last 24 hours.
You can restore data to the same cluster from which the snapshot was taken or to other clusters that Atlas or Cloud Manager manage.
You must restore the backup to a cluster running either the same major release version, or the next higher one. Atlas doesn't support restoring to older versions.
You can still use backups made before an upgrade.
Example
To restore a 4.0 cluster to 4.2:
Restore the old 4.0 backup to another 4.2 cluster.
Upgrade the restored cluster to 4.2.
For instructions on restoring data from a Cloud Backup, see Restore Your Database Deployment.
Considerations
Downtime for the Target Cluster
The restore process requires downtime for the target cluster.
MongoDB Versions Must Be Compatible
The MongoDB versions must also be compatible. For instance, you cannot restore from a snapshot of a 5.0 cluster to a 4.2 or earlier cluster.
Restore to Atlas or Cloud Manager
If you have the proper project permissions, you can restore to a cluster of a different project in either Atlas or Cloud Manager:
Restore to Project on | Required Roles on Destination Project |
|---|---|
Atlas | |
Cloud Manager | One of the following Cloud Manager roles: |
Prerequisites
Stop Client Operations during Restoration
You must ensure that the target Atlas database deployment doesn't receive client requests during restoration. You can restore to a new database deployment and reconfigure your application to use that new database deployment once it is running for maximum uptime.
Procedure
In addition to standard snapshots and Continuous Cloud Backup, you can restore a Legacy Backup from a locally-downloaded snapshot file.