Veritas NetBackup™ Commands Reference Guide
- Appendix A. NetBackup Commands
tldd — Tape library DLT (TLD) daemon (process) or control daemon (process).
On UNIX systems, the directory path to this command is /usr/openv/volmgr/bin/
On Windows systems, the directory path to this command is install_path\Volmgr\bin\
tldd and tldcd interface with Media Manager to mount and unmount volumes in a tape library DLT (TLD) robot.
ltid is the Media Manager device daemon on UNIX systems and the NetBackup Device Manager service on Windows systems. tldd directly interfaces with ltid. tldd runs on each host with a drive connection and sends mount and unmount requests to the control daemon (tldcd). tldcd communicates directly with the robotics through a SCSI interface.
The following items apply only to NetBackup Enterprise Server:
TLD robotic control software permits drives in the same robot to be configured on different hosts. tldcd may be running on a different host than tldd, depending on where the interface connection resides (see EXAMPLES). When the connection is established (the path for robotics can be opened), tldd puts the TLD robot in the UP state. It then can mount and unmount volumes. If the robotics are inaccessible, tldd changes the robot to the DOWN state. In this state, tldd is still running and returns the robot to the UP state if tldcd is able to make a connection.
If drives are on different NetBackup hosts, enter the robotic information in the Media and Device Management of the Administration Console on all computers. The robot number must be the same on all computers.
On UNIX systems, tldd and tldcd automatically start and stop when ltid is started and stopped. To stop or start tldd independently of ltid, use
/usr/openv/volmgr/bin/vmps or your server's ps command to identify the tldd process ID. Then enter the following commands:
kill tldd_pid /usr/openv/volmgr/bin/tldd [-v] &
The control daemon, tldcd, is on the host that has the robotic control. tldd on that host automatically starts it (see EXAMPLES).
On Windows systems, tldd and tldcd are started when the NetBackup Device Manager service is started. They are stopped when this service is stopped. The control process, tldcd, is on the host that has the robotic control. tldd starts it automatically on that host (see EXAMPLES). tldcd stops when you stop the NetBackup Device Manager service.
Before you access any volumes through the NetBackup Device Manager service (Windows systems), ltid, tl8d, and tl8cd, define the following information: the media ID and slot number for volumes in a robot in the EMM database.
If a cleaning volume is used, it must be defined in the volume configuration. See tpclean for information on setting the frequency to clean the drive automatically.
The drives are logically numbered 1 through n, where n is the number of drives in the robotic library. Use one or more of the following to determine the correct robot drive numbers:
The Device Configuration Wizard (if the robotic library and drives support serialization).
The robotic library vendor's documentation on how to index drives.
The robotic test utility, or experiment by mounting media and watch the operator display.
On UNIX systems, the Internet service port number for tldcd must be in
/etc/services. If you use NIS (Network Information Service), place the entry in this host's
/etc/services file in the master NIS server database for services.
On Windows systems, the Internet service port number for tldcd must be in
The default service port number is 13711.
You must have administrator privileges to run this command.
The following option operates only on UNIX systems.
Logs debug information by using syslogd. If you start ltid with -v, tldd and tldcd are also started with -v.
Media Manager logs any tape library DLT and robotic errors to the Windows application event log. Log entries are also made when the state changes between UP and DOWN.
tldd and tldcd log an error message if another copy of the daemon is in operation.
Media Manager logs any tape library DLT and robotic errors to syslogd. Log entries are also made when the state changes between UP and DOWN.
Example 1 - In the following diagram, the two drives and the robotics connect to Host A. ltid initiates tldd, which in turn initiates tldcd.
Example 2 - This example applies only to NetBackup Enterprise Server. In the following diagram, each host connects to one drive and the robotics connect to host A. ltid on each computer initiates tldd. The tldd on host A also initiates tldcd, since that is where the robotic control is defined. Requests to mount tapes from host B go to tldd on host B, which sends the robotic command to tldcd on host A.