Veritas NetBackup™ Logging Reference Guide
- Using logs
- About unified logging
- About legacy logging
- About global logging levels
- Troubleshooting error messages in the NetBackup Administration Console
- Backup process and logging
- Media and device processes and logging
- Restore process and logging
- Advanced Backup and Restore Features
- Storage logging
- NetBackup Deduplication logging
- OpenStorage Technology (OST) logging
- Storage lifecycle policy (SLP) and Auto Image Replication (A.I.R.) logging
- Snapshot technologies
- Locating logs
- Java-based administration console logging
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.
This setting also affects unified logging.
On UNIX, add a VERBOSE entry in the /usr/openv/netbackup/bp.conf file.
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.
See more about logging properties in the NetBackup Administrator's Guide, Volume I.
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. This entry affects logging levels in the Event Viewer Application and System log. The
vm.conf file is located in the following directory: