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
 - About limiting the size and the retention of legacy logs
 - Configuring the legacy log rotation
 
 - 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
 
Deduplication configuration logs
The following are the deduplication configuration logs.
NetBackup Administration Console for Windows wizard logging:
wingui (OID: 263):
# vxlogcfg -a -p 51216 -o 263 -s DebugLevel=6 -s DiagnosticLevel=6
On the applicable MSDP storage pool, edit
install_path\etc\puredisk\spa.cfgandinstall_path\etc\puredisk\contentrouter.cfg. Specify Logging=full,thread and then restart the spad and spoold services for the changes to take effect.nbsl (OID: 132):
vxlogcfg -a -p 51216 -o 132 -s DebugLevel=6 -s DiagnosticLevel=6
dsm (OID: 178):
vxlogcfg -a -p 51216 -o 178 -s DebugLevel=6 -s DiagnosticLevel=6
Storage service (turn on STS logging, to log the msdp/pdplugin responses to NetBackup):
# vxlogcfg -a -p 51216 -o 202 -s DebugLevel=6 -s DiagnosticLevel=6
Remote Monitoring & Management Service:
# vxlogcfg -a -p 51216 -o 222 -s DebugLevel=6 -s DiagnosticLevel=6
tpcommand (
...\volmgr\debug\tpcommand)storage_directory\log\msdp-config.log
Command-line configuration logging:
Administration log for nbdevquery (add storage_server)
tpcommand log for tpconfig (add credentials) (
...\volmgr\debug\tpcommand)storage_directory\log\pdde-config.logStorage service (turn on STS logging, to log the msdp/pdplugin responses to NetBackup):
# vxlogcfg -a -p 51216 -o 202 -s DebugLevel=6 -s DiagnosticLevel=6Remote Monitoring and Management Service:
# vxlogcfg -a -p 51216 -o 222 -s DebugLevel=6 -s DiagnosticLevel=6storage_directory\log\pdde-config.log
NetBackup Administration Console logging:
First, open the Debug.Properties file, in C:\Program Files\VERITAS\Java (for Windows) or /usr/openv/java (for UNIX/Linux). Then, edit the file so the following lines are uncommented (or append the lines if they are not present). If you have a GUI that is running, be sure to restart it.
printcmds=true printCmdLines=true debugMask=0x0C000000 debugOn=true
The logs are located under C:\Program Files\VERITAS\NetBackup\logs\user_ops\nbjlogs (Windows) or /opt/openv/netbackup/logs/user_ops/nbjlogs (UNIX/Linux). Ensure that you look at the most recent log.
Storage service (turn on STS logging, to log the
msdp/pdpluginresponses to NetBackup):# vxlogcfg -a -p 51216 -o 202 -s DebugLevel=6 -s DiagnosticLevel=6Remote Monitoring and Management Service:
# vxlogcfg -a -p 51216 -o 222 -s DebugLevel=6 -s DiagnosticLevel=6tpcommand (
...\volmgr\debug\tpcommand)storage_directory\log\msdp-config.log