Back Up, Restore, and Archive Data
Backups are copies of your data that encapsulate the state of your cluster at a given time. Backups provide a safety measure in the event of data loss.
You must have the Project Owner role for an Atlas
project to manage backups for or to restore a backup to clusters in
that project.
Considerations
Be aware that:
- Atlas backups are not available for
M0free clusters. You may use mongodump to back up yourM0cluster data and mongorestore to restore that data. To learn how to manually back up your data, see Command Line Tools. - 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.ExampleTo restore a 3.6 cluster to 4.0:
- Restore the old 3.6 backup to another 3.6 cluster.
- Upgrade the restored cluster to 4.0.
Cloud Backups
Available in M10+ Clusters.
Atlas uses the native snapshot capabilities of your cloud provider to support full-copy snapshots and localized snapshot storage.
Atlas supports Cloud Backups on:
To learn more, see Back Up Your Database Deployment.
To learn how to restore cluster from a Cloud Backup, see Restore Your Database Deployment.
M2 / M5 Snapshots
Backups are automatically enabled for M2 and M5 shared clusters
and can't be disabled. Atlas takes
daily snapshots of your M2 and M5
clusters which you can restore to clusters tiers M2 or greater.
To learn more about M2 / M5 daily snapshots, see
Shared Cluster Backups.
To learn how to restore a cluster from an M2 / M5 snapshot,
see Restore a Cluster from an M2/M5 Snapshot.
Serverless Instance Snapshots
Atlas uses the native snapshot capabilities of your cloud provider to support full-copy snapshots and localized snapshot storage.
Backups are automatically enabled for serverless instances. You can't disable serverless instance backups.
Atlas takes snapshots of your serverless instances every six hours. You can restore serverless instance snapshots to other serverless instances and dedicated clusters.
To learn more, see:
Legacy Backups
Available in M10+ Clusters.
Effective 23 March 2020, all new clusters can only use Cloud Backups.
When you upgrade from 4.0 to 4.2, 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.
Atlas uses incremental snapshots to continuously back up your data. Continuous backup snapshots are typically just a few seconds behind the operational system.
Atlas ensures continuous cloud backup of replica sets and consistent, cluster-wide snapshots of sharded clusters.
For each Atlas project with legacy backups enabled, Atlas stores the legacy backup snapshots in the backup data center location where legacy backups were first enabled for a cluster in the project.
Continuous snapshots support restoring from the full snapshot or from a Continuous Cloud Backup between snapshots. You can also query a continuous snapshot.
With Atlas legacy backup, the total number of collections
across all databases in a Atlas cluster can't be equal to or
exceed 100,000.
To learn more about Legacy Backups, see Legacy Backups (Deprecated).
To learn how to restore cluster from a Legacy Backup, see Restore a Cluster from a Legacy Backup Snapshot.