Veritas NetBackup™ Device Configuration Guide
- Introducing device configuration
- Section I. Operating systems
- About configuring tape drive device files in AIX
- Creating AIX no rewind device files for tape drives
- About device drivers and files for HP-UX persistent DSFs
- About configuring persistent DSFs
- About HP-UX legacy device drivers and files
- About configuring legacy device files
- Creating legacy SCSI and FCP robotic controls on HP-UX
- 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
The following table describes the ACS robot attributes.
Table: ACS robot attributes
Remote Robot control
No. Each host that has ACS drives that are attached to it has robotic control.
Shared drives support
Drive cleaning support
No. The ACS library software manges drive cleaning.
Media access port support
Yes, for eject only.
NetBackup tracks slots
Media type support
DLT, DLT2, DLT3, HCART, HCART2, and HCART3.
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.
Yes. Depends on ACS library software to obtain NetBackup media IDs.
Barcodes must be the same as the media ID (1 to 6 characters).
Oracle SL500, Oracle SL3000, and Oracle SL8500