Veritas 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
- 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
Configuring and gathering logs when troubleshooting NetBackup Administration Console issues
After the NetBackup Administration Console is installed, the log levels are configured to gather a detailed set of logs.
The NetBackup Administration Console uses the Debug.properties file to determine which logging level to use:
/usr/openv/java/Debug.properties
install_dir\VERITAS\Java\Debug.properties
The following settings are tuned to enable additional logging:
printcmds=true debugMask=0x00040000
To increase the verbosity to max (which is recommended for troubleshooting), set debugMask to debugMask=0x00160000.
Gather the following NetBackup Administration Console logs from the following pre-existing log directories on the system from which the console was started:
The Java GUI logs are located in the following log directories for root and administrator users:
UNIX:
/usr/openv/netbackup/logs/user_ops/nbjlogs/Windows:
install_directory\netbackup\logs\user_ops\nbjlogs\
The Java GUI logs are located in the following log directories for non-root and non-administrator users, the Java GUI logs are located in the following log directories:
UNIX:
/usr/openv/netbackup/logs/user_ops/nbjlogs/<non-root-username>Windows:
install_directory\netbackup\logs\user_ops\nbjlogs\<non-admin-username>
The administrator needs to create the non-root username directories under the
nbjlogsdirectory using mklogdir -user username -group groupname command which is present in the NetBackup legacy log folder. If these username directories are not created with appropriate write permission for that user, then the users home directory is used for logging. Thenbjlogsfolder is created in the user's home directory first and all logs appear in this folder. If the home directory is not accessible, the logs are redirected to console.On the master server, log on to the NetBackup Administration Console to create the
admin,bpjava-msvc,bpjava-susvc, and bpjava-usvc log directories and enable VERBOSE 5 logging. You do not have to restart the NetBackup daemons for the logging level changes to take effect.For UNIX systems, create the following directories:
/usr/openv/netbackup/logs/admin/usr/openv/netbackup/logs/bpjava-msvc/usr/openv/netbackup/logs/bpjava-susvc/usr/openv/netbackup/logs/bpjava-usvc
In the
/usr/openv/netbackup/bp.conffile add the following lines:ADMIN_VERBOSE = 5 BPJAVA-MSVC_VERBOSE = 5 BPJAVA-SUSVC_VERBOSE = 5 BPJAVA-USVC_VERBOSE = 5
For Windows systems, create the following directories:
install_dir\VERITAS\NetBackup\logs\admininstall_dir\VERITAS\NetBackup\logs\bpjava-msvcinstall_dir\VERITAS\NetBackup\logs\bpjava-susvcinstall_dir\VERITAS\NetBackup\logs\bpjava-usvc
Update the Windows registry at and add the following entries of type DWORD:
ADMIN_VERBOSE = 5 BPJAVA-MSVC_VERBOSE = 5 BPJAVA-SUSVC_VERBOSE = 5 BPJAVA-USVC_VERBOSE = 5
Run the following commands to set up detailed logging for nbatd (OID 18) and nbsl (OID 132). OID 137 (NetBackup libraries) and OID 156 (CORBA/ACE) write to the caller that requires access to either the libraries or CORBA/ACE, as follows:
vxlogcfg -a -p NB -o 18 -s DebugLevel=6 vxlogcfg -a -p NB -o 132 -s DebugLevel=6 vxlogcfg -a -p NB -o 137 -s DebugLevel=6 vxlogcfg -a -p NB -o 156 -s DebugLevel=6
Gather the nbatd and nbsl logs that are located in the following directory paths:
For UNIX:
/usr/openv/logs/nbsl
/usr/openv/logs/nbatd
For Windows:
install_dir\VERITAS\NetBackup\logs\nbsl
install_dir\VERITAS\NetBackup\logs\nbatd
Finally, gather the PBX logs, as follows:
For UNIX: /opt/VRTSpbx/log (gather any logs that cover the current date and time)
For Windows: install_dir\VERITAS\pbx\log