NetBackup™ SAN Client and Fibre Transport Guide

Last Published:
Product(s): NetBackup & Alta Data Protection (10.3.0.1, 10.3)
  1. Introducing SAN Client and Fibre Transport
    1.  
      About NetBackup SAN Client and Fibre Transport
    2.  
      About Fibre Transport
    3.  
      About Fibre Transport media servers
    4.  
      About SAN clients
    5.  
      About the Fibre Transport Service Manager
    6.  
      About NetBackup Release Notes
  2. Planning your deployment
    1.  
      Planning your SAN Client deployment
    2.  
      SAN Client operational notes
    3. About SAN Client storage destinations
      1.  
        About SAN Client disk storage destinations
      2. About SAN Client tape storage destinations
        1.  
          SAN Client tape storage limitations
    4.  
      How to choose SAN Client and Fibre Transport hosts
    5.  
      About NetBackup SAN Client support for agents
    6.  
      About NetBackup SAN Client support for clustering
    7.  
      About NetBackup SAN Client support for Windows Hyper-V Server
    8.  
      About NetBackup SAN Client unsupported restores
    9.  
      About Fibre Transport throughput
    10.  
      Converting a SAN media server to a SAN client
  3. Preparing the SAN
    1.  
      Preparing the SAN
    2.  
      About zoning the SAN for Fibre Transport
    3.  
      About zoning the SAN for Fibre Transport for a 16-gigabit target mode HBA support
    4.  
      About HBAs for SAN clients and Fibre Transport media servers
    5.  
      About the 16-gigabit target mode HBAs for SAN clients and Fibre Transport media servers
    6.  
      When selecting the HBA ports for SAN Client
    7.  
      About supported SAN configurations for SAN Client
  4. Licensing SAN Client and Fibre Transport
    1.  
      About SAN Client installation
    2.  
      About the SAN Client license key
    3.  
      When upgrading SAN Client and Fibre Transport
  5. Configuring SAN Client and Fibre Transport
    1.  
      Configuring SAN Client and Fibre Transport
    2. Configuring a Fibre Transport media server
      1.  
        About the target mode driver
      2.  
        About nbhba mode and the ql2300_stub driver
      3.  
        About FC attached devices
      4.  
        How to identify the HBA ports
      5.  
        About HBA port detection on Solaris
      6.  
        About Fibre Transport media servers and VLANs
      7.  
        Starting nbhba mode
      8.  
        Marking the Fibre Transport media server HBA ports
      9.  
        Configuring the media server Fibre Transport services
      10.  
        Configuring the media server Fibre Transport services for a 16-gigabit target mode HBA support
      11.  
        Displaying the FTMS state for a 16-gigabit target mode HBA support
      12.  
        Identifying the HBA ports for a 16-gigabit target mode HBA support
    3. Configuring SAN clients
      1.  
        About configuring firewalls for SAN clients
      2.  
        SAN client driver requirements
      3.  
        Configuring the SAN client Fibre Transport service
    4. Configuring SAN clients in a cluster
      1.  
        Registering a SAN client cluster virtual name
      2.  
        Setting NetBackup configuration options by using the command line
    5.  
      About configuring Fibre transport properties
    6.  
      Configuring Fibre Transport properties
    7. Fibre transport properties
      1.  
        About Linux concurrent FT connections
    8.  
      About SAN client usage preferences
    9. Configuring SAN client usage preferences
      1.  
        SAN client usage preferences
  6. Managing SAN clients and Fibre Transport
    1.  
      Enabling or disabling the Fibre Transport services
    2.  
      Enabling or disabling the Fibre Transport services for a 16-gigabit target mode HBA support
    3.  
      Rescanning for Fibre Transport devices from a SAN client
    4.  
      Viewing SAN Client Fibre Transport job details
    5.  
      Viewing Fibre Transport traffic
    6.  
      Adding a SAN client
    7.  
      Deleting a SAN client
  7. Disabling SAN Client and Fibre Transport
    1.  
      About disabling SAN Client and Fibre Transport
    2.  
      Disabling a SAN client
    3.  
      Disabling a Fibre Transport media server
    4.  
      Disabling a Fibre Transport media server for a 16-gigabit target mode HBA support
  8. Troubleshooting SAN Client and Fibre Transport
    1.  
      About troubleshooting SAN Client and Fibre Transport
    2.  
      SAN Client troubleshooting tech note
    3.  
      Viewing Fibre Transport logs
    4. About unified logging
      1.  
        About using the vxlogview command to view unified logs
      2.  
        Examples of using vxlogview to view unified logs
    5.  
      Stopping and starting Fibre Transport services
    6.  
      Stopping and starting Fibre Transport services for a 16-gigabit target mode HBA support
    7.  
      Backups failover to LAN even though Fibre Transport devices available
    8.  
      Kernel warning messages when Veritas modules load
    9.  
      SAN client service does not start
    10.  
      SAN client Fibre Transport service validation
    11.  
      SAN client does not select Fibre Transport
    12.  
      Media server Fibre Transport device is offline
    13.  
      No Fibre Transport devices discovered
  9. Appendix A. AIX Specific Configuration Details
    1.  
      AIX Reference Information
    2.  
      Before you begin configuring NetBackup on AIX
    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 non-QIC tape drives on AIX
      2.  
        About no rewind device files on AIX
      3.  
        Creating AIX no rewind device files for tape drives
  10. Appendix B. HP-UX Specific Configuration Details
    1.  
      HP-UX Reference Information
    2.  
      Before you begin configuring NetBackup on HP-UX
    3.  
      About HP-UX device drivers for legacy device files
    4.  
      About legacy robotic control device files
    5.  
      About legacy tape drive device files
    6.  
      About legacy pass-through paths for tape drives
    7.  
      Creating device files for SAN Clients on HP-UX
    8. 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
  11.  
    Index

