-
MongoDB node discovery operation fails
A MongoDB node discovery operation fails with errors.
Article ID: 64418
-
MongoDB Backup Job Goes to Pending State
A MongoDB backup job goes to the Pending state.
Article ID: 57009
-
A MongoDB backup job goes to pending state with errors
Article ID: 64535
-
IntelliSnap Backup Copy Operation Fails
An IntelliSnap backup copy operation fails for the hardware array.
Article ID: 56877
-
A MongoDB snapshot backup operation fails with errors.
Article ID: 64536
-
A scheduled backup of MongoDB operation logs fails.
Article ID: 56966
-
A MongoDB restore operation fails to bring up the nodes during recovery.
Article ID: 64526
-
MongoDB Server Fails to Start After a Data Restore Operation
A MongoDB server fails to start after a restore operation.
Article ID: 56866
-
A MongoDB server fails to stop automatically and remove existing data on a destination cluster.
Article ID: 67567
-
The Software Does Not Populate Client Names after a Node Discovery Operation
Symptom
The Commvault software does not display the client names on the Details tab of the Instance Properties dialog box after a node discovery operation.
Cause
The CommCell Console client host name might be different from the host names of the members in the replica set.
Resolution
You can perform either of the following operations to address the issue:
-
Change the CommCell Console client host name to match the MongoDB host replica set members.
-
Change the replica set member host name to match the CommCell Console client host name.
-
-
MongoDB granular recovery fails on nodes that has MongoDB installed
For more information, see KB article 75665.
-
MongoDB restore fails when journalCompressor option is not available in the Commvault configuration file
For more information, see KB article 78149.