Veritas NetBackup™ Device Configuration Guide
- Introducing device configuration
- Section I. Operating systems
- Linux
- About the required Linux SCSI drivers
- About configuring robot and drive control for Linux
- Solaris
- 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
- Windows
- Linux
- 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
- ACS robotic test utility
- ACS configurations supported
- Device configuration examples
ACS robots
Unlike other robot types, NetBackup does not track slot locations for the media in ACS robots. The ACS library software tracks slot locations and reports them to NetBackup.
The following table describes the ACS robot attributes.
Table: ACS robot attributes
Attribute | NetBackup server |
---|---|
API robot | Yes |
SCSI control | No |
LAN control | Yes |
Remote Robot control | No. Each host that has ACS drives that are attached to it has robotic control. |
NDMP support | Yes |
Shared drives support | Yes |
Drive cleaning support | No. The ACS library software manges drive cleaning. |
Media access port support | Yes, for eject only. |
NetBackup tracks slots | No |
Media type support | DLT, DLT2, DLT3, HCART, HCART2, and HCART3. |
Hosts Supported | Windows, UNIX, and Linux. Windows servers require STK LibAttach software. See the Veritas support web site for the latest compatibility information and obtain the appropriate LibAttach software from STK. |
Barcode Support | Yes. Depends on ACS library software to obtain NetBackup media IDs. Barcodes must be the same as the media ID (1 to 6 characters). |
Robot Examples | Oracle SL500, Oracle SL3000, and Oracle SL8500 |