Recovering the MongoDB Database Using the Mongo Recovery Assistant Tool for Windows

You can recover your MongoDB persistant data from a disaster recovery (DR) backup to a Windows Web Server host using the Mongo Recovery Assistant tool for Windows.

The tool is primarily used in the following scenarios:

  • To rebuild a MongoDB database in the event of a disaster

  • To upgrade or move the MongoDB database to a new hardware

Before You Begin

  • Make sure that you have the latest version of the DR backup (SET_XXX folder) in the destination Web Server host (where MongoDB package is installed).

    • If you have the DR backup files in the network location, copy the files to the local disk on the Web Server host.

    • If the latest copy of the DR backup metadata does not exist in the export location, you must retrieve the metadata from the backup media. For more information on retrieving DR backups from media, See Retrieving Disaster Recovery (DR) Backups from Media.

Procedure

  1. Stop services on all the Web Server host, if it is active. For more information on stopping services, see Stopping a Service for Windows, and Commands to Control Services on UNIX Clients for UNIX.

  2. On the destination computer (where MongoDB package is present), go to the {software installation path}\MongoDB\Util and double-click the CVMongoRecoveryAssistant.exe.

    The Mongo Recovery Assitant dialog box is displayed.

  3. Click Next.

  4. If there are multiple instances, select the instance on which you want to perform the restore operation and then click Next.

  5. In the Enter the path to the database dump folder box, enter or browse the name of the Disaster Recovery folder where the dump files are located, and then click Next.

    Make sure that the dump files are available on the local disk of the Web Server host.

  6. Review the summary and then click Start Recovery.

  7. Click Finish.

Note

If you have any unfinished restore, you can select either Resume restore or Clean up unfinished restore and start over.

What To Do Next

Restart all the Commvault services on all the Web Server hosts that were previously stopped.

Loading...