Veritas NetBackup™ Device Configuration Guide
- Introducing device configuration
- Section I. Operating systems
- About the required Linux SCSI drivers
- About configuring robot and drive control for Linux
- Installing/reinstalling the sg and the st drivers
- About Solaris robotic controls
- About Solaris tape drive device files
- Configuring Solaris SAN clients to recognize FT media servers
- Section II. Robotic storage devices
- Robot overview
- Oracle StorageTek ACSLS robots
- About removing tapes from ACS robots
- Robot inventory operations on ACS robots
- NetBackup robotic control, communication, and logging
- NetBackup robotic control, communication, and logging for UNIX systems
- ACS robotic test utility
- ACS configurations supported
- Device configuration examples
Robotic process example
Each drive in a tape library DLT (TLD) robot can be attached to a different host, and a tldd process runs on each host. However, only one host controls the robotics, and the tldcd robotic control process runs on that host only. To mount a tape, the tldd process on the host to which the drive is attached sends control information to the tldcd process on the robotic control host.
The following figure shows the processes and where they run for a TLD robot.
The following describes this example:
Each host connects to one drive, and a tldd robotic process runs on each host.
The robotic control and therefore the robotic control process, tldcd, is on host A.
The NetBackup Device Manager services on host A and B start tldd. The tldd process on host A also starts tldcd. Requests to mount tapes from host B go to tldd on host B, which then sends the robotic command to tldcd on host A.