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
Media and device management components
This topic shows the file and the directory structure and the programs and the daemons that are associated with media management and device management.
Figure: Media and device management directories and files shows the file structure and directory structure for media management and device management on a UNIX server. A Windows NetBackup server has the equivalent files and the directories that are located in the directory where NetBackup is installed (by default, the C:\Program Files\VERITAS directory).
Table: Media and device management directories and files
File or directory | Contents |
|---|---|
| Commands, scripts, programs, daemons, and any files that are required for media and device management. The following subdirectories under bin are available:
|
| Legacy debug logs for the Volume Manager daemon, vmd, and all requesters of vmd, ltid, and device configuration. The administrator must create these directories for debug logging to occur. If the service user is configured, assign permissions to the service user to access the debug directory and its sub-directories. |
| Any help files that the media and device management programs use. These files are in ASCII format. |
| Lock files and temporary files that are required by the various components of media and device management. |
| Media and device management configuration options. |
Table: Media and device management daemons and programs describes the media management and device management programs and daemons. The components are located in the following directory:
/usr/openv/volmgr/bin
install_path\volmgr\bin.
Note:
On UNIX, syslog manages the system log (the facility is daemon). On Windows, the Event Viewer manages the system log (the log type is Application).
Table: Media and device management daemons and programs
Program or daemon | Description |
|---|---|
acsd | The Automated Cartridge System daemon interfaces with the Automated Cartridge System. It communicates with the server that controls the ACS robotics through the acsssi process (UNIX) or the STK Libattach Service (Windows). For UNIX, see the acsssi and the acssel programs. : Starting ltid (or on UNIX, independently by using the /usr/openv/volmgr/bin/ascd command. : Stopping ltid (or on UNIX, independently by finding the PID (process ID) and then using the kill command). : Errors are logged in the system log and robots debug log. Debug information is included by adding VERBOSE to the |
acssel | Available only on UNIX. See the NetBackup Device Configuration Guide. |
acsssi | Available only on UNIX. See the NetBackup Device Configuration Guide. |
avrd | The automatic-volume-recognition daemon controls the automatic volume assignment and label scanning. This daemon lets NetBackup read labeled tape volumes and automatically assigns the associated removable media to the requesting processes. : Starting ltid (or on UNIX, independently by using the /usr/openv/volmgr/bin/avrd command). : Stopping ltid, (or on UNIX, independently by finding the PID (process ID) and then using the kill command). : All errors are logged in the system log. Debug information is included by adding VERBOSE to the |
ltid | The device daemon (UNIX) or NetBackup Device Manager service (Windows) controls the reservation and assignment of tapes. : /usr/openv/volmgr/bin/ltid command on UNIX or the Stop/Restart Device Manager Service command in the Media and Device Management window on Windows. : /usr/openv/volmgr/bin/stopltid command on UNIX or the Stop/Restart Device Manager Service command in the Media and Device Management window on Windows. : Errors are logged in the system log and the ltid debug log. Debug information is included if the daemon is started with the -v option (available only on UNIX) or adding VERBOSE to the |
tldd | The tape library DLT daemon works with tldcd to handle requests to TLD robots (tape library DLT). The tape library DLT daemon drives in the same TLD robot can be attached to different hosts than the robotic control. tldd is the interface between the local ltid and the robotic control. If a host has a device path for a drive in a DLT robot, then mount or unmount requests for that drive go first to the local ltid and then to the local tldd (all on the same host). tldd then forwards the request to tldcd on the host that is controls the robot (it can be on another host). : Starting ltid (or on UNIX, independently by using the /usr/openv/volmgr/bin/tldd command). : Stopping ltid (or on UNIX, independently by finding the PID (process ID) and then using the kill command). : Errors are logged in the system log and robots debug log. Debug information is included by adding VERBOSE to the |
tldcd | The tape library DLT control daemon provides the robotic control for a DLT robot and communicates with the robotics through a SCSI interface. tldcdcd receives mount and unmount requests from tldd on the host to which the drive is attached and then communicates these requests to the robot. : Starting ltid (or on UNIX, independently by using the /usr/openv/volmgr/bin/tldcd command). : Stopping ltid or by using the tldcd -t command. : Errors are logged in the system log and robots debug log. Debug information is included by adding VERBOSE to the vm.conf file. On UNIX, debug information is also included by starting the daemon with the -v option (either by itself or through ltid). |
vmd | The Volume Manager daemon (NetBackup Volume Manager service on Windows) allows the remote administration and control of Media and Device Management. : Starting ltid. : Terminating the Media Manager Volume Daemon option. : System log and also a debug log if the daemon or reqlib debug directories exist. |