Navigation
This version of the documentation is archived and no longer supported. It will be removed on 01 March 2021. 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

On this page

To restore a snapshot from a point in time, you must direct Ops Manager to restore to another managed cluster or generate a download of the snapshot data. A restore to another managed cluster can be called either a targeted or automatic restore. A restore to create an archive of the database or an unmanaged cluster can be called a downloaded or manual restore.

This workflow steps through the backend process for both an automatic restore and a manual restore. Automatic restores omit the optional steps. Manual restores follow all steps.

To learn how to restore snapshots, see Next Steps.

Note

PIT restores include points in time, oplog timestamps, and checkpoints.

Workflow

Diagram showing the flow of data when restoring a point-in-time snapshot via HTTP using Ops Manager.
1

Select a timestamp.

Select a timestamp to which you want to restore your data:

  • Through the Ops Manager console:
    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

Backup Daemon picks up the RestoreJob document.

The Backup Daemon service:

  1. Picks up the RestoreJob document.
  2. Sets the status of this RestoreJob to Waiting for Customer….
4

Ops Manager creates a URL.

5

Optional: Download the snapshot.

If you aren’t restoring the data to another cluster that Automation manages:

  1. Click the get link link.
  2. Click Download.
6

Ops Manager streams the snapshot.

In streaming the snapshot, Ops Manager:

  1. Sets the RestoreJob document status to Transferring….
  2. 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.
7

Optional: Download the MongoDB Backup Restore Utility.

If you aren’t restoring the data to another cluster that Automation manages, download the MongoDB Backup Restore Utility from the Ops Manager application to the target snapshot host.

Note

The MBRU works with any restore. If the utility is installed on the host where you want to restore the snapshot, the you don’t need to download it again.

8

Optional: Start a temporary MongoDB instance on the target snapshot host.

If you aren’t restoring the data to another cluster that Automation manages, start a temporary MongoDB instance on the target snapshot host. The MBRU applies the fetched oplog to the snapshot restored to this instance.

9

Optional: Request the oplog.

  • The target host should run the MBRU to request the oplog.
  • If you aren’t restoring the data to another cluster that Automation manages, you need to run the MBRU to request the oplog
10

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

11

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

12

Optional: user exports the restored database from the temporary MongoDB instance.