Veritas NetBackup™ Device Configuration Guide

Last Published:
Product(s): NetBackup (8.0)
  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. AIX
      1.  
        Before you begin configuring NetBackup on AIX
      2.  
        RS/6000 AIX adapter number conventions
      3.  
        About AIX persistent naming support
      4.  
        About configuring robotic control device files in AIX
      5.  
        About device files for SAN Clients on AIX
      6. About configuring tape drive device files in AIX
        1.  
          About choosing a tape driver on AIX
        2.  
          About non-QIC tape drives on AIX
        3.  
          About extended-file marks for drives
        4.  
          About fast-tape positioning (locate-block) on AIX
        5.  
          About no rewind device files on AIX
        6. Creating AIX no rewind device files for tape drives
          1.  
            Example of creating a no rewind device file
        7.  
          Using multiple tape densities on AIX
        8.  
          About SPC-2 SCSI reserve on AIX
        9.  
          Disabling SPC-2 SCSI reserve in AIX
      7.  
        About Sony AIT drives on AIX
      8.  
        AIX command summary
    2. HP-UX
      1.  
        Before you begin configuring NetBackup on HP-UX
      2.  
        About robotic control on HP-UX
      3.  
        About HP-UX device addressing schemes
      4.  
        HP-UX tape drive device file requirements for NetBackup
      5. About device drivers and files for HP-UX persistent DSFs
        1.  
          About device drivers for persistent DSFs
        2.  
          About persistent DSFs for robotic control
        3.  
          About persistent DSFs for tape drive access
        4.  
          About persistent DSF pass-through paths
      6. About configuring persistent DSFs
        1.  
          Creating HP-UX persistent DSFs
        2.  
          Upgrading NetBackup to use HP-UX persistent DSFs
        3.  
          Creating persistent DSF pass-through paths
      7. About HP-UX legacy device drivers and files
        1.  
          About device drivers for legacy device files
        2.  
          About legacy robotic control device files
        3.  
          About legacy tape drive device files
        4.  
          About legacy pass-through paths for tape drives
      8.  
        Creating device files for SAN Clients on HP-UX
      9. About configuring legacy device files
        1. Creating legacy SCSI and FCP robotic controls on HP-UX
          1.  
            Example of how to create a sctl device file for SCSI (PA-RISC)
          2.  
            Example of how to create a sctl device file for FCP (PA-RISC)
          3.  
            Example of how to create sctl device files for FCP (Itanium)
        2.  
          About creating legacy tape drive device files
        3.  
          Creating tape drive pass-through device files
      10.  
        About SPC-2 SCSI reserve on HP-UX
      11.  
        Disabling SPC-2 SCSI reserve in HP-UX
      12.  
        About disabling the HP-UX EMS Tape Device Monitor for a SAN
      13.  
        HP-UX command summary
    3. 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
    4. 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 Oracle 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
    5. 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. 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

Creating tape drive pass-through device files

On media servers, NetBackup creates pass-through paths for tape drives automatically. However, you can create them manually.

NetBackup also uses the tape drive pass-through device files for SAN Client.

Use one of the following two procedures:

To create pass-through tape drive device files

  1. Determine the devices that are attached to the SCSI bus by using the HP-UX ioscan -f command, as follows:
    ioscan -f
    Class    I  H/W Path     Driver S/W State  H/W Type   Description
    =================================================================
    ext_bus  7  0/7/0/       c720   CLAIMED    INTERFACE  SCSI C896 Fast Wide LVD
    target  10  0/7/0/1.0    tgt    CLAIMED    DEVICE
    tape    65  0/7/0/1.0.0  stape  CLAIMED    DEVICE     QUANTUM SuperDLT1
    target  11  0/7/0/1.1    tgt    CLAIMED    DEVICE
    tape    66  0/7/0/1.1.0  stape  CLAIMED    DEVICE     QUANTUM SuperDLT1
    target  12  0/7/0/1.2    tgt    CLAIMED    DEVICE
    autoch  14  0/7/0/1.2.0  schgr  CLAIMED    DEVICE     ADIC Scalar 100
    target  13  0/7/0/1.3    tgt    CLAIMED    DEVICE
    autoch  19  0/7/0/1.3.0  schgr  CLAIMED    DEVICE     IBM ULT3583-TL
    target  14  0/7/0/1.4    tgt    CLAIMED    DEVICE
    tape    21  0/7/0/1.4.0  atdd   CLAIMED    DEVICE     IBM ULT3580-TD1
    target  15  0/7/0/1.5    tgt    CLAIMED    DEVICE
    tape    19  0/7/0/1.5.0  atdd   CLAIMED    DEVICE     IBM ULT3580-TD1

    This example output shows the following:

    • The robotic control for an ADIC Scalar 100 library is on a SCSI bus with an instance number of 7. The SCSI ID is 2, and the LUN is 0. The robotic control for an IBM ULT3583-TL library is on the same SCSI bus at SCSI ID 3 and LUN 0.

    • The ADIC library contains two Quantum Super DLT drives. One has a SCSI ID of 0 and a LUN of 0. The other has a SCSI ID of 1 and a LUN of 0.

    • The IBM library contains two IBM Ultrium LTO drives. One has a SCSI ID of 4 and a LUN of 0. The other has a SCSI ID of 5 and a LUN of 0.

      Use the IBM atdd driver when you configure IBM tape drives on HP-UX. Configure atdd and BEST device paths according to the IBM driver documentation. Do not configure atdd for robotic control of IBM robots. For the latest recommended atdd driver version from IBM, check the Veritas support Web site.

  2. Create the pass-through device files for the tape drives, as follows:
    cd /dev/sctl
    /usr/sbin/mknod c7t0l0 c 203 0x070000
    /usr/sbin/mknod c7t1l0 c 203 0x071000
    /usr/sbin/mknod c7t4l0 c 203 0x074000
    /usr/sbin/mknod c7t5l0 c 203 0x075000

    When you use the HP-UX mknod command for tape drives, the target is the SCSI ID of the tape drive. It is not the SCSI ID of the robotic control.

    The previous commands create the following pass-through device files.

    /dev/sctl/c7t0l0
    /dev/sctl/c7t1l0
    /dev/sctl/c7t4l0
    /dev/sctl/c7t5l0

    Although the pass-through device files for tape drives are used during NetBackup operation, they are not used during NetBackup configuration. During NetBackup tape drive configuration, use the following device files to configure the tape drives.

    /dev/rmt/c7t0d0BESTnb
    /dev/rmt/c7t1d0BESTnb
    /dev/rmt/c7t4d0BESTnb
    /dev/rmt/c7t5d0BESTnb

To create SAN client pass-through device files

  1. Determine the devices that are attached to the SCSI bus by using the HP-UX ioscan -f command, as follows:
    ioscan -f
    Class    I  H/W Path                Driver    S/W State   H/W Type    Description
    =================================================================================
    ext_bus  9  0/3/1/0.1.22.255.0      fcd_vbus  CLAIMED     INTERFACE   FCP Device Interface
    target   4  0/3/1/0.1.22.255.0.0    tgt       CLAIMED     DEVICE
    tape     6  0/3/1/0.1.22.255.0.0.0  stape     CLAIMED     DEVICE      ARCHIVE Python
    tape     7  0/3/1/0.1.22.255.0.0.1  stape     CLAIMED     DEVICE      ARCHIVE Python

    This example output shows that the instance number of the Fibre Channel HBA is 9. It also shows that the target mode drivers on the Fibre Transport media server appear as ARCHIVE Python devices. One has a SCSI ID of 0 and a LUN of 0; the other has a SCSI ID of 0 and a LUN of 1.

  2. Determine the character major number of the sctl driver by using the following command:
    lsdev -d sctl
    Character  Block  Driver  Class
    203        -1     sctl    ctl

    The output from this command shows that the character major number for the sctl driver is 203.

  3. Create the pass-through device files, as follows:
    cd /dev/sctl
    /usr/sbin/mknod c9t0l0 c 203 0x090000
    /usr/sbin/mknod c9t0l1 c 203 0x090100

    The following describes the device file name:

    • c9 defines the instance number of the interface card.

    • t0 defines the SCSI ID (the target).

    • l1 defines the LUN (the first character is the letter "l").

  4. Verify that the device files were created, as follows:
    # ls -l /dev/sctl
    total 0
    crw-r--r--   1 root       sys        203 0x090000 Nov  1 13:19 c9t0l0
    crw-r--r--   1 root       sys        203 0x090100 Nov  1 13:19 c9t0l1