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. Backup
  4. Add a policy
NetBackup™ for MongoDB Ops Manager Administrator's Guide

Add a policy

This section provides information about how to configure a policy to backup the MongoDB Ops Manager assets.

Upgrade behavior for MongoDB Ops Manager backups

If you upgrade to NetBackup 11.2 or later, existing MongoDB Ops Manager policies remain available.

However, backup behavior changes for policies that were created before the upgrade.

  • Policies that used Differential Incremental backups now run as Incremental (INCR) backups.

  • Transaction log (oplog) backups do not continue automatically after the upgrade.

Required action:

To continue transaction log - based backups and point‑in‑time recovery, you must manually edit existing MongoDB Ops Manager policies and change the backup type to Transaction Log (TLOG).

If this change is not made, backups may run successfully, but transaction log recovery will not be available.

  1. On the left pane, click or expand Protection and then click Policies.

  2. Click Add. Create policy page is displayed.

  3. Specify the details for the following tabs:

    • Attributes: Select BigData from the Policy dropdown and then select MongoDB Ops Manager from the workload type dropdown.

    • Schedule: On this tab, configure all the settings required to schedule backup. You can also select Full backup, Differential incremental backup, or Transaction log backup.

      • Full backup: Creates a complete copy of all data for the selected cluster at a specific point in time.

      • Differential incremental backup: Backs up only the data that has changed since the last full backup.

      • Transaction log backup: Backs up transaction log data so that changes made after a backup can be captured.

        Note:

        Operational warning: Point‑in‑time (PIT) restore is supported only with Transaction log (TLOG) backups. PIT restore is not supported with Differential incremental backups (INCR) alone.

    • MongoDB Ops Manager Assets: On this tab, a list of clusters which are protection ready is displayed. Select the required cluster.

  4. Click Create.

Warning:

If the preferred nodes are shared with multiple clusters, adding multiple clusters in the policy may lead to backup failures.

Feedback

Was this page helpful?
Previous

How INCR incremental backups works

Next

Recovery

Feedback

Was this page helpful?