Configuring the media server Fibre Transport services for a 16-gigabit target mode HBA support

You must configure the media server FT services before you configure the SAN clients. The FT server must run on the media servers so that the client operating system discovers the target mode driver (the FT device). One service (nbftsrvr) comprises of the NetBackup FT server that runs on media servers.

The nbftsrv_config script configures the media server for Fibre Transport. In this process, the script does the following:

  • Installs the required drivers

  • Installs the FT server start-up scripts

  • Starts the FT server

    When the FT server starts, the NetBackup target mode driver binds automatically to the QLogic or Emulex HBA ports. The HBA ports operate in target mode until you disable FTMS.

Configure the FT services on every NetBackup media server that connects to SAN clients.

For procedures, see the following:

You must be the root user.

Note:

After you configure the Fibre Transport media servers using the nbftsrv_config and the nbftserver scripts, reload the target driver for the HBA port on the NetBackup SAN clients that were used for backup and restore. This step ensures that the client operating system detects the tape devices that the Fibre Transport media servers export. Alternatively, you can restart the client computers to reload the drivers and refresh the device tree.

If you plan to use Emulex LPe31000/LPe35000 Series as the target mode HBAs, ensure that the firmware versions are supported. If the firmware is not supported, upgrade it to the specific version before configuring SAN Client and Fibre Transport. For information about the supported firmware versions, see the hardware compatibility list at the following location:

http://www.netbackup.com/compatibility

