Veritas NetBackup™ Device Configuration Guide
- Introducing device configuration
- Section I. Operating systems
- Linux
- Before you begin on Linux
- About the required Linux SCSI drivers
- Verifying the Linux drivers
- About configuring robot and drive control for Linux
- Verifying the device configuration on Linux
- About SAN clients on Linux
- About SCSI persistent bindings for Linux
- About Emulex HBAs
- Utilities to test SCSI devices
- Linux command summary
- Solaris
- Before you begin on Solaris
- About the NetBackup sg driver
- Determining if the NetBackup sg driver is installed
- Special configuration for the StorEdge Network Foundation HBA driver
- About binding Fibre Channel HBA drivers
- Configuring Solaris 10 x86 for multiple drive paths
- Installing/reinstalling the sg and the st drivers
- Configuring 6 GB and larger SAS HBAs in Solaris
- Preventing Solaris driver unloading
- About Solaris robotic controls
- About Solaris tape drive device files
- Configuring Solaris SAN clients to recognize FT media servers
- Uninstalling the sg driver on Solaris
- Solaris command summary
- Windows
- Linux
- Section II. Robotic storage devices
- Robot overview
- Oracle StorageTek ACSLS robots
- About Oracle StorageTek ACSLS robots
- Sample ACSLS configurations
- Media requests for an ACS robot
- About configuring ACS drives
- Configuring shared ACS drives
- Adding tapes to ACS robots
- About removing tapes from ACS robots
- Robot inventory operations on ACS robots
- NetBackup robotic control, communication, and logging
- ACS robotic test utility
- Changing your ACS robotic configuration
- ACS configurations supported
- Oracle StorageTek ACSLS firewall configuration
- Device configuration examples
Robotic processes
A NetBackup robotic process and possibly a robotic control process exist on a NetBackup media server for each robot that you install, as follows:
Every media server that has a drive in a robotic library has a robotic process for that robotic library. The robotic process receives requests from the NetBackup Device Manager (ltid) and sends necessary information directly to the robotics or to a robotic control process.
Robotic control processes exist only for the robot types that support library sharing (or robot sharing).
When the NetBackup Device Manager starts, it starts the robotic processes and the robotic control processes for all of the configured robots on that host. When the Device Manager stops, the robotic processes and the robotic control processes stop. (On UNIX, the name is Media Manager Device daemon.)
You can start and stop the Device Manager manually by using the NetBackup Administration Console as follows:
In the NetBackup Activity Monitor Daemons tab, select it and then select or .
Select , , or Devices in the right pane and then select .
In addition, the NetBackup Commands Reference Guide describes commands to control the robotic processes that run on Windows media servers.
You can determine if a robotic process or robotic control process is active by using the NetBackup Activity Monitor Processes tab.
You can determine the control state of NetBackup by using the Device Monitor Drive paths pane or Drive status pane. If the value in the Control column for a drive shows the control mode, the robotic process is running and the drive is usable. For example, for a TLD robot the control mode is TLD.
Other values such as AVR or DOWN may indicate that the drive is unusable. For the possible values and their explanations, see the online Help for the Device Monitor.