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
NetBackup web services logging
The NetBackup web services logs are as follows (on the master server only):
UNIX: /usr/openv/logs/nbwebservice
Windows: install path\netbackup\logs\nbwebservice
This log directory contains the web services originator log files. They include, but are not limited to, the following log files:
Table: Web services OIDs and log files
Originator ID | Log file | Description |
|---|---|---|
439 |
| NetBackup Web Service |
466 |
| NetBackup Security Service (security web app) |
482 |
| NetBackup Hosts Webservice (hosts web app) |
483 |
| NetBackup Configuration Management Service (web app) |
484 |
| NetBackup Gateway Service (web app) |
485 |
| NetBackup WebSocket Service (NBWSS) (web app) |
487 |
| NetBackup Catalog Web Service (web app) |
488 |
| NetBackup Role-based Access Control (RBAC) Web Service (web app) |
489 |
| NetBackup Admin Web Service (web app) |
The logging for processes with originator IDs (OIDs) can be increased and decreased using the vxlogcfg command located in NetBackup\bin. This command can be used to add and remove logging for each of the previous processes. See the following examples that use OID 439:
To add logging, use the following command with the -a (add) option:
vxlogcfg -a -p NB -o 439 -s DebugLevel=6
To remove logging, use the following command with the -r (remove) option:
vxlogcfg -r -p NB -o 439 -s DebugLevel=6
If an issue can be easily or quickly reproduced, it can be easier to configure the default log file setting to 6, and then decrease it to the out-of-the-box setting of 1. See the following examples:
To increase logging, use the following command:
vxlogcfg -a -p NB -o Default -s DebugLevel=6
To decrease logging, use the following command:
vxlogcfg -a -p NB -o Default -s DebugLevel=1
Note:
In the previous examples, the -a option was added to both commands because we do not want to remove the default logging, but only change the debug level to the out-of-the-box default level.
Caution:
Always wait at least 1 full minute after changing the log file logging levels as it may take a minute for the changes to be implemented.
Do not leave a high level of logging in place for a long period of time as it can cause the file systems to fill up with logs.
If the OIDs are set to 0 by default, they are not affected when the default logging levels are changed. These OIDs are as follows:
156 - NetBackup ACE/TAO; this logs to any process that needs to utilize an ACE/TAO call
486 - NetBackup proxy helper; this logs to the unified
nbpxyhelperlog file. See NetBackup proxy helper logging.