To configure Fibre Transport services on Linux

  1. Run the nbftsrv_config script. The following is an example; output on your system may differ:
    /usr/openv/netbackup/bin/admincmd/nbftsrv_config -scst -install
    Checking for SCST drivers and firmwares in the package. [yes]
    Checking if the server is not NetBackup Appliance. [yes]
    Checking for kernel version 4.18.0-372.9.1. [yes]
    Checking for QLogic QLE2562 8Gb or QLE2692 16Gb or QLE2770 
    QLE2772 32Gb, or other supported QLogic 16/32Gb HBA cards on 
    the server. [yes]
    Checking for Emulex LPe31002 16Gb, LPe31004 16Gb, and other 
    supported Emulex 32Gb HBA cards on the server. [yes]
    
    
    DISCLAIMER:
    -----------
    NOTE:
    1. When you install the SAN client with 16Gb/32Gb HBA, the script stops the original qla2xxx and lpfc driver and updates the firmware ql2500_fw.bin. QLogic QLE2562 8Gb and QLE2692 16Gb and QLE2770 QLE2772 32Gb HBA models, Emulex LPe31002 16Gb, LPe31004 16Gb, and other qualified QLogic/Emulex 32Gb HBA models are supported by this NetBackup version.
    2. Ensure that there is no other process that uses the HBAs. If there is an active process that uses qla2xxx or lpfc, manually restart the process after the installation completes.
    3. If you use the SANsurfer agent during the deployment of the environment, the script stops and restarts the SANsurfer agent daemon (qlremote).
    4. Stop all the backup jobs that use the FT user interface.
    
    
    Do you acknowledge this disclaimer? [y,n] (n) y
    
  2. The QLogic drivers are reloaded so that the HBA ports can be detected during this session.
    Proceeding to deploy SCST environment  [ok]
    
    Stopping the NetBackup Fibre Transport Server.
    Waiting for nbftsrvr to shut down (this may take some time).
    
    HBA-Type         Port WWN                Status   Supported Speeds               Current Speed
    LPe31000-M6-D    10:00:00:10:9b:df:92:0e Online   4 Gbit, 8 Gbit, 16 Gbit        16 Gbit
    QLE2772          21:00:f4:c7:aa:0c:2a:87 Online   8 Gbit, 16 Gbit, 32 Gbit       32 Gbit
    QLE2692          21:00:f4:c7:aa:0b:d6:88 Online   4 Gbit, 8 Gbit, 16 Gbit        16 Gbit
    QLE2692          21:00:f4:c7:aa:0b:d6:89 Online   4 Gbit, 8 Gbit, 16 Gbit        16 Gbit
    QLE2772          21:00:f4:c7:aa:0c:2a:86 Online   8 Gbit, 16 Gbit, 32 Gbit       32 Gbit
    LPe35000-M2-D    10:00:00:10:9b:f1:63:a8 Linkdown 8 Gbit, 16 Gbit, 32 Gbit       unknown
    
    NOTE:
    The types of HBA cards listed below are filtered by the chip model. All of these HBA cards are not verified. Choose supported HBA card according to NetBackup hardware compatibility list. Some of the WWNs may be used to connect to an external storage and other external devices.
    
    Do you want to continue? [y,n] (n)
    
  3. Enter the port numbers and make sure of the operation warnings during this session.
    Please input the Port WWNs you want to use as the targets (separated by commas like: wwn1,wwn2...):10:00:00:10:9b:1d:4c:6a,10:00:00:10:9b:1d:4c:6b
    The input is: 10:00:00:10:9b:1d:4c:6a,10:00:00:10:9b:1d:4c:6b
    The targets you defined are Emulex HBAs
    The targets you defined: 10:00:00:10:9b:1d:4c:6a 10:00:00:10:9b:1d:4c:6b
    Do you want to redefine the targets? [y,n] (n) n
    Do you want to add additional targets? [y,n] (n) n
    The targets you defined: 10:00:00:10:9b:1d:4c:6a 10:00:00:10:9b:1d:4c:6b
    The targets you have defined contain 16Gb HBA cards.
    
    NOTE:
    1. Make sure that you do not use a WWN that is used to connect to external storage.
    2. Make sure to define the input WWNs as targets.
    3. Make sure the WWNs can be zoned with WWNs of clients.
    Do you want to continue to setup the WWNs as targets? [y,n] (n) y
  4. The FTMS environment is deployed.
    --------------------------------------------
    FTMS environment installation started.
    --------------------------------------------
    Successfully created the dependent path: /var/lib/scst/pr.
    Successfully created the dependent path: /var/lib/scst/vdev_mode_pages.
    Successfully copied /usr/openv/netbackup/bin/driver/lancerg6_A12.8.340.8.grp to /lib/firmware/LPE31004.grp.
    Successfully copied /usr/openv/netbackup/bin/driver/scst/ocs_fc_scst.ko.3.10.0-1160.el7.x86_64 to /lib/modules/3.10.0-1160.15.2.el7.x86_64/extra/ocs_fc_scst.ko.
    Successfully copied /usr/openv/netbackup/bin/driver/scst/scst.ko.3.10.0-1160.el7.x86_64 to /lib/modules/3.10.0-1160.15.2.el7.x86_64/extra/scst.ko.
    Successfully copied /usr/openv/netbackup/bin/driver/scst/scst_user.ko.3.10.0-1160.el7.x86_64 to /lib/modules/3.10.0-1160.15.2.el7.x86_64/extra/scst_user.ko.
    Successfully created /etc/modprobe.d/ocs_fc_scst.conf.
    Successfully copied /usr/openv/netbackup/bin/nbftsrvr to /usr/openv/netbackup/bin/nbftsrvr_old.
    Successfully copied /usr/openv/netbackup/bin/goodies/nbftserver_scst to /etc/rc.d/init.d/nbftserver.
    Successfully linked /etc/rc.d/init.d/nbftserver /etc/rc.d/rc2.d/S21nbftserver.
    Successfully linked /etc/rc.d/init.d/nbftserver /etc/rc.d/rc3.d/S21nbftserver.
    Successfully linked /etc/rc.d/init.d/nbftserver /etc/rc.d/rc5.d/S21nbftserver.
    Successfully linked /etc/rc.d/init.d/nbftserver /etc/rc.d/rc0.d/K03nbftserver.
    Successfully linked /etc/rc.d/init.d/nbftserver /etc/rc.d/rc1.d/K03nbftserver.
    Successfully linked /etc/rc.d/init.d/nbftserver /etc/rc.d/rc6.d/K03nbftserver.
    Successfully enabled nbftserver.
    Successfully created /etc/modules-load.d/scst.conf.
    Successfully find PCIID:0000:07:00.0 for target:10:00:00:10:9b:1d:4c:6a
    Successfully find PCIID:0000:07:00.1 for target:10:00:00:10:9b:1d:4c:6b
    Successfully bind target mode for pciid: 0000:07:00.0.
    Successfully bind target mode for pciid: 0000:07:00.1.
    Successfully rebind emulex target ports.
    Successfully modify the attribute of /sys/kernel/scst_tgt/targets/ocs_xe201/10:00:00:10:9b:1d:4c:6a/enabled with value 1.
    Successfully write /sys/class/fc_host/host13/issue_lip with value 1
    Enable target: 10:00:00:10:9b:1d:4c:6a
    Successfully modify the attribute of /sys/kernel/scst_tgt/targets/ocs_xe201/10:00:00:10:9b:1d:4c:6b/enabled with value 1.
    Successfully write /sys/class/fc_host/host14/issue_lip with value 1
    Enable target: 10:00:00:10:9b:1d:4c:6b
    Previous initramfs image is saved at /boot/initramfs-3.10.0-1160.15.2.el7.x86_64.img.03-19-21.19:31:51.
    Running dracut, it may take several minutes to complete...
    /sbin/dracut succeeded
    Successfully moved /boot/initramfs-3.10.0-1160.15.2.el7.x86_64.img.tmp to /boot/initramfs-3.10.0-1160.15.2.el7.x86_64.img
    NetBackup Fibre Transport Server started.
    -------------------------------
    Driver ocs_fc_scst is loaded
    -------------------------------
    Driver scst is loaded
    -------------------------------
    Driver scst_user is loaded
    
    --------------------------------------------
    FTMS environment installation completed.
    --------------------------------------------