NetBackup™ Device Configuration Guide
- Introducing device configuration
- Section I. Operating systems
- Linux
- Before you begin on Linux
- About the required Linux SCSI drivers
- Verifying the Linux drivers
- About configuring robot and drive control for Linux
- Verifying the device configuration on Linux
- About SAN clients on Linux
- About SCSI persistent bindings for Linux
- About Emulex HBAs
- Utilities to test SCSI devices
- Linux command summary
- Solaris
- Before you begin on Solaris
- About the NetBackup sg driver
- Determining if the NetBackup sg driver is installed
- Special configuration for the StorEdge Network Foundation HBA driver
- About binding Fibre Channel HBA drivers
- Configuring Solaris 10 x86 for multiple drive paths
- Installing/reinstalling the sg and the st drivers
- Configuring 6 GB and larger SAS HBAs in Solaris
- Preventing Solaris driver unloading
- About Solaris robotic controls
- About Solaris tape drive device files
- Configuring Solaris SAN clients to recognize FT media servers
- Uninstalling the sg driver on Solaris
- Solaris command summary
- Windows
- Linux
- Section II. Robotic storage devices
- Robot overview
- Oracle StorageTek ACSLS robots
- About Oracle StorageTek ACSLS robots
- Sample ACSLS configurations
- Media requests for an ACS robot
- About configuring ACS drives
- Configuring shared ACS drives
- Adding tapes to ACS robots
- About removing tapes from ACS robots
- Robot inventory operations on ACS robots
- NetBackup robotic control, communication, and logging
- ACS robotic test utility
- Changing your ACS robotic configuration
- ACS configurations supported
- Oracle StorageTek ACSLS firewall configuration
- Device configuration examples
About SAN clients on Linux
NetBackup SAN clients on Linux hosts require the SCSI Generic (sg) driver pass-through tape drive device files for traffic to NetBackup FT media servers. The media server FT devices appear as ARCHIVE Python tape devices during SCSI inquiry from the SAN client. (However, they are not tape devices and do not appear as tape devices in NetBackup device discovery.)
You should verify that you have the correct driver and device files.
If your Linux operating system does not add all of the SCSI device files automatically, you can do so manually. The following is an example of code you can include in the /etc/rc.local file to add LUN 1, targets 0-7 on Controllers 0-2. Note that the last line is the MAKEDEV command, which makes the required device files. The code you include in your /etc/rc.local file depends on how your hardware environment.
# Add the troublesome device on LUN 1 for the FT server echo "scsi add-single-device 0 0 0 1" > /proc/scsi/scsi echo "scsi add-single-device 0 0 1 1" > /proc/scsi/scsi echo "scsi add-single-device 0 0 2 1" > /proc/scsi/scsi echo "scsi add-single-device 0 0 3 1" > /proc/scsi/scsi echo "scsi add-single-device 0 0 4 1" > /proc/scsi/scsi echo "scsi add-single-device 0 0 5 1" > /proc/scsi/scsi echo "scsi add-single-device 0 0 6 1" > /proc/scsi/scsi echo "scsi add-single-device 0 0 7 1" > /proc/scsi/scsi echo "scsi add-single-device 1 0 0 1" > /proc/scsi/scsi echo "scsi add-single-device 1 0 1 1" > /proc/scsi/scsi echo "scsi add-single-device 1 0 2 1" > /proc/scsi/scsi echo "scsi add-single-device 1 0 3 1" > /proc/scsi/scsi echo "scsi add-single-device 1 0 4 1" > /proc/scsi/scsi echo "scsi add-single-device 1 0 5 1" > /proc/scsi/scsi echo "scsi add-single-device 1 0 6 1" > /proc/scsi/scsi echo "scsi add-single-device 1 0 7 1" > /proc/scsi/scsi echo "scsi add-single-device 2 0 0 1" > /proc/scsi/scsi echo "scsi add-single-device 2 0 1 1" > /proc/scsi/scsi echo "scsi add-single-device 2 0 2 1" > /proc/scsi/scsi echo "scsi add-single-device 2 0 3 1" > /proc/scsi/scsi echo "scsi add-single-device 2 0 4 1" > /proc/scsi/scsi echo "scsi add-single-device 2 0 5 1" > /proc/scsi/scsi echo "scsi add-single-device 2 0 6 1" > /proc/scsi/scsi echo "scsi add-single-device 2 0 7 1" > /proc/scsi/scsi /dev/MAKEDEV sg
More Information