MongoDB Ops Manager transaction log (TLOG) backup continuity considerations
MongoDB Ops Manager transaction log (oplog) backups rely on continuous oplog metadata to support point‑in‑time recovery. NetBackup validates oplog continuity during backup and restore operations to ensure recovery consistency.
If any oplog or incremental backup fails, the continuity of the oplog chain required for point‑in‑time recovery may be broken.
MongoDB Ops Manager logs may report messages such as:
Observed non‑continuous sets of oplog files
Gap overlap observed for this set of oplog files
After an oplog or incremental backup failure, subsequent oplog or incremental backups (including retry and auto‑retry operations) may report success; however, successful completion does not indicate point‑in‑time recoverability if oplog continuity was previously broken. .
Until a new Full backup is performed, the affected backup chain cannot be used for log‑based (point‑in‑time) recovery.
Snapshot‑based restores (Full or Incremental without logs) remain available.
Operational guidance
If an oplog or incremental backup failure occurs:
- Treat the current Full + oplog backup chain as unavailable for point‑in‑time recovery.
- Perform a new Full backup to establish a new recovery baseline.
- Review MongoDB Ops Manager logs for oplog continuity or retention warnings.
- Verify oplog retention sizing and ensure backup schedules align with the required recovery window.
Warning:
NetBackup validates oplog continuity but does not generate, repair, or reconcile MongoDB oplog metadata. Continuous oplog retention and accurate metadata reporting by MongoDB Ops Manager are required for successful log‑based recovery.