You can restore an entire MongoDB cluster to its current location (in place).
After the data is restored to all the servers in the source cluster, replica sets are initiated, and then all the secondary nodes are added to the corresponding replica set automatically.
Note: If the authentication is disabled on the destination MongoDB server, the loopback IP (127.0.0.1/localhost) must be a part of the bind_ip list to automatically shutdown the server. Otherwise, you will need to manually shutdown the server.
Before You Begin
If you scheduled oplog dump backups, disable them.
From the navigation pane, go to Protect > Big data.
The Apps page appears.
In the row for the cluster, click the action button , and then click Restore.
The Backup content page appears.
Select the content that you want to restore, and then click Restore.
The Restore dialog box appears.
On the In place tab, click Submit.
By default, the Stop MongoDB services check box is enabled to automatically shut down the MongoDB servers and clean up the data directories as part of the restore operation.
Note: If the Stop MongoDB services check box is disabled, then user has to manually shut down the servers and clean up the dbPath before submitting the restore operation. In addition, on Linux, if there are any symbolic links to dbPath or under dbPath, they must not be removed.
For sharded clusters, start the mongo routing service (mongos) on the required nodes:
mongos --config <path-to-config>