This version of the documentation is archived and no longer supported. To learn how to upgrade your version of MongoDB Ops Manager, refer to the upgrade documentation.
You were redirected from a different version of the documentation. Click here to go back.

Restore from a Specific Point-in-Time using SCP

To restore a snapshot using SCP, the Backup Daemon streams the snapshot to the target snapshot host.

Diagram showing the flow of data when restoring a point-in-time snapshot via SCP using Ops Manager.
  1. The user selects a timestamp:

    • Through the Ops Manager application:
      1. Click on a timestamp.
      2. Submit their request.
    • Through the API:
      1. Find the cluster to restore.
      2. Create new Restore Job for that cluster.
  2. Ops Manager creates a RestoreJob document.

  3. The Backup Daemon service picks up the RestoreJob document.

  4. Backup Daemon service starts streaming the snapshot in the requested format from the Snapshot Store to the target snapshot host. Each Snapshot Store streams its snapshot components through Ops Manager:

    1. A Blockstore streams Blocks.
    2. A S3 Snapshot Store streams the Blocks.
    3. A File System Store streams the Files.
  5. The user downloads the MongoDB Backup Restore Utility from the Ops Manager application to the target snapshot host.


    The MBRU is not unique to each restore. If the utility is installed on the host where the snapshot will be restored, the user does not need to download it again.

  6. The user starts a temporary MongoDB instance on the target snapshot host. The fetched oplog is applied to the snapshot restored to this instance.

  7. The user runs the MBRU to request the oplog.

  8. The MBRU fetches the oplog for the point-in-time snapshot.

  9. The MBRU applies the oplog to snapshot in the temporary MongoDB instance.

  10. The user exports the restored database from the temporary MongoDB instance.