Search <book_title>...

Veritas NetBackup™ Logging Reference Guide

Last Published: 2018-09-19

Product(s): NetBackup (8.2, 8.1.2)

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 describes the directories and files that are of special interest.

Table: Media and device management directories and files

File or directory	Contents
bin	Commands, scripts, programs, daemons, and 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.
help	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 explanations include what starts and stops the program or daemon, and the log (if any) where it records its activities. On UNIX, all of the components that are discussed in this table are in /usr/openv/volmgr/bin. On Windows, they are in install_path\volmgr\bin.

Note:

The following table contains references to the system log. On UNIX, syslog manages this 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.
tl4d	The Tape Library 4MM daemon is the interface between ltid and the Tape Library 4MM and communicates with the robotics through a SCSI interface. Started By: Starting ltid (or on UNIX, independently by using the /usr/openv/volmgr/bin/tl4d 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 starting the daemon with the -v option (either by itself or through ltid).
tl8d	The Tape Library 8MM daemon provides the robotic control for a TL8 robot (Tape Library 8mm or Tape Stacker 8mm). The Tape Library 8MM daemon drives in the same TL8 robot can be attached to different hosts than the robotic control. tl8d is the interface between the local ltid and the robotic control. If a host has a device path for a drive in a TL8 robot, then mount or unmount requests for that drive go first to the local ltid and then to the local tl8d (all on the same host). tl8d then forwards the request to tl8cd 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/tl8d 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 the 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).
tl8cd	The Tape Library 8MM control daemon provides the robotic control for a TL8 robot and communicates with the robotics through a SCSI interface. tl8cd receives mount and unmount requests from tl8d 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/tl8cd command). Stopped By: Stopping ltid or by using the tl8cd -t command. Debug Log: Errors are logged in the system log and the 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).
tldd	The Tape Library DLT daemon works with tldcd to handle requests to TLD robots (Tape Library DLT and Tape Stacker DLT). tldd provides the interface between the local ltid and the robotic control (tldcd) in the same way as explained previously for tl8d. 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 robotic control for a TLD robot in the same way as explained previously for tl8cd. 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).
tlhd	The Tape Library Half-inch daemon works with tlhcd to handle requests to the TLH robots that are in an IBM Automated Tape Library (ATL). tlhd provides the interface between the local ltid and the robotic control (tlhcd) in the same way as explained previously for tl8d. Started By: Starting ltid (or on UNIX, independently by using the /usr/openv/volmgr/bin/tlhd 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).
tlhcd	The Tape Library half-inch control daemon provides robotic control for a TLH robot that is in an IBM Automated Tape Library (ATL) in the same way as explained previously for tl8cd. Started By: Starting ltid (or on UNIX, independently by using the /usr/openv/volmgr/bin/tlhcd command). Stopped By: Stopping ltid or by using the tlhcd -t command. Debug Log: Errors are logged in the system log and robots debug log. Debug information is included if the daemon is started with the -v option (either by itself or through ltid). The -v option is available only on UNIX. Also, add the VERBOSE option to the `vm.conf` file.
tlmd	The Tape Library Multimedia daemon is the interface between ltid and a TLM robot that is in an ADIC Distributed AML Server (DAS). This daemon communicates with the TLM robotics through a network API interface. Started By: Starting ltid or starting independently by using the /usr/openv/volmgr/bin/tlmd command. Stopped By: Stopping ltid or stopping 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 if the daemon is started with the -v option (either by itself or through ltid). The -v option is available only on UNIX. Also, add the VERBOSE option to the `vm.conf` file.
tshd	The Tape Stacker Half-inch daemon is the interface between ltid and the half-inch-cartridge stacker and communicates with the robotics through a SCSI interface. This robot is not supported on Windows. Started By: Starting ltid (or on UNIX, independently by using the /usr/openv/volmgr/bin/tshd command). Started By: tpconfig command. Stopped By: Quit option from within the utility on UNIX. On Windows, tpconfig is only a command-line interface that runs to completion (no quit option). Debug Log: tpcommand debug logs.
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.
vmscd	The Media Manager Status Collector Daemon keeps the EMM server database up-to-date with the actual status of the drives that are attached to the 5.x servers. Started By: the EMM server. Stopped By: the EMM server. Debug Log: `/usr/openv/volmgr/debug/vmscd` (UNIX), `install_path\Volmgr\debug\vmscd` (Windows)