Fully Managed Backup Service


This feature is not available for M0 (Free Tier), M2, and M5 clusters. For more information, see Atlas M0 (Free Tier), M2, and M5 Limitations.

Atlas continuously backs up your data, ensuring your backups are typically just a few seconds behind the operational system.


Atlas only allows one backup method per project. Once you select a backup method for a cluster in a project, Atlas locks the backup service to the chosen method for all subsequent clusters in that project.

For example, in a project where one or more clusters use continuous backups, you cannot enable cloud provider snapshots for any cluster in that project.

To change the backup method for the project, disable backups for all clusters in the project, then re-enable backups using your preferred backup methodology. Atlas deletes any stored snapshots when you disable backup for a cluster.

Consider creating a separate project for clusters where a different backup method is required.

You must restore a backup to an Atlas cluster running the same version of MongoDB as the cluster that you want to restore. The length of time required for an upgrade depends on factors such as the number of nodes in the cluster. Atlas uses a rolling upgrade process to maintain cluster availability.


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.

Atlas supports two backup methods:

Continuous Backups

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 one backup data center location dictated by the first backup-enabled cluster created in that project.

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

Collection Limit for Atlas Continuous Backup.

If the total number of collections across all databases in a Atlas cluster meets or exceeds 100,000, Atlas continuous backup cannot take snapshots of that cluster.

If you need to enable Atlas continuous backup in a project where one or more deployments meets or exceeds the collection limit, click Support in the left-hand navigation bar of the Atlas UI and filling in the requested information to open a support ticket.

Cloud Provider Snapshots do not have a collection limit.

Cloud Provider Snapshots


Atlas only supports cloud provider snapshots for Microsoft Azure or Amazon Web Services (AWS) backed replica sets.

A project using the Atlas Cloud Provider Snapshots cannot create backups of sharded clusters or any cluster hosted on Google Cloud Provider (GCP).

Atlas uses the native snapshot capabilities of your cloud provider to support full-copy snapshots and localized snapshot storage.

For each Atlas cluster with cloud provider snapshots enabled, Atlas stores the snapshots in the same region as the snapshot source replica set member.