Restore a Cluster from a Legacy Backup Snapshot

Click Legacy Backup in the left navigation.

Choose the cluster to restore.

The Overview tab on the Legacy Backup page lists the project's clusters.

• If backup is enabled for the cluster, the Status is Active.
• If backup is disabled for the cluster, the Status is Inactive.

To begin restoring a cluster either:

• Hover over the Active status of the cluster and click Restore or Download or
• From the menu next to the cluster select Restore.

Select the restore point.

1. Choose the point from which you want to restore your backup.

   Restore Type	Description	Action
   Snapshot	Allows you to choose one stored snapshot.	Select an existing snapshot to restore.
   Point In Time	Creates a custom snapshot that includes all operations up to but not including the selected time. By default, the Oplog Store stores 24 hours of data. Example If you select 12:00, the last operation in the restore is 11:59:59 or earlier. Important Continuous Cloud Backup Timeframe Limits You cannot perform a continuous cloud backup that covers any time prior to the latest backup resync. For sharded clusters running FCV 4.0 or earlier, you must enable cluster checkpoints to perform a PIT restore on a sharded cluster. If no checkpoints that include your date and time are available, Atlas asks you to choose another point in time. For sharded clusters running FCV 4.2 or later, you can restore from any point in time within the duration of the oplog.	Select a Date and Time.
   Oplog Timestamp	Important Replica Sets and Sharded Clusters running FCV 4.2 Only You can't use this backup point objective with Sharded Clusters running FCV 4.0 or earlier. Creates a custom snapshot that includes all operations up to and including the entered Oplog timestamp. The Oplog Timestamp is represented as two fields: Timestamp timestamp in the number of seconds that have elapsed since the UNIX epoch Increment Order of operation applied in that second as a 32-bit ordinal.	Type an Oplog Timestamp and Increment. Run a query against local.oplog.rs on your replica set to find the desired timestamp.

2. Click Next.

db.getSiblingDB('local').oplog.rs.find().sort({$natural:-1}).limit(1).pretty()

{
  "ts": Timestamp(1537559320, 1),
  "h": NumberLong("-2447431566377702740"),
  "v": 2,
  "op": "n",
  "ns": "",
  "wall": ISODate("2018-09-21T19:48:40.708Z"),
  "o": {
    "msg": "initiating set"
  }
}

Choose to restore the files to another cluster.

1. Click Choose Cluster to Restore to.

2. Complete the following fields:

   Field	Action
   Project	Select a project to which you want to restore the snapshot.
   Cluster to Restore to	Select a cluster to which you want to restore the snapshot. Atlas must manage the target replica set. Warning Automation removes all existing data from the cluster. All backup data and snapshots for the existing cluster are preserved.

2. Click Restore.

   Atlas notes how much storage space the restore requires.

Click Restore.

Use your preferred archive utility to extract the archive and access the data files.

Atlas compresses the snapshot into a .tar.gz file. This archive includes the snapshot and the mongod logs.

1. Extract the files in the archive.

   Example

   The following command uses the tar utility to extract a tar``archive with ``gzip compression.

   tar -xvzf ~/Downloads/mongodb-snapshots/my-cluster-snapshot.tar.gz

2. Access the data files by starting a mongod instance on the host and pointing it at the extract directory using the --dbpath option.

   Example

   The following command starts a mongod instance using the extracted data file directory:

   mongod --dbpath ~/Downloads/mongodb-snapshots/my-cluster-snapshot/