Troubleshooting MongoDB Ops Manager issues
For more information about MongoDB Ops Manager troubleshooting, verify the following details:
Verify the Job Details section of the job on the Activity monitor page for the failures.
Verify the following logs:
Auto-discovery log files (/usr/openv/logs)
ncfnbcs
Backup log files (/usr/openv/netbackup/logs)
bpbrm
nbaapidiscv
bpbkar
Recovery log files (/usr/openv/netbackup/logs)
bprd
nbaapireq_handler
tar
Asset/Backup/Recovery API (/usr/openv/logs)
nbwebservice
Note:
For API call failures, also check MongoDB Ops Manager logs such as mms0.log and mms0-access.log.
In earlier releases, transaction log backups were referred to as oplog backups. In this release, they are referred to as TLOG (transaction log) backups.
Workaround and guidance
Avoid running incremental backups immediately after rapid data or schema changes
Allow sufficient time for data to stabilize and synchronize across replica set nodes before starting incremental backups
When possible, use FULL backups or Transaction log (TLOG) backups instead of relying solely on incremental backups until this issue is resolved