MongoDB incremental backup failed

Hi Laxman,

Is the issue still persisting? Since we don't have access to the logs, I am answering based on my experience.

Answer for Query 1:

We need to Compare the exact mongodump invocation:
From the client logs (CVMongoDBUtil.log / MongoDBCtrl.log) capture the exact mongodump command Commvault ran and its rc/out. Compare it to the manual command you ran. Look for differences in path, --config, --ssl, --sslCAFile, --sslPEMKeyFile, or other arguments.
Verify the binary path and version Commvault is configured to use:
Confirm the MongoDB bin path configured in the Commvault MongoDB instance matches the mongodump you ran manually.
Confirm the mongodump version supports the --config option and (if Commvault uses a config file for credentials) is >= 100.3 when required.

Commvault is invoking mongodump differently than your manual test (different binary path, different user environment, or different arguments), or the mongodump used by Commvault is incompatible with how Commvault passes credentials/config.

Answer for Query 2:

There is a known issue with the Routing Service restore option in versions prior to 11.40.

Could you please upgrade the client agent version to 11.40 and applying the additional setting 'bMongoDbStartAsProcess'

Use the setting "bMongoDbStartAsProcess" when the mongo server is running with any custom options. https://documentation.commvault.com/additionalsetting/bmongodbstartasprocess.html

After performing above please resubmit the restore operation and see if it helped in your environment.

I advise creating a support ticket to have a deeper look into this.

Regards,

Sarvesh Anand