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
NetBackup ACS daemon (acsd)
The NetBackup ACS daemon acsd provides robotic control to mount and dismount volumes. It also requests inventories of the volumes that are under the control of ACS library software. the Media Manager device daemon ltid starts the acsd daemon and communicates with it. If ltid is active already, you can start acsd manually.
The acsd daemon requests SCSI tape unloads through the device host's tape driver before it uses the ACS API to request that tape dismounts. This control process accommodates the configurations that have SCSI multiplexors. Loaded tapes are not ejected forcibly when a dismount operation occurs.
When acsd starts, it first starts the NetBackup acssel process and then starts the acsssi process. When it starts acsssi, acsd passes the ACS library software host name to acsssi. One copy of acsssi starts for each ACS library software host that appears in the NetBackup device configuration for the media server. If multiple media servers share drives in an ACS robot, acsssi must be active on each media server.