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™ Logging Reference Guide
  3. Using logs
  4. About legacy logging
  5. How to control the amount of information written to legacy logging files
Veritas NetBackup™ Logging Reference Guide

How to control the amount of information written to legacy logging files

You can set legacy logging levels to increase the amount of information that NetBackup processes write in the logs.

The following settings affect legacy logging, except media and device management.

  • Increase the Global logging level, which also affect unified logging.

  • On UNIX, add a VERBOSE entry in the /usr/openv/netbackup/bp.conf file.

    If you enter VERBOSE without a value, the verbose value defaults to 1. For more log detail, enter VERBOSE = 2 or a higher value. This setting affects legacy logging only.

    Warning:

    High verbose values can cause debug logs to become very large.

  • Set the logging level for individual processes.

    Also, you can set the logging level of an individual process to a negative value in the bp.conf file as follows:

    <processname>_VERBOSE = -2 completely disables logs for the corresponding process.

Media and device management legacy logging has two levels: not verbose (the default) and verbose. To set the verbose (higher) level, add the word VERBOSE to the vm.conf file. Create the file if necessary. Restart ltid and vmd after you add the VERBOSE entry. The vm.conf file is located in the following directory:

Windows

install_path\Volmgr\

UNIX

/usr/openv/volmgr/

Feedback

Was this page helpful?
Previous

Directory names for legacy debug logs for media and device management

Next

About limiting the size and the retention of legacy logs

Feedback

Was this page helpful?