NetBackup™ Logging Reference Guide
- Using logs
- About logging
 - Logging levels
 - Log retention and log size
 - Changing the logging levels
 - 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
 - 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
 - Limit the size and retention of legacy logs
 - Accessibility of the legacy logs
 
 - Setting retention limits for logs on clients
 - UNIX logging with syslogd
 - Logging options with the Windows Event Viewer
 
 - 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
 - NetBackup secure communication logging
- About NetBackup secure communication logging
 - Tomcat logging
 - NetBackup web services logging
 - Command-line logging
 - NetBackup cURL logging
 - Java logging
 - Embeddable Authentication Client (EAT) logging
 - Authentication Services (AT) logging
 - vssat logging
 - NetBackup proxy helper logging
 - NetBackup proxy tunnel logging
 - PBX logging
 - Sending secure communication logs to Veritas Technical Support
 
 - Snapshot technologies
 - Locating logs
- Overview of NetBackup log locations and processes
 - acsssi logging
 - bpbackup logging
 - bpbkar logging
 - bpbrm logging
 - bpcd logging
 - bpcompatd logging
 - bpdbm logging
 - bpjobd logging
 - bprd logging
 - bprestore logging
 - bptestnetconn logging
 - bptm logging
 - daemon logging
 - ltid logging
 - nbemm logging
 - nbjm logging
 - nbpem logging
 - nbproxy logging
 - nbrb logging
 - NetBackup Vault logging
 - NetBackup web services logging
 - NetBackup web server certificate logging
 - PBX logging
 - reqlib logging
 - Robots logging
 - tar logging
 - txxd and txxcd logging
 - vnetd logging
 
 - NetBackup Administration Console logging
- NetBackup Administration Console logging process flow
 - Enabling detailed debug logging for the NetBackup Administration Console
 - Setting up a secure channel between the NetBackup Administration Console and bpjava-*
 - Setting up a secure channel between the NetBackup Administration Console and either nbsl or nbvault
 - NetBackup Administration Console logging configuration on NetBackup servers and clients
 - Logging Java operations for the NetBackup Remote Administration Console
 - Configuring and gathering logs when troubleshooting NetBackup Administration Console issues
 - Undo logging
 
 - Using the Logging Assistant
 
File name format for legacy logging
NetBackup legacy logging creates debug log files in the following format:
user_name.mmddyy_nnnnn.log
The file names include the following 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 new folder structure for non-root or non-admin invoked process logs is created under process log directory name.
For example,
/usr/openv/netbackup/logs/tar/root.031020_00001.log
/usr/openv/netbackup/log/tar/usr1/usr1.031020_00001.log
Here, for non-root user usr1, a non-root username directory is created under the respective NetBackup processes.