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
Logging options with the Windows Event Viewer
You can configure a NetBackup Windows master server to also write logging application and diagnostic messages to the Windows Event Viewer Application Event log.
For details on vxlogcfg, see the NetBackup Commands Reference Guide.
To write unified logging messages to the Windows Event Viewer for an originator
- Use the vxlogcfg command to set the LogToOslog value to true for the originator.
For example:
# vxlogcfg -a -o nbrb -p NB -s "LogToOslog=true"
- Restart the NetBackup services.
To write legacy logging messages to the Windows Event Viewer
- Create the eventlog file on the NetBackup master server.
install_path\NetBackup\db\config\eventlog
- Optionally, add an entry to the eventlog file. For example:
56 255
"56" produces a log with the messages that have a severity of warning, error, and critical (56 = 8 + 16 + 32). "255" produces a log with messages for all types (255 = 1 + 2 + 4 + 8 + 16 + 32 + 64 +128).
- Restart the NetBackup services.
The parameters in the eventlog represent severity and type. Both parameters are specified as decimal numbers and equate to a bitmap for the values below.
Severity |
| 1 = Unknown 2 = Debug 4 = Info 8 = Warning 16 = Error 32 = Critical |
Type |
| 1 = Unknown 2 = General 4 = Backup 8 = Archive 16 = Retrieve 32 = Security 64 = Backup Status 128 = Media Device |
In the logs, the messages are formatted as follows:
<Severity> <Job type> <Job ID> <Job group ID> <Server> <Client> <Process> <Text>
For example:
16 4 10797 1 cacao bush nbpem backup of client bush exited with status 71