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 storage server interface (acsssi)
The NetBackup ACS storage server interface (SSI) acsssi communicates with the ACS library software host. acsssi processes all RPC communications from acsd or from the ACS robotic test utility that are intended for the ACS library software.
One copy of acsssi must run for each unique ACS library software host that is configured on a NetBackup media server. acsd tries to start copies of acsssi for each host. However, if an acsssi process for a specific ACS library software host exists already, the new acsssi processes for that host fails during initialization.
In normal operations, acsssi runs in the background and sends log messages to acssel.
You can specify the socket name (IP port) used by acsssi in any of the following ways:
On the command line when you start acsssi.
By using an environment variable (ACS_SSI_SOCKET).
Through the default value.
If you configure acsssi to use a nondefault socket name, you also must configure the ACS daemon and ACS test utility to use the same socket name.
The ACS library software host name is passed to acsssi by using the CSI_HOSTNAME environment variable.
acsssi is based on the Oracle StorageTek storage server interface. Therefore, it supports environment variables to control most aspects of operational behavior.
More Information