Performing a Restore Operation of a MongoDB Cluster Managed By Ops Manager

To restore the replica set or the sharded cluster managed by the Ops Manager, perform the restore operation.

Before You Begin

• Make a copy of the MongoDB configuration file, especially if the file is in the dbpath directory. The configuration file is required to start the server after the restore operation.

• Verify that, on the General tab of the Restore Options dialog box, to shut down the destination server and to clean up the dbPath directory before the restore operation, the Automatic restore option is selected.

• To schedule operation log dump backups, disable operation log dump backups using the bEnableMongoOpLogDumps additional setting.

• To automatically stop and start the Ops Manager during restore, add the bMongoDbOpsManagerSetup additional setting.

Procedure

1. Perform the MongoDB restore operation.

2. Before the restore is performed, the Ops Manager automation agent is automatically stopped on all the nodes of the replica set or the sharded cluster.

   Example:

   sudo systemctl stop mongodb-mms-automation-agent.service

3. After performing the MongoDB restore operation, the following steps are performed automatically:

   1. The Commvault software shuts down the mongod service on all the nodes of the replica sets, including the config server replica set.

   2. The Commvault software starts the Ops Manager automation agent on all nodes of the replica set or the sharded cluster.

      Example:

      sudo systemctl start mongodb-mms-automation-agent.service