Restore Overview

To restore a deployment from a backup, select a snapshot or point in time from which you want to restore your database. Cloud Manager provides you with the files from which you can restore your database.

You can restore a single MongoDB database, a replica set, or a sharded cluster. You may select to restore from:

  • An existing snapshot,
  • A specific point in time by selecting:
    • A specific date and time,
    • A specific oplog timestamp, or
    • A specific sharded cluster checkpoint.

If you are restoring from a point in time, you must download the MongoDB Backup Restore Utility to your target host. The MBRU requests and applies oplog entries between the latest complete snapshot and the point in time you chose.


For sharded clusters, enable checkpoints before restoring to a point between snapshots.

You can restore your backup in one of two ways:

You may cancel a restore by going to the Backup > Restore History tab and clicking on Cancel.

Automated Restore

If you choose to have Cloud Manager automation restore your backup, the Automation Agent removes all existing data from the target hosts and replaces that data with new backup data from your snapshot.


To perform automated restores, you must have:

  • An Automation Agent installed on the source and all target hosts.

  • A Monitoring Agent on the target deployment that can connect to all hosts in the target deployment.

  • The Backup Admin and Automation Admin roles in Cloud Manager.

  • A target cluster whose featureCompatibilityVersion is greater than or equal to the source cluster’s featureCompatibilityVersion.


    Run the following command to retrieve the featureCompatibilityVersion of a given host:

    db.adminCommand( { getParameter: 1, featureCompatibilityVersion: 1 } )

    The featureCompatibilityVersion of each host in the target cluster must be greater than or equal to the featureCompatibilityVersion of any host in the source cluster.

    See setFeatureCompatibilityVersion for complete documentation on changing the featureCompatibilityVersion flag.

  • The following compatibility matrix lists the supported source cluster FCV of each MongoDB version. The MongoDB version of each host in the target cluster must support the FCV of the snapshot of the source cluster.

    Source Cluster FCV MongoDB 3.2 MongoDB 3.4 MongoDB 3.6

Restore to Different Project

You can choose to restore to a cluster of a different project:

  • To restore to another Cloud Manager project, you must have Automation Admin or Backup Admin roles for the target project.
  • To restore to another MongoDB Atlas project, you must have Project Owner role for the target project.

Potential Causes for Automated Restore Failure

An automated restore can fail when certain storage settings of the backup’s database and target database do not match:

No method exists to check for mismatches before attempting a restore. If a restore attempt fails, Cloud Manager displays any mismatched settings. If you still want to restore the backup’s database, fix the settings in the target database that do not match backup’s database, then retry the restoring the backup’s database.

Restore Procedures

To perform an automated restore, see the procedure for the deployment you want to restore:

Manual Restore


To perform manual restores, you must have the Backup Admin role in Cloud Manager.


Restore File Format

Cloud Manager provides each snapshot as an uncompressed (.tar) archive containing a complete copy of the data directory.

File Delivery Methods

With a manual restore, Cloud Manager can deliver the snapshots in two ways:

  • Provide a link to download the snapshots through HTTP.

  • Transfer the snapshots to a target directory on a target host that you choose using SCP.


    If you use SCP, you may choose to transfer the individual database files instead of the snapshot as an archive file.


    You need to generate a key pair before using SCP. SCP transfers files faster than HTTP.


    Microsoft Windows does not include SCP. Installing SCP is outside the scope of this manual.

Manual Restore Procedures

To perform a manual restore, see the procedure for the deployment you want to restore: