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 FCP (PA-RISC)
The following example shows how create a sctl device file for an HP VLS9000 robot. NetBackup uses the device file for robotic control.
To create an FCP robotic device file for HP-UX PA-RISC
- Invoke the ioscan -f command. The following output example is edited for readability:
ioscan -f Class I H/W Path Driver S/W State H/W Type Description ============================================================================= fc 0 0/2/0/0 td CLAIMED INTERFACE HP Tachyon XL2 Fibre Channel Mass Storage Adapter fcp 4 0/2/0/0.10 fcp CLAIMED INTERFACE FCP Domain ext_bus 6 0/2/0/0.10.11.255.0 fcpdev CLAIMED INTERFACE FCP Device Interface target 5 0/2/0/0.10.11.255.0.0 tgt CLAIMED DEVICE autoch 2 0/2/0/0.10.11.255.0.0.0 schgr CLAIMED DEVICE HP VLS tape 5 0/2/0/0.10.11.255.0.0.1 stape CLAIMED DEVICE HP Ultrium 4-SCSI tape 6 0/2/0/0.10.11.255.0.0.2 stape CLAIMED DEVICE HP Ultrium 4-SCSI tape 7 0/2/0/0.10.11.255.0.0.3 stape CLAIMED DEVICE HP Ultrium 4-SCSI Examine the output for the card instance number and the SCSI ID and LUN of the robotic device. In this example, the interface card instance number (the I column) is 6. If you use the card's H/W Path value as a mask (0/2/0/0.10.11.255.0), you see the following:
An HP VLS9000 robot is at SCSI ID 0, LUN 0.
Three Ultrium 4-SCSI drives are at SCSI ID 0 and LUN 1, LUN 2, and LUN 3.
- Determine the character major number of the sctl driver by using the lsdev command, as follows:
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 file for the HP VLS9000 robotic control are as follows. The card instance number is 6, the target is 0, and the LUN is 0.
cd /dev/sctl /usr/sbin/mknod c6t0l0 c 203 0x060000
If you add the robot to NetBackup manually, specify the following pathname for robotic control:
/dev/sctl/c6t0l0