Restoring a Collection or a Database in a MongoDB Cluster to to a Different Cluster (Out of Place)

You can restore a collection or a database in a MongoDB cluster to a different cluster (out of place).

Before You Begin

• Verify that the MongoDB system meets the following requirements for out-of-place restores:

  • In a sharded cluster environment, the source and destination shard configurations must be the same.

  • The destination must have the same version or a more recent version of MongoDB than the source.

• Verify that the MediaAgent that hosts the 3DFS server meets the requirements for 3DFS.

• To restore to a Windows MongoDB cluster, verify that the UNIX MediaAgent and the pseudoclient master node are in the same domain. On the UNIX MediaAgent, install the wbinfo program using the samba-winbind-clients RPM package.

• Provide user credentials to access the share exported to the Windows MongoDB cluster.

• Verify that the backup copy job is completed.

• If there is a firewall between the MongoDB node and the MediaAgent, verify the following ports are open:

  • For the MediaAgent on a Windows computer, open 111, 2049, and 2050.

  • For the MediaAgent on a Linux computer, open 111 and 2049.

• To specify additional arguments to the mongodump process that is started during granular recovery, set the sGranularRestoreMongodumpArgs additional setting.

• To specify additional arguments to the mongorestore process that is started during granular recovery, set the sGranularRestoreMongorestoreArgs additional setting.

Procedure

1. From the navigation pane, go to Protect > Big data.

   The Big data page appears.

2. In the row for the cluster, click the action button , and then click Restore.

   The Backup content page appears.

3. From the list beside the Restore button, select Restore collections.

4. Select the database or a collection to restore, and then click Restore.

   The Restore options dialog box appears.

5. From the Destination cluster list, select a different cluster for out of place restore.

   By default, the current cluster is selected as the destination.

   Note: During a granular restore, a MongoDB staging server is started automatically and does not have the TLS or authentication enabled on it. After the restore operation is complete, the server is deleted.

6. To perform a point-in-time restore between the duration of incremental backups, beside Apply oplog until, enter the backup time.

7. If the database or collection with the same name already exists in the destination cluster and you do not want to overwrite it, clear the Unconditionally overwrite if it already exists check box.

8. Click Restore.

   The Confirm restore dialog box appears.

9. Click Yes.