Veritas NetBackup™ Device Configuration Guide

Last Published:
Product(s): NetBackup (8.3.0.1, 8.3, 8.2, 8.1.2)
  1. Introducing device configuration
    1.  
      Using this guide
    2. General device configuration sequence
      1.  
        Configuration cautions
    3.  
      About the NetBackup compatibility lists
  2. Section I. Operating systems
    1. Linux
      1.  
        Before you begin on Linux
      2. About the required Linux SCSI drivers
        1.  
          About the st driver debug mode
      3.  
        Verifying the Linux drivers
      4. About configuring robot and drive control for Linux
        1.  
          About the Linux robotic control device files
        2.  
          About the Linux tape drive device files
      5.  
        Verifying the device configuration on Linux
      6.  
        About SAN clients on Linux
      7.  
        About SCSI persistent bindings for Linux
      8.  
        About Emulex HBAs
      9.  
        Utilities to test SCSI devices
      10.  
        Linux command summary
    2. Solaris
      1.  
        Before you begin on Solaris
      2.  
        About the NetBackup sg driver
      3.  
        Determining if the NetBackup sg driver is installed
      4.  
        Special configuration for the StorEdge Network Foundation HBA driver
      5.  
        About binding Fibre Channel HBA drivers
      6.  
        Configuring Solaris 10 x86 for multiple drive paths
      7. Installing/reinstalling the sg and the st drivers
        1.  
          st.conf file example
        2.  
          sg.conf file example
        3.  
          sg.links file example
      8.  
        Configuring 6 GB and larger SAS HBAs in Solaris
      9.  
        Preventing Solaris driver unloading
      10. About Solaris robotic controls
        1.  
          About SCSI and FCP robotic controls on Solaris
        2.  
          Examples of SCSI and FCP robotic control device files on Solaris
      11. About Solaris tape drive device files
        1.  
          About Berkeley-style close
        2.  
          About no rewind device files on Solaris
        3.  
          About fast-tape positioning (locate-block) on Solaris
        4.  
          About SPC-2 SCSI reserve on Solaris
        5.  
          Disabling SPC-2 SCSI reserve on Solaris
        6.  
          About nonstandard tape drives
      12. Configuring Solaris SAN clients to recognize FT media servers
        1.  
          Adding the FT device entry to the st.conf file
        2.  
          Modifying the st.conf file so that Solaris discovers devices on two LUNS
      13.  
        Uninstalling the sg driver on Solaris
      14.  
        Solaris command summary
    3. Windows
      1.  
        Before you begin configuring NetBackup on Windows
      2.  
        About tape device drivers on Windows
      3.  
        Attaching devices to a Windows system
  3. Section II. Robotic storage devices
    1. Robot overview
      1.  
        NetBackup robot types
      2. NetBackup robot attributes
        1.  
          ACS robots
        2.  
          TLD robots
      3.  
        Table-driven robotics
      4.  
        Robotic test utilities
      5. Robotic processes
        1.  
          Processes by robot type
        2.  
          Robotic process example
    2. Oracle StorageTek ACSLS robots
      1.  
        About Oracle StorageTek ACSLS robots
      2.  
        Sample ACSLS configurations
      3.  
        Media requests for an ACS robot
      4.  
        About configuring ACS drives
      5.  
        Configuring shared ACS drives
      6.  
        Adding tapes to ACS robots
      7. About removing tapes from ACS robots
        1.  
          Removing tapes using the ACSLS utility
        2.  
          Removing tapes using NetBackup
      8. Robot inventory operations on ACS robots
        1.  
          Configuring a robot inventory filtering on ACS robots
      9. NetBackup robotic control, communication, and logging
        1.  
          NetBackup robotic control, communication, and logging for Windows systems
        2. NetBackup robotic control, communication, and logging for UNIX systems
          1.  
            NetBackup ACS daemon (acsd)
          2.  
            NetBackup ACS SSI event logger (acssel)
          3.  
            Using acssel with a different socket name
          4.  
            NetBackup ACS storage server interface (acsssi)
          5.  
            About the ACS_SSI_SOCKET configuration option
          6.  
            Starting acsssi manually
          7.  
            Optional environment variables
      10. ACS robotic test utility
        1.  
          acstest on Windows systems
        2.  
          acstest on UNIX systems
      11.  
        Changing your ACS robotic configuration
      12. ACS configurations supported
        1.  
          Multiple ACS robots with one ACS library software host
        2.  
          Multiple ACS robots and ACS library software hosts
      13.  
        Oracle StorageTek ACSLS firewall configuration
    3. Device configuration examples
      1.  
        An ACS robot on a Windows server example
      2.  
        An ACS robot on a UNIX server example

