NetBackup™ for MongoDB Ops Manager Administrator's Guide

Last Published:
Product(s): NetBackup (11.1)

Errors and recommended actions

The following table describes the problem that might occur.

Table: Error and recommended actions

Error message or cause

Explanation and recommended action

Post changing the preferred nodes, running incremental backup process fails.

Error: Backup of client exited with status 112.

This is a known issue with MongoDB, in case of any topology change.

Take a incremental backup of <PrefNode1> node. Change the preferred node from <PrefNode1> to <PrefNode2> and again take a incremental backup.

Note:

The Ops Manager point-in-time restore might have oplog gaps in some situations.

oplog is the MongoDB operation log.

The backup fails with an error.

Recommended action:

  • Take a full backup post topology changes.

Running backup on old media server.

Error: The backup selection fails with an error.

Cohesity recommends upgrading the media server to latest.

Run full and incremental backup on the RECOVERING cluster. Then recovery the cluster and run incremental backup.

Warning: The executed incremental backup, post cluster recovery, is not accurate.

Cohesity recommends to run full backup post cluster recovery.

Differential Incremental backup fails with error code 3298.

The error is triggered under specific conditions involving large-scale data changes. The root cause is traced to Oplog Snapshot API within MongoDB Ops Manager.