Search <book_title>...

NetBackup™ Logging Reference Guide

Last Published: 2024-03-27

Product(s): NetBackup & Alta Data Protection (10.4)

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).

Figure: Media and device management directories and files

Table: Media and device management directories and files

File or directory	Contents
`bin`	Commands, scripts, programs, daemons, and any files that are required for media and device management. The following subdirectories under bin are available: `driver`: Contains the SCSI drivers that are used on various platforms to control robotics. `goodies`: Contains the vmconf script and scan utility.
`debug`	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.
`help`	Any help files that the media and device management programs use. These files are in ASCII format.
`misc`	Lock files and temporary files that are required by the various components of media and device management.
`vm.conf`	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. Started By: Starting ltid (or on UNIX, independently by using the /usr/openv/volmgr/bin/ascd command. Stopped By: Stopping ltid (or on UNIX, independently by finding the PID (process ID) and then using the kill command). Debug Log: 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: this option can also be used through ltid, or by putting VERBOSE in the `vm.conf` file.
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. Started By: Starting ltid (or on UNIX, independently by using the /usr/openv/volmgr/bin/avrd command). Stopped By: Stopping ltid, (or on UNIX, independently by finding the PID (process ID) and then using the kill command). Debug Log: All errors are logged in the system log. Debug information is included by adding VERBOSE to the `vm.conf` file. On UNIX, debug information is also included by aborting avrd and starting the daemon with the -v option.
ltid	The device daemon (UNIX) or NetBackup Device Manager service (Windows) controls the reservation and assignment of tapes. Started By: /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. Stopped By: /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. Debug Log: 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 `vm.conf` file.
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). Started By: Starting ltid (or on UNIX, independently by using the /usr/openv/volmgr/bin/tldd command). Stopped By: Stopping ltid (or on UNIX, independently by finding the PID (process ID) and then using the kill command). Debug Log: 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).
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. Started By: Starting ltid (or on UNIX, independently by using the /usr/openv/volmgr/bin/tldcd command). Stopped By: Stopping ltid or by using the tldcd -t command. Debug Log: 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. Started By: Starting ltid. Stopped By: Terminating the Media Manager Volume Daemon option. Debug Log: System log and also a debug log if the daemon or reqlib debug directories exist.