- VERITAS VOLUME MANAGER COMMAND LINE HOW TO
- VERITAS VOLUME MANAGER COMMAND LINE SOFTWARE
- VERITAS VOLUME MANAGER COMMAND LINE WINDOWS
VERITAS VOLUME MANAGER COMMAND LINE WINDOWS
On Windows systems, the Internet service port number for tldcd must be in %SystemRoot%\system32\drivers\etc\services. If you use NIS, place the entry in the /etc/services file in the master NIS server database for services. On UNIX systems, the Internet service port number for tlhcd must be in /etc/services. In addition, you cannot use the Media Manager utilities or the tpclean command for cleaning operations on drives under TLH robotic control. For this reason, you cannot define the volumes to clean through Media Manager. The cleaning operations are not available to applications that use the IBM library manager. You can also use this utility along with IBM's mtlib command-line interface to verify library communications, status, and functionality.Ĭonfigure the drive cleaning operation for the tape library half-inch robotic control through an IBM library manager console.
The robotic test utility, tlhtest ( robtest if the robot is configured), can be used to determine the device names that are associated with the robot. The drives are configured by using IBM device names.
VERITAS VOLUME MANAGER COMMAND LINE HOW TO
See tpclean about how to set the frequency to clean the drive automatically. If a cleaning volume is used, it must be defined in the volume configuration. Both the initial EMM database population and future updates can be accomplished by using Media Manager robotic inventory options. tlhcd stops when you stop the NetBackup Device Manager service.īefore you access any volumes through the NetBackup Device Manager service (Windows systems), ltid, tlhd, and tlhcd, define the following information: the media ID and slot number for volumes in a robot in the EMM database. tlhd starts it automatically on that host (see EXAMPLES). The control process, tlhcd, is on the host that has the robotic control. They are stopped when this service is stopped. On Windows systems, tlhd and tlhcd are started when the NetBackup Device Manager service is started. tlhcd on that host automatically starts it (see EXAMPLES).
The control daemon, tlhcd, is on the host that has the robotic control. Then enter the following commands: kill tlhd_pid To stop or start tlhd independently of ltid, use /usr/openv/volmgr/bin/vmps or your server's ps command to identify the tlhd process ID. On UNIX systems, tlhd and tlhcd automatically start and stop when ltid is started and stopped. The robot number must be the same on all computers. If drives are on different hosts, enter the robotic information in the Media and Device Management of the Administration Console on all computers. In this state, tlhd is still running and returns the robot to the UP state if tlhcd is able to make a connection. If the library or the control daemon is inaccessible, tlhd changes the robot to the DOWN state. When communication with the library is established, tlhd puts the TLH robot in the UP state and can request volume mounts and unmounts. tlhcd can be running on a different host than tlhd, depending on where the IBM library control is configured (see EXAMPLES).
VERITAS VOLUME MANAGER COMMAND LINE SOFTWARE
TLH robotic control software permits drives in the same robot to be configured on different hosts. Tlhcd communicates with the IBM Automated tape library (ATL) library manager, which processes all requests and all control functions for the robotic library. tlhd runs on each host with a drive connection and sends mount and unmount requests to the control daemon-process, tlhcd. Ltid is the Media Manager device daemon on UNIX systems and the NetBackup Device Manager service on Windows systems. Tlhd and tlhcd interface with Media Manager to mount and unmount tape volumes in a tape library half-inch (TLH) robot. This command applies only to the NetBackup Enterprise Server.