DOCUMENTATION: Ultrium 3 SCSI tape drive support issues on Solaris when using VERITAS NetBackup (tm) 5.1.

Article:TECH39191  |  Created: 2009-01-01  |  Updated: 2009-01-01  |  Article URL http://www.symantec.com/docs/TECH39191
Article Type
Technical Solution


Environment

Issue



DOCUMENTATION: Ultrium 3 SCSI tape drive support issues on Solaris when using VERITAS NetBackup (tm) 5.1.

Solution



Manual
VERITAS NetBackup (tm) Enterprise Server and NetBackup Server Version 5.x Hardware Compatibility List for all supported drives.

Modification type
Supplement

Modification
Solaris does not support Ultrium 3 tape drives on parallel SCSI Host Bus Adapters (HBA) that use the glm driver.  Ultrium 3 drives are high-speed devices that, with compression enabled, may exceed the performance of HBAs running the glm driver.  

Symantec recommends using SCSI HBAs that use the qus driver when direct-attaching Ultrium 3 SCSI tape drives to Solaris systems. Contact Sun or your HBA vendor to obtain the current qus driver and patches, or information on HBAs that support Ultrium 3 tape drives.      

Symantec's VERITAS NetBackup (tm) does not support HP Ultrium 3 drives with WORM on Solaris using any parallel SCSI HBA. HP Ultrium 3 WORM requires the use of 16-byte SCSI CDBs and parallel SCSI HBAs do not handle these command descriptor blocks (CDBs) correctly.  Attempting to use the glm driver can result in a SCSI bus reset when a 16-byte CDB is received.  This issue can occur regardless of the NetBackup version installed on the system.  The qus driver is the supported method when direct-attaching Ultrium 3 SCSI tape drives to Solaris systems.

To identify the driver your SCSI HBA is using, use the sysdef -D command.  The following section of sysdef -D output is from a Sunfire V240 server.  
pci instance #1 is the expansion PCI bus, which has a PCI Dual Ultra3 card running the qus driver at pci instance #0
pci instance #2 is the standard Ultra160 card running the glm driver:

...
pci, instance #0 (driver name: pcisch)
network, instance #0 (driver name: bge)
network, instance #1 (driver name: bge)
pci, instance #1 (driver name: pcisch)
isa, instance #0 (driver name: ebus)
...
SUNW,XVR-100, instance #0 (driver name: pfb)
pci, instance #0 (driver name: pci_pci)
scsi, instance #0 (driver name: qus)
sd (driver name: sd)
st (driver name: st)
sd, instance #31 (driver name: sd)
(snip)
sg, instance #270 (driver name: sg)
(snip)
st, instance #404 (driver name: st)
scsi, instance #1 (driver name: qus)
sd (driver name: sd)
st (driver name: st)
sd, instance #46 (driver name: sd)
(snip)
sg, instance #405 (driver name: sg)
(snip)
sg, instance #406 (driver name: sg)
 (snip)
st, instance #539 (driver name: st)
pci, instance #2 (driver name: pcisch)
scsi, instance #0 (driver name: glm)
disk (driver name: sd)
tape (driver name: st)
sd, instance #0 (driver name: sd)
(snip)
sg, instance #0 (driver name: sg)
(snip)
st, instance #141 (driver name: st)
scsi, instance #1 (driver name: glm)
disk (driver name: sd)
tape (driver name: st)
sd, instance #15 (driver name: sd)
(snip)
sg, instance #14 (driver name: sg)
(snip)
st, instance #269 (driver name: st)



Legacy ID



277299


Article URL http://www.symantec.com/docs/TECH39191


Terms of use for this information are found in Legal Notices