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
OpenStorage Technology (OST) backup logging
In this scenario, the client backs up the data directly to the media server and the media server accesses the vendor plug-in to transfer the data to the storage server.
For logging that is specific to OST, enable the following on the media server or plug-in host:
In the registry or
bp.conffile, set VERBOSE = 5.Ensure that the following directories exist under
/usr/openv/netbackup/logs(for Windows, useinstall_path\NetBackup\logs):bptmbpbrmbpstsinfo
Create the
volmgr/debug/tpcommanddirectory.Put VERBOSE in the
vm.conffile.Set DebugLevel=6 and DiagnosticLevel=6 for the following processes:
OID 178 (Disk Manager Service, dsm)
OID 202 (Storage service, stssvc)
OID 220 (Disk Polling Service, dps)
OID 221 (Media Performance Monitor Service)
OID 222 (Remote Monitoring & Management Service)
OID 230 (Remote Disk Manager Service, rdsm)
OID 395 (STS Event Manager, stsem)
These OIDs all log to the
nbrmmsunified log file on the media server.Increase the vendor plug-in logging. Most vendors have their own plug-in logging in addition to what is logged within the NetBackup logs.
Reproduce the backup failure.
Within the NetBackup Administration Console, click on , open the job details and click the Detailed Status tab. It displays the media server host name that ran the backup and the bptm process ID number (PID).
Find a line similar to bptm(pid=value); this value is the bptm PID to locate in the bptm log.
Extract the bptm PID found in step 8 from the bptm log on the media server. This step gathers only the single-line entries; review the raw logs to see the multi-line log entries. In the following examples, 3144 is the bptm PID:
Windows command line:
findstr "\[3144." 092611.log > bptmpid3144.txt
UNIX/Linux command line:
grep "\[3144\]" log.092611 > bptmpid3144.txt
Gather the vendor specific plug-in logs that cover the dates from when the backup started and when it failed.