Navigation

Backup

Feature unavailable in Free Tier Clusters

This feature is not available for M0 (Free Tier) clusters. To learn more about M0 cluster limitations, see Atlas M0 (Free Tier), M2, and M5 Limitations.

Backup Methods

Atlas offers the following methods to back up your data.

Continuous Backups

Available in M10+ Clusters.

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 point-in-time backup of replica sets and consistent, cluster-wide snapshots of sharded clusters.

For each Atlas project with continuous snapshots enabled, Atlas stores the continuous backup snapshots in the backup data center location where continuous backups were first enabled for a cluster in the project.

Continuous snapshots support restoring from the full snapshot or from a point-in-time between snapshots. You can also query a continuous snapshot.

With Atlas continuous backup, the total number of collections across all databases in a Atlas cluster cannot equal or exceed 100,000.

Cloud Provider Snapshots

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 provider snapshots on:

M2/M5 Snapshots

Backups are automatically enabled for M2 and M5 shared-tier clusters and cannot be disabled. Atlas takes daily snapshots of your M2 and M5 clusters which you can restore to clusters of size M2 or greater.

Considerations

Be aware that:

  • Atlas backups are not available for M0 (Free Tier) clusters. You may use mongodump to back up your M0 cluster data and mongorestore to restore that data. To learn how to manually back up your data, see Command Line Tools.

  • You must restore a backup to an Atlas cluster running the same major release version of MongoDB as the cluster that you want to restore.

    Tip

    You can still use backups made before an upgrade. For example, you can restore a 3.6 cluster to 4.0 with the following procedure:

    1. Restore the old 3.6 backup to another 3.6 cluster.
    2. Upgrade the restored cluster to 4.0.