Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ for MongoDB Ops Manager Administrator's Guide
  3. Introduction
  4. Prerequisites and best practice
  5. Snapshot and transaction log (TLOG) considerations
NetBackup™ for MongoDB Ops Manager Administrator's Guide

Snapshot and transaction log (TLOG) considerations

For stable backup and recovery behavior, follow these general guidelines:

  • Perform a full backup at least once a week.

  • Perform incremental backups at least once a day.

  • Once a full backup is started, earlier backups cannot be used as the source for subsequent incremental backups, even if the full backup fails.

  • Transaction log (TLOG) backups should be taken frequently to maintain a reliable point‑in‑time recovery window.

  • During initial setup or when transaction log gaps are detected, take a transaction log backup followed by a full backup.

  • Snapshot creation requires a running cluster with stable data. Snapshots cannot be taken while a restore operation is in progress.

These practices help ensure reliable recovery and minimize the risk of data loss.

Feedback

Was this page helpful?
Previous

Feature flags for NetBackup integration

Next

Add MongoDB Ops Manager workload

Feedback

Was this page helpful?