Veritas NetBackup™ Logging Reference Guide
- Using logs- About logs
- About UNIX system logs
- About log retention in NetBackup
- About limiting the size of unified and legacy logs
- About unified logging- Gathering unified logs for NetBackup
- Types of unified logging messages
- File name format for unified logging
- Originator IDs for the entities that use unified logging
- About changing the location of unified log files
- About rolling over unified log files
- About recycling unified log files
- About using the vxlogview command to view unified logs
- About query strings used with the vxlogview command
- Examples of using vxlogview to view unified logs
- Examples of using vxlogmgr to manage unified logs
- Examples of using vxlogcfg to configure unified logs
 
- About legacy logging- UNIX client processes that use legacy logging
- PC client processes that use legacy logging
- File name format for legacy logging
- Directory names for legacy debug logs for servers
- Directory names for legacy debug logs for media and device management
- How to control the amount of information written to legacy logging files
- About limiting the size and the retention of legacy logs
- Configuring the legacy log rotation
 
- About global logging levels
- Setting retention limits for logs on clients
- Logging options with the Windows Event Viewer
- 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- acsssi logging
- bpbackup logging
- bpbkar logging
- bpbrm logging
- bpcd logging
- bpcompatd logging
- bpdbm logging
- bpjobd logging
- bprd logging
- bprestore logging
- bptm logging
- daemon logging
- ltid logging
- nbemm logging
- nbjm logging
- nbpem logging
- nbproxy logging
- nbrb logging
- NetBackup web services logging
- NetBackup web server certificate logging
- PBX logging
- reqlib logging
- robots logging
- tar logging
- txxd and txxcd logging
- vnetd logging
 
- Java-based administration console logging- About the Java-based administration console logging
- Java-based administration console logging process flow
- Setting up a secure channel between the Java-based administration console and bpjava-*
- Setting up a secure channel between the Java-based administration console and either nbsl or nbvault
- Java-based administration console logging configuration on NetBackup servers and clients
- Java-based remote administration console logging on a Windows computer where NetBackup is not installed
- Configuring and gathering logs when troubleshooting Java GUI issues
- Undo logging
 
File name format for legacy logging
NetBackup legacy logging creates debug log files in the following format:
user_name.mmddyy_nnnnn.log
The following items describe the log file name elements:
| user_name | The name of the user in whose context the process runs, as follows: 
 | 
| mmddyy | The month, day, and year on which NetBackup created the log file. | 
| nnnnn | The counter or the rotation number for the log file. When the counter exceeds the setting for number of log files, the oldest log file is deleted. The MAX_NUM_LOGFILES configuration parameter sets the maximum number of a legacy log file per process. | 
The retention of all logs files in the legacy debug log directories is managed by using the following options:
- setting of the NetBackup Host Properties Logging dialog box. The default is 28 days. 
- setting of the NetBackup Host Properties Logging dialog box. 
- The legacy logging settings. 
Any mixture of new and old log file names in a legacy debug log directory is managed according to the setting and the robust logging settings.
More Information