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. Veritas NetBackup™ Administrator's Guide, Volume I
  3. Section V. Configuring backups
  4. About the NetBackup relational database
  5. About backup and recovery procedures
  6. Database transaction log
Veritas NetBackup™ Administrator's Guide, Volume I

Database transaction log

The transaction log for the NetBackup database is necessary for recovering the database. It is automatically truncated after a successful catalog backup.

The transaction log, NBDB.log, is located by default in the following directory:

On Windows: install_path\NetBackupDB\data\NBDB.log

On UNIX: /usr/openv/db/data/NBDB.log

The transaction log continues to grow until it becomes truncated. Catalog backups must run frequently enough so that the transaction log does not grow to fill the file system.

In addition to the default transaction log, a mirrored transaction log can be created for additional protection of NBDB.

The directory for the mirrored log should not be the same as the directory for the default transaction log. Ideally, the mirrored log should be located on a file system on a different physical disk drive.

If BMR is installed, a transaction log for BMRDB is also created by default in:

On Windows: install_path\NetBackupDB\data\BMRDB.log

On UNIX: /usr/openv/db/data/BMRDB.log

It has an optional mirrored log in the following location:

On Windows: mirrored_log_directory\BMRDB.m.log

On UNIX: mirrored_log_directory/BMRDB.m.log

The BMRDB transaction logs are backed up and truncated during the catalog backup along with the NBDB transaction logs.

Note:

If a catalog backup is not run, the logs are not truncated. Truncation must be managed in this manner as it is critical to recovery of the database.

Feedback

Was this page helpful?
Previous

About backup and recovery procedures

Next

About catalog recovery

Feedback

Was this page helpful?