Veritas NetBackup™ Device Configuration Guide

Last Published:
Product(s): NetBackup (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

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

  1. 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.

  2. 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.

  3. 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.

  4. Verify that Solaris created the device nodes for all the tape devices by using the following command:

    ls -l /dev/rmt/*cbn

  5. 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.

  6. Verify that the <command>sg</command> driver finds all of the robots and tape drives.