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
Multiple ACS robots and ACS library software hosts
NetBackup supports the following configuration:
A NetBackup server is connected to drives in multiple ACS robots.
The robots are controlled from separate ACS library software hosts.
Inventory requests include the volumes that are configured on the ACS library software hosts (Host A for Robot 1 and Host B for Robot 2). The software hosts reside on the robot (ACS 0 for each) that is designated in the Sun StorageTek drive address.
In this example, assume the following about drive 1:
Has an ACS drive address (ACS, LSM, panel, drive) of 0,0,1,1 in the NetBackup device configuration
Is under control of robot number 10 (ACS(10))
If any other robot ACS(10) drives have a different ACS drive address (for example, 1,0,1,0), the configuration is invalid.
NetBackup supports configurations of multiple LSMs in a single ACS robot if a pass-through port exists.