About restoring MongoDB data in a high availability setup on an alternate client
Use this information when the client (MongoDBnode-port) that is defined in the Clients tab of the backup policy is not available and you want 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 in the same MongoDB cluster
Complete the following steps:
Rename the application server and its nodes and set the value for the alternate application server.
In the web UI select the tab > and use or 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 done from the MongoDB node endu79-26055. In this scenario, as part of restore and recovery, append endu79:26055 as follows:ALT_APPLICATION_SERVER=endu79:26055.