sg.links file example

The following /usr/openv/volmgr/bin/driver/sg.links file example shows targets 0-15 and LUNs 0-7. It also includes entries for three StorEdge Network Foundation HBA ports.

The sg.build -mt option does not affect FCP targets, but the -ml option does. The Solaris luxadm command detected three ports (identified by their World Wide Names). Therefore, the sg.build script created entries for LUNs 0 through 7 for those three ports.

The field separator between the addr=x, y; field and the sg/ field is a tab. The addr= field uses hexadecimal notation, and the sg/ field uses decimal values.

# begin SCSA Generic devlinks file - creates nodes in /dev/sg
type=ddi_pseudo;name=sg;addr=0,0;       sg/c\N0t0l0
type=ddi_pseudo;name=sg;addr=0,1;       sg/c\N0t0l1
type=ddi_pseudo;name=sg;addr=0,2;       sg/c\N0t0l2
type=ddi_pseudo;name=sg;addr=0,3;       sg/c\N0t0l3
type=ddi_pseudo;name=sg;addr=0,4;       sg/c\N0t0l4
type=ddi_pseudo;name=sg;addr=0,5;       sg/c\N0t0l5
type=ddi_pseudo;name=sg;addr=0,6;       sg/c\N0t0l6
type=ddi_pseudo;name=sg;addr=0,7;       sg/c\N0t0l7
type=ddi_pseudo;name=sg;addr=1,0;       sg/c\N0t1l0
type=ddi_pseudo;name=sg;addr=1,1;       sg/c\N0t1l1
...
<entries omitted for brevity>
...
type=ddi_pseudo;name=sg;addr=f,5;       sg/c\N0t15l5
type=ddi_pseudo;name=sg;addr=f,6;       sg/c\N0t15l6
type=ddi_pseudo;name=sg;addr=f,7;       sg/c\N0t15l7
type=ddi_pseudo;name=sg;addr=w500104f0008d53c3,0;       sg/c\N0t\A1l0
type=ddi_pseudo;name=sg;addr=w500104f0008d53c3,1;       sg/c\N0t\A1l1
type=ddi_pseudo;name=sg;addr=w500104f0008d53c6,0;       sg/c\N0t\A1l0
type=ddi_pseudo;name=sg;addr=w500104f0008d53c6,1;       sg/c\N0t\A1l1
type=ddi_pseudo;name=sg;addr=w500104f0008d53c9,0;       sg/c\N0t\A1l0
type=ddi_pseudo;name=sg;addr=w500104f0008d53c9,1;       sg/c\N0t\A1l1
type=ddi_pseudo;name=sg;addr=w500104f0008d53cc,0;       sg/c\N0t\A1l0
type=ddi_pseudo;name=sg;addr=w500104f0008d53cc,1;       sg/c\N0t\A1l1
type=ddi_pseudo;name=sg;addr=w500104f0008d53b9,0;       sg/c\N0t\A1l0
type=ddi_pseudo;name=sg;addr=w500104f0008d53b9,1;       sg/c\N0t\A1l1
type=ddi_pseudo;name=sg;addr=w500104f0008d53c3,0;       sg/c\N0t\A1l0
type=ddi_pseudo;name=sg;addr=w500104f0008d53c3,1;       sg/c\N0t\A1l1
type=ddi_pseudo;name=sg;addr=w500104f0008d53c6,0;       sg/c\N0t\A1l0
type=ddi_pseudo;name=sg;addr=w500104f0008d53c6,1;       sg/c\N0t\A1l1
type=ddi_pseudo;name=sg;addr=w500104f0008d53c9,0;       sg/c\N0t\A1l0
type=ddi_pseudo;name=sg;addr=w500104f0008d53c9,1;       sg/c\N0t\A1l1
type=ddi_pseudo;name=sg;addr=w500104f0008d53cc,0;       sg/c\N0t\A1l0
type=ddi_pseudo;name=sg;addr=w500104f0008d53cc,1;       sg/c\N0t\A1l1
type=ddi_pseudo;name=sg;addr=w500104f0008d53b9,0;       sg/c\N0t\A1l0
type=ddi_pseudo;name=sg;addr=w500104f0008d53b9,1;       sg/c\N0t\A1l1
# end SCSA devlinks