Veritas NetBackup™ Device Configuration Guide
- Introducing device configuration
- Section I. Operating systems
- 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
About binding Fibre Channel HBA drivers
For Fibre Channel HBAs other than StorEdge Network Foundation, you must bind the devices to specific target IDs on the NetBackup host. When you bind devices to targets, the target ID does not change after a system reboot or a Fibre Channel configuration change.
In some instances, Veritas products are configured to use a specific target ID. If you change the ID, the products fail until you configure the ID correctly.
How you bind devices to targets is vendor and product specific. For information about how to modify the HBA configuration files to bind devices to targets, see the documentation for the HBA.
The binding may be based on the following:
After you bind the devices to target IDs, continue with the Solaris configuration in the same manner as for parallel SCSI installations.
Each time you add or remove a device, you must update the bindings and then configure the sg and the st drivers again.