• Restoration >
  • Restore a Cluster from a Continuous Backup Snapshot

Restore a Cluster from a Continuous Backup Snapshot


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 lets you restore data from a scheduled continuous backup snapshot or from a selected point between snapshots. For replica sets, you can restore from selected points in time within the last 24 hours. For sharded clusters you can restore from checkpoints between snapshots within the last 24 hours.

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.

For instructions on restoring data from a cloud provider snapshot, see Restore a Cluster from a Cloud Provider Snapshot


Stop Client Operations during Restoration

You must ensure that the Atlas cluster does not receive client requests during restoration. You must either:

  • Restore to a new Atlas cluster and reconfigure your application to use that new cluster once the new deployment is running, or
  • Ensure that the source Atlas cluster cannot receive client requests while you restore data.

Restore a Cluster

To restore a cluster:

  1. Click Backup in the left-hand navigation.

    The Overview lists the project’s clusters. If the cluster has backup enabled, its Status is Active. If the cluster has backup disabled, its Status is Inactive.

  2. Select a cluster’s snapshot to use for the restore.

    Hover over the Active status of the cluster and click Restore or Download.

    Alternatively, you can click the ... button for the cluster and select the Restore.

  3. Follow the prompts to restore your cluster.

    You may choose to:

    • Download your backup data via HTTPS and restore manually.

      - or -

    • Have Atlas restore to a selected cluster. Atlas can only restore to a cluster of the same type (i.e. replica set to replica set or sharded cluster to sharded cluster).


      The restore process requires downtime for the target cluster.


      The MongoDB versions must also be compatible. For instance, you cannot restore from a snapshot of a 4.0 cluster to a 3.6 or earlier cluster.

      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 Project Owner
      Cloud Manager

      One of the following Cloud Manager roles:

      When prompted for a destination cluster, select the Cloud Manager project and then select a cluster belonging to that project.

  4. Restart your application and ensure it uses the new target cluster.