Veritas 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
Installing/reinstalling the sg and the st drivers
You must install the NetBackup sg driver and the Sun st driver on each Solaris NetBackup media server that hosts tape devices.
Each time you add or remove a device, you should configure the NetBackup sg driver and the Sun st driver again. For 6 GB and larger serial-attached SCSI (SAS) HBAs, also configure class 08 and 0101 for the sg driver.
See Configuring 6 GB and larger SAS HBAs in Solaris.
Before you configure the sg and the st drivers, ensure that all devices are turned on and connected to the HBA.
The sg.build command uses the Solaris sasinfo command to probe for SAS attached device paths. This command is only available on Solaris 11 and later. On Solaris 10 and earlier, you must configure the sg driver manually.
To install and configure the sg and the st drivers
- Invoke the following two commands to run the NetBackup sg.build script:
cd /usr/openv/volmgr/bin/driver /usr/openv/volmgr/bin/sg.build all -mt target -ml lun
The following describes the options:
The all option creates the following files and populates them with the appropriate entries:
/usr/openv/volmgr/bin/driver/st.conf
/usr/openv/volmgr/bin/driver/sg.conf
/usr/openv/volmgr/bin/driver/sg.links
The -mt target option and argument specify the maximum target ID that is in use on the SCSI bus (or bound to an FCP HBA). The maximum value is 126. By default, the SCSI initiator target ID of the adapter is 7, so the script does not create entries for target ID 7.
The -ml lun option and argument specify the maximum number of LUNs that are in use on the SCSI bus (or by an FCP HBA). The maximum value is 255.
- Replace the following seven entries in the /kernel/drv/st.conf file with all of the entries from the /usr/openv/volmgr/bin/driver/st.conf file:
name="st" class="scsi" target=0 lun=0; name="st" class="scsi" target=1 lun=0; name="st" class="scsi" target=2 lun=0; name="st" class="scsi" target=3 lun=0; name="st" class="scsi" target=4 lun=0; name="st" class="scsi" target=5 lun=0; name="st" class="scsi" target=6 lun=0;
You should make a backup copy of the /kernel/drv/st.conf file before you modify it.
- Reboot the system with the reconfigure option (boot -r or reboot -- -r).
During the boot process, the system probes all targets in the st.conf file for devices. It should create device files for all of the devices it discovers.
- Verify that Solaris created the device nodes for all the tape devices by using the following command:
ls -l /dev/rmt/*cbn
- Install the new sg driver configuration by invoking the following two commands:
/usr/bin/rm -f /kernel/drv/sg.conf /usr/openv/volmgr/bin/driver/sg.install
The NetBackup sg.install script does the following:
Installs and loads the sg driver.
Copies the /usr/openv/volmgr/bin/driver/sg.conf file to /kernel/drv/sg.conf.
Creates the /dev/sg directory and nodes.
Appends the /usr/openv/volmgr/bin/driver/sg.links file to the /etc/devlink.tab file.
- Verify that the <command>sg</command> driver finds all of the robots and tape drives.