Veritas NetBackup™ Device Configuration Guide
- Introducing device configuration
- Section I. Operating systems
- Linux
- About the required Linux SCSI drivers
- About configuring robot and drive control for Linux
- Solaris
- Installing/reinstalling the sg and the st drivers
- About Solaris robotic controls
- About Solaris tape drive device files
- Configuring Solaris SAN clients to recognize FT media servers
- Windows
- Linux
- Section II. Robotic storage devices
- Robot overview
- Oracle StorageTek ACSLS robots
- About removing tapes from ACS robots
- Robot inventory operations on ACS robots
- NetBackup robotic control, communication, and logging
- ACS robotic test utility
- ACS configurations supported
- Device configuration examples
Configuring 6 GB and larger SAS HBAs in Solaris
Use the procedure in this topic to configure the NetBackup sg driver for Oracle 6 GB and larger SAS HBAs on Solaris.
A separate topic describes how to install the NetBackup sg and Sun st drivers.
See Installing/reinstalling the sg and the st drivers.
Note:
Support for Solaris 6 GB serial-attached SCSI (SAS) HBAs for tape devices requires a specific Solaris patch level. Ensure that you install the required patches. For supported Solaris versions, see the Oracle Support website.
To configure 6 GB and larger SAS HBAs in Solaris
- Verify that the 6 GB SAS tape device path exists by running the following command in a shell window:
ls -l /dev/rmt | grep cbn
6 GB SAS tape devices should have iport@ in the name path. The following is an example of the output (the tape drive address is highlighted):
1cbn -> ../../devices/pci@400/pci@0/pci@9/LSI,sas@0/iport@8/tape@w500104f000ba856a,0:cbn
- Edit the
/etc/devlink.tab
fileInclude the following lines for every 6 GB SAS tape drive in the
/etc/devlink.tab
file. Replace drive_address with the tape drive address; see the output from step 1 for the tape drive addresses.type=ddi_pseudo;name=sg;addr=wdrive_address,0,1; sg/c\N0t\A1l0 type=ddi_pseudo;name=sg;addr=wdrive_address,1,1; sg/c\N0t\A1l1
Include the following lines for every 6 GB SAS robotic library in the
/etc/devlink.tab
file. Replace drive_address with the tape drive address; see the output from step 1 for the tape drive address.type=ddi_pseudo;name=medium-changer;addr=wdrive_address,0; sg/c\N0t\A1l0 type=ddi_pseudo;name=medium-changer;addr=wdrive_address,1; sg/c\N0t\A1l1
The following are example entries for the
devlink.tab
file:# SCSA devlinks for SAS-2 drives: type=ddi_pseudo;name=sg;addr=w500104f000ba856a,0,1; sg/c\N0t\A1l0 type=ddi_pseudo;name=sg;addr=w500104f000ba856a,1,1; sg/c\N0t\A1l1 # SCSA devlinks for SAS-2 libraries: type=ddi_pseudo;name=medium-changer;addr=w500104f000ba856a,0; sg/c\N0t\A1l0 type=ddi_pseudo;name=medium-changer;addr=w500104f000ba856a,1; sg/c\N0t\A1l1
- Verify that the sg driver SCSI classes are 08 and 0101 by running the following command:
grep sg /etc/driver_aliases
The following is an example of the output:
sg "scsiclass,0101" sg "scsiclass,08"
- If the sg driver SCSI classes are not 08 and 0101, reinstall the sg driver by using the following commands:
rem_drv sg update_drv -d -i "scsiclass,08" sgen add_drv -m '* 0600 root root' -i '"scsiclass,0101" "scsiclass,08"' sg
- Restart the host.
- Verify that the sg drivers exist by running the following command:
ls -l /dev/sg
The following is an example of the output (the output was modified to fit on the page):
c0tw500104f000ba856al0 -> ../../devices/pci@400/pci@0/pci@9/LSI,sas@0/iport@8/sg@w500104f000ba856a,0,1:raw c0tw500104f000ba856al1 -> ../../devices/pci@400/pci@0/pci@9/LSI,sas@0/iport@8/medium-changer@w500104f000ba856a,1:raw
- Verify that the NetBackup sgscan utility recognizes the tape devices by entering the following command:
/usr/openv/volmgr/bin/sgscan
The following is an example of the output:
/dev/sg/c0tw500104f000ba856al0: Tape (/dev/rmt/1): "HP Ultrium 5-SCSI" /dev/sg/c0tw500104f000ba856al1: Changer: "STK SL500"