You can restore only the data to the MongoDB cluster, and then follow the manual procedure to start the servers and the replica sets.
Before You Begin
If you have oplog dump backups enabled on the destination cluster, 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 all the content, and then click Restore.
The Restore dialog box appears.
On the Restore to files tab, do the following:
From the Destination cluster list, select a different cluster.
By default, the source cluster is selected as the destination.
To restore the oplogs, in the Staging path for oplog dumps box, enter the path to restore the oplogs to.
By default, the oplog backups are restored to the Job Results directory on each node.
To provide inputs for the primary member in each replica set, under Replica set options, click the edit button.
The Provide inputs for primary member dialog box appears.
Enter the new values for the primary member, and then click Save.
To add a secondary member for each replica set, under Replica set options, click the add button.
The Provide inputs for secondary member dialog box appears.
Enter the values for the secondary member, and then click Save.
By default, the Automatic Restore check box is selected, to automatically clean up the data directories as part of the restore. Before you submit the restore, you must stop the MongoDB services on all the destination clients.
Note: If the Automatic Restore check box is cleared, then before you submit the restore, you must manually clean up the dbPath.
What to Do Next
After restoring the MongoDB cluster to disk, you must manually start and recover the sharded cluster or a replica set. For more information, see Performing a Manual MongoDB Restore Operation for a Sharded Cluster or Performing a Manual MongoDB Restore Operation for a Replica Set.