Veritas NetBackup™ Device Configuration Guide
- Introducing device configuration
- Section I. Operating systems
- AIX
- Before you begin configuring NetBackup on AIX
- RS/6000 AIX adapter number conventions
- About AIX persistent naming support
- About configuring robotic control device files in AIX
- About device files for SAN Clients on AIX
- About configuring tape drive device files in AIX
- About choosing a tape driver on AIX
- About non-QIC tape drives on AIX
- About extended-file marks for drives
- About fast-tape positioning (locate-block) on AIX
- About no rewind device files on AIX
- Creating AIX no rewind device files for tape drives
- Using multiple tape densities on AIX
- About SPC-2 SCSI reserve on AIX
- Disabling SPC-2 SCSI reserve in AIX
- About Sony AIT drives on AIX
- AIX command summary
- HP-UX
- Before you begin configuring NetBackup on HP-UX
- About robotic control on HP-UX
- About HP-UX device addressing schemes
- HP-UX tape drive device file requirements for NetBackup
- About device drivers and files for HP-UX persistent DSFs
- About configuring persistent DSFs
- About HP-UX legacy device drivers and files
- Creating device files for SAN Clients on HP-UX
- About configuring legacy device files
- About SPC-2 SCSI reserve on HP-UX
- Disabling SPC-2 SCSI reserve in HP-UX
- About disabling the HP-UX EMS Tape Device Monitor for a SAN
- HP-UX command summary
- 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 Oracle 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
- AIX
- 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
Example of how to create a sctl device file for SCSI (PA-RISC)
In this example, the following robots exist:
An ADIC Scalar 100 library is on a SCSI bus with an instance number of 7, SCSI ID 2, and LUN 0.
The robotic control for an IBM ULT3583-TL library is on the same SCSI bus at SCSI ID 3 and LUN 0.
To create SCSI robotic device files for HP-UX PA-RISC
- Invoke the ioscan -f command, as follows:
ioscan -f Class I H/W Path Driver S/W State H/W Type Description ================================================================= ext_bus 7 0/7/0/1 c720 CLAIMED INTERFACE SCSI C896 Fast Wide LVD target 10 0/7/0/1.0 tgt CLAIMED DEVICE tape 65 0/7/0/1.0.0 stape CLAIMED DEVICE QUANTUM SuperDLT1 target 11 0/7/0/1.1 tgt CLAIMED DEVICE tape 66 0/7/0/1.1.0 stape CLAIMED DEVICE QUANTUM SuperDLT1 target 12 0/7/0/1.2 tgt CLAIMED DEVICE autoch 14 0/7/0/1.2.0 schgr CLAIMED DEVICE ADIC Scalar 100 target 13 0/7/0/1.3 tgt CLAIMED DEVICE autoch 19 0/7/0/1.3.0 schgr CLAIMED DEVICE IBM ULT3583-TL target 14 0/7/0/1.4 tgt CLAIMED DEVICE tape 21 0/7/0/1.4.0 atdd CLAIMED DEVICE IBM ULT3580-TD1 target 15 0/7/0/1.5 tgt CLAIMED DEVICE tape 19 0/7/0/1.5.0 atdd CLAIMED DEVICE IBM ULT3580-TD1
- Examine the output for the card instance number and the SCSI ID and LUN of the robotic device, as follows:
The card H/W Path is 0/7/0/1; the card instance number (I column) is 7. Apply the H/W Path value as a mask. The ADIC robotic device (schgr) is at SCSI ID 2, LUN 0 on this bus. The IBM robotic device (schgr) is at SCSI ID 3, LUN 0 on this bus.
- Determine the character major number of the sctl driver by using the following command:
lsdev -d sctl Character Block Driver Class 203 -1 sctl ctl
The output from this command shows that the character major number for the sctl driver is 203.
- The commands to create the device files follow. For the ADIC robot, the card instance number is 7, the target is 2, and the LUN is 0. For the IBM robot, the card instance number is 7, the SCSI ID is 3, and the LUN is 0.
cd /dev/sctl /usr/sbin/mknod c7t2l0 c 203 0x072000 /usr/sbin/mknod c7t3l0 c 203 0x073000
If you add the robots to NetBackup manually, you specify the following for ADIC robotic control and IBM robotic control respectively:
/dev/sctl/c7t2l0 /dev/sctl/c7t3l0