Veritas NetBackup™ SAN Client and Fibre Transport Guide

Last Published:
Product(s): NetBackup (8.3.0.1)
  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
        1.  
          Example of creating a no rewind device file
  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

Marking the Fibre Transport media server HBA ports

You must mark the ports on the QLogic HBAs that you want to operate in target mode. The process modifies the port device IDs in NVRAM. When the FT server starts, the NetBackup target mode driver binds automatically to the QLogic HBA ports that you marked.

Before you mark ports, you must start nbhba mode.

See Starting nbhba mode.

The following procedures describe how to mark the HBA ports and if necessary how to reverse this process and return the ports to the initiator mode driver:

You must be the root user to make these changes.

To mark the HBA ports

  1. Display the QLogic HBA ports on the media server by using the nbhba command with the -l option. The following is an example; output on your system may differ:
    /usr/openv/netbackup/bin/admincmd/nbhba -l
    1 2312 21:00:00:E0:8B:83:9D:A1 "QLA2342 " 0 0 101
    2 2312 21:01:00:E0:8B:A3:9D:A1 "QLA2342 " 1 0 101
    3 2312 21:00:00:E0:8B:8F:28:7B "QLA2342 " 0 0 101
    4 2312 21:01:00:E0:8B:AF:28:7B "QLA2342 " 1 0 101

    For the QLA-234x series, the port WWNs on the same card differ in the second byte and the sixth byte. This output shows two, two-port HBAs. Lines 1 and 2 are one HBA; lines 3 and 4 are the other HBA. The HBAs are in initiator mode: the second rightmost column shows 0, and the rightmost column does not begin with 8.

    Alternatively, use the nbhba -L option to produce verbose output, which lets you identify the mode more easily.

  2. Mark the ports by using the nbhba command. The following is the syntax:
    /usr/openv/netbackup/bin/admincmd/nbhba -modify -wwn string 
    -mode target

    For example, the following two commands change the two ports on one of the HBAs from the example output in step 1:

    nbhba -modify -wwn 21:00:00:E0:8B:8F:28:7B -mode target
    nbhba -modify -wwn 21:01:00:E0:8B:AF:28:7B -mode target
  3. Verify the changes by using the nbhba command and -L option to display the HBA card ports on the server. The following is an example; output on your system may differ:
    /usr/openv/netbackup/bin/admincmd/nbhba -L
    HBA Port #1 
     Device ID = 2312 
     World Wide Name = 21:00:00:E0:8B:83:9D:A1 
     Model Name = "QLA2342 " 
     Port = 0 
     Mode = initiator (designated for other use)(101)
    HBA Port #2 
     Device ID = 2312
     World Wide Name = 21:01:00:E0:8B:A3:9D:A1 "QLA2342
     Model Name = "QLA2342 "
     Port = 1
     Mode = initiator (designated for other use)(101)
    HBA Port #3
     World Wide Name = 21:00:00:E0:8B:8F:28:7B
     Slot = ""
     Port = 0
     Fibre Not Attached
     Mode = target (designated for FT Server)(8101)
    HBA Port #4
     World Wide Name = 21:01:00:E0:8B:AF:28:7B
     Slot = ""
     Port = 1
     Fibre Not Attached
     Mode = target (designated for FT Server)(8101)

    The nbhba -l option also produces the output that lets you identify the mode:

    /usr/openv/netbackup/bin/admincmd/nbhba -l
    1 2312 21:00:00:E0:8B:83:9D:A1 "QLA2342 " 0 0 101
    2 2312 21:01:00:E0:8B:A3:9D:A1 "QLA2342 " 1 0 101
    3 2312 21:00:00:E0:8B:8F:28:7B "QLA2342 " 0 1 8101
    4 2312 21:01:00:E0:8B:AF:28:7B "QLA2342 " 1 1 8101

    The rightmost two columns show the ports that are marked for target mode: the second rightmost column shows 1, and the rightmost column begins with 8. The other digits in the rightmost column are not significant.

  4. If necessary, transfer the HBAs to the appropriate media servers.
  5. If necessary, connect the HBAs to the SAN.
  6. Continue by configuring the FT services.

    See Configuring the media server Fibre Transport services.

To revert to the initiator mode driver

  • Invoke the nbhba command on the NetBackup FT server in which the HBA is installed. The following is the command syntax:
    /usr/openv/netbackup/bin/admincmd/nbhba -modify -wwn 
    world_wide_port_name -mode initiator