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™ Deduplication Guide
  3. Troubleshooting
  4. About legacy logging
Veritas NetBackup™ Deduplication Guide

About legacy logging

In NetBackup legacy debug logging, a process creates log files of debug activity in its own logging directory. By default, NetBackup creates only a subset of logging directories, in the following locations:

Windows

install_path\NetBackup\logs
install_path\Volmgr\debug

UNIX

/usr/openv/netbackup/logs
/usr/openv/volmgr/debug

To use legacy logging, a log file directory must exist for a process. If the directory is not created by default, you can use the Logging Assistant or the mklogdir batch files to create the directories. Or, you can manually create the directories. When logging is enabled for a process, a log file is created when the process begins. Each log file grows to a certain size before the NetBackup process closes it and creates a new log file.

You can use the following batch files to create all of the log directories:

  • Windows: install_path\NetBackup\Logs\mklogdir.bat

  • UNIX: /usr/openv/netbackup/logs/mklogdir

More information

See the NetBackup Commands Reference Guide for a complete description about the mklogdir command.

Feedback

Was this page helpful?
Previous

Examples of using vxlogview to view unified logs

Next

Creating NetBackup log file directories for MSDP

Feedback

Was this page helpful?