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
Creating legacy SCSI and FCP robotic controls on HP-UX
You must create the robotic control device files for the sctl driver manually; they are not created automatically when the system boots.
Before you create the device files, you must do the following:
Install and configure the sctl driver. For more information, see the HP-UX scsi_ctl(7) man page.
The sctl driver may be the default pass-through driver on your system. If so, you do not have to configure the kernel to use the sctl pass-through driver.
Install and configure the schgr device driver. For more information, see the HP-UX autochanger(7) man page.
Attach the devices.
Examples of how to create the device files are available.
To create sctl device files
- Invoke the ioscan -f command to obtain SCSI bus and robotic control information.
Examine the output for the card instance number and the SCSI ID and LUN of the robotic device, as follows:
The instance number of the card is in the I column of the output.
The H/W Path column of the changer output (schgr) includes the SCSI ID and LUN. Use the card's H/W Path value to filter the changer's H/W Path entry; the SCSI ID and the LUN remain.
- Determine the character major number of the sctl driver by using the following command:
lsdev -d sctlExamine the output for an entry that shows sctl in the Driver column.
- Use the following commands to create the device file for the SCSI robotic control:
mkdir /dev/sctl cd /dev/sctl /usr/sbin/mknod cCARDtTARGETlLUN c Major 0xIITL00
Where:
CARD is the card instance number of the adapter.
TARGET is the SCSI ID of the robotic control.
LUN is the SCSI logical unit number (LUN) of the robot.
Major is the character major number (from the lsdev command).
II are two hexadecimal digits that represent the card instance number.
T is a hexadecimal digit that represents the SCSI ID of robotic control.
L is a hexadecimal digit that represents the SCSI LUN of the robotic control.