Restoring MongoDB data in a high availability setup to an alternate client
If a client (MongoDBnode-port) that is defined in the backup policy is not available use the following procedure to restore to a different client in the same MongoDB cluster (MongoDBnode-port).
In a high availability setup, you can restore the MongoDB data as follows:
Sharded MongoDB cluster
Restore to an alternate config server in the same MongoDB cluster.
Replica set MongoDB cluster
Restore to an alternate node of the replica set that is in the same MongoDB cluster.
To restore MongoDB data in a high availability setup to an alternate client
- Open the web UI.
- On the left, click Recovery. On the Regular recovery card, click Start recovery.
- Rename the application server and its nodes and set the value for the alternate application server.
Select Restore individual directories and files to different locations and click Edit file paths to add the alternate application servers.
If the application_server (Host1-port1) is different from the target application_server (Host2:Port2), the rename entry must contain ALT_APPLICATION_SERVER=Host2:Port2.
In the following example, the Source client that is defined in the backup policy is endu79-26050, and the backup was performed by the MongoDB node endu79-26055. In this scenario, as part of restore and recovery, append endu79:26055 as follows:ALT_APPLICATION_SERVER=endu79:26055.