VERITAS NetBackupTM 5.0, Инструкция пользователя и технические характеристики

Страница: 379 / 428

Appendix B, Automated Cartridge System (ACS)
Using the STK SN6000
345
▼
To use the Device Configuration wizard
1. Run the Device Configuration wizard on one of the hosts where drives in an
ACS-controlled library are attached. Allow the drives to be added as standalone
drives.
2.
Add the ACS robot definition and update each drive to indicate its appropriate
position in the robot. Make each drive robotic and add the ACS, LSM, Panel, and
Drive information.
See “Correlating Device Files to Physical Drives When Adding Drives” on page 272
for help in determining the correct addressing and verifying the drive paths.
3. After the drive paths have been verified on one host, re-run the wizard and specify
that all hosts that have ACS drives in the library should be scanned.
The wizard will add the ACS robot definition and the drives to the remaining hosts
with correct device paths (assuming that the devices and their serial numbers were
successfully discovered and that the drive paths were correctly configured on the first
host).
The use of SANs (including switches rather than direct connection) can increase the
possibility of errors. If you are experiencing errors, you can manually define the tape
drive configuration by using the NetBackup Administration Console or the command
line.
Care must be taken to avoid any errors. With shared drives, the device paths must be
correct for each server. Also ensure that the drives are defined correctly to avoid errors
where drives are defined to be in ACS index number 9, instead of ACS index 0.
Using the STK SN6000
The StorageTek SN6000 provides tape drive virtualization. Logical tape drives are
presented to host operating system interfaces (tape drivers), while robotic control is
accomplished through the ACS API.
Some SN6000 configurations may involve a different number of logical drives compared to
the number of physical drives (or equivalent resources) available for satisfying requests for
drives. Also, the relationship between the number of logical drives and physical drives
may change if hardware failures occur.
NetBackup scheduling, drive allocation, and drive assignment algorithms are only able to
determine logical drive availability, and will attempt to fully utilize all configured and
available logical drives. If the number of logical drives being utilized exceeds the number
of physical drives available, a NetBackup job may be started when insufficient drive