"Could not figure out the client node name to use for the secondary MongoDB Hostname": A MongoDB backup job goes to pending state

Article ID: 64535

Article Type: Troubleshooting

Last Modified: February 19, 2021

A MongoDB backup job goes to pending state with errors.

Symptoms

A MongoDB backup job fails with the following error in the MongoDB.log file on the primary node:

MongoDbIDA::MongoDbBackupCoordinator::populateNodeAndTaskList(472)} {MongoDbIDA::MongoDbBackupCoordinator::GetSecondaryDataPath(331)/W32.1168.(Element not found. (ERROR_NOT_FOUND.1168))-Could not figure out the client node name to use for the secondary MongoDB Hostname [x.x.x.x].

Causes

The host name of the MongoDB nodes configured in the CommCell Console and the replica set are different.

Resolution

Verify that the host name of the MongoDB nodes configured in the CommCell Console and the replica set are identical.