Navigation
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

To restore a snapshot using HTTP, Ops Manager creates and displays a download link to the appropriate snapshot in snapshot storage.

After clicking the download link, Ops Manager streams the snapshot to the target snapshot host.

Note

PIT restores include points in time and oplog timestamps. PIT restores include checkpoints for sharded clusters running FCV of 4.0 or earlier.

Diagram showing the flow of data when restoring a snapshot via HTTP 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. Ops Manager sets the RestoreJob document status to Transferring… and starts streaming the snapshot in the requested format from the Snapshot Store to Ops Manager. Each Snapshot Store streams its snapshot components through Ops Manager:

    1. A blockstore streams blocks.
    2. A S3 snapshot store streams the blocks.

  4. With the status set to Waiting for Customer…, Ops Manager creates a URL.

  5. The user clicks the get link link, then Download in the Ops Manager application to download the snapshot.

  6. The user downloads the MongoDB Backup Restore Utility from the Ops Manager application to the target snapshot host.

    Note

    The MBRU can be used with any restore. If the utility is installed on the host where you want to restore the snapshot, the user doesn’t need to download it again.

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

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

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

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

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

© MongoDB, Inc 2008-present. MongoDB, Mongo, and the leaf logo are registered trademarks of MongoDB, Inc.