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
- Accessibility of the 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
Directory names for legacy debug logs for media and device management
The following directories enable legacy logging for the media management processes and device management processes. NetBackup creates 1 log per day in each of the debug directories. Each directory corresponds to a process. Unless it is noted, each directory should be created under the following directory.
Windows | install_path\Volmgr\debug |
UNIX | /usr/openv/volmgr/debug |
Table: Media and device management legacy debug logs
Directory | Associated process |
|---|---|
acsssi | UNIX only. Debug information on transactions between NetBackup and the StorageTek ACSLS server. |
daemon | Debug information for vmd (NetBackup Volume Manager service, Windows) and its associated processes (oprd and rdevmi). Stop and restart vmd after creating the directory. |
ltid | Debug information on ltid, the Media Manager device daemon (UNIX), or on the NetBackup Device Manager service (Windows), and on avrd. Stop and restart ltid after creating the directory. |
reqlib | Debug information on the processes that request media management services from vmd or EMM. Stop and restart vmd after creating the directory. |
robots | Debug information on all robotic daemons, which includes tldcd daemons. Stop and restart robotic daemons. |
tpcommand | Debug information for device configuration, including the tpconfig and the tpautoconf commands and the NetBackup Administration Console. |
vmscd | Debug information for the NetBackup Status Collection daemon. Stop and restart vmscd after creating the directory. |
You can disable debug logging by deleting or renaming the following directory:
Windows: NetBackup Volume Manager service | install_path\Volmgr\debug\daemon |
UNIX: vmd command | /usr/openv/volmgr/debug/daemon |