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.

Back Up Ops Manager

Deploying the Ops Manager Backup Blockstore and Application databases as replica sets is key to protect the databases from failure.

Ensure you configure and deploy your replica sets for failover and redundancy. See Replica Set High Availability and Replica Set Deployment Architectures for more about replica set architecture.

Beyond using MongoDB’s replication capabilities, you can create backups for the Backup Blockstore database and Application database, both for longterm storage of snapshots, and for backing up Ops Manager for disaster recovery purposes.

To restore Ops Manager, you only need backups of the Application database and the Backup Blockstore database. Ops Manager’s other components are stateless: you can rebuild them from the installation package if need be.


Your Backup installation cannot back up Ops Manager. If you wish to use Ops Manager to back up Ops Manager, you will need two Ops Manager installations: one to back up your MongoDB deployment, and another to back up your Ops Manager databases.

Back Up with the Public API

The Ops Manager Public API allows you to programmatically restore snapshots on your desired schedule, and store them offline. Ideally, you should save the backups to a tape drive, appending the new snapshots daily until the drive is full, and then store the drive offsite.

Programmatically restoring snapshots has the same impact on a snapshot as a typical restore.

See the API documentation for how to restore jobs using this method.

This method backs up the snapshots only: you cannot use the backups to restore Ops Manager in the event that a Blockstore database is lost.

Shut Down and Back Up Ops Manager

To perform a full backup of all snapshots contained in Ops Manager, including the point-in-time restores:

  1. Shut down the Ops Manager application service
  2. Shut down the Ops Manager application databases
  3. Shut down the Ops Manager backup databases.
  4. If you backed up using blockstores, back up the file systems that store the application and backup databases (and/or files) while they are offline.
  5. If you backed up using file system stores, backup the snapshot files on the file system.

The Shut Down and Back Up approach has the advantage of providing all of Ops Manager’s backup snapshots and the point-in-time restores that it stores. However, the process involves significant downtime and during the shut down, Ops Manager is completely unavailable as are monitoring and automation capabilities. As such, if a failure occurs in one of your MongoDB instances, you may lose the data that Ops Manager did not back up prior to shutdown nor are you alerted of that fact because monitoring is unavailable.