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
- 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
- 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 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
Configuring and gathering logs when troubleshooting Java GUI issues
Once installed, the log levels for the Java-based administration console are configured to gather a detailed set of logs.
The NetBackup Java GUI uses the Debug.properties file to determine which logging level to use.
On UNIX systems, the file is: /usr/openv/java/Debug.properties
On Windows systems, the file is: install_dir\VERITAS\Java\Debug.properties
Specifically, the following settings are tuned to enable additional logging (these are the default values):
printcmds=true debugMask=0x00040000
To increase the verbosity to max (which is recommended for troubleshooting), set debugMask to debugMask=0x00160000.
Gather the following Java console logs from the following pre-existing log directories on the system from which the GUI was started:
UNIX:
/usr/openv/netbackup/logs/user_ops/nbjlogsWindows:
install directory\netbackup\logs\user|ops\nbjlogs
On the master server, log in through the Java-based 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
Edit the
/usr/openv/netbackup/bp.conffile by adding 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 nbatd (OID 18) and nbsl (OID 132) logging. 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 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/time)
For Windows: install_dir\VERITAS\pbx\log