Veritas NetBackup™ SAN Client and Fibre Transport Guide

Last Published:
Product(s): NetBackup (8.0)
  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.  
      About SAN Client best practices
    3.  
      SAN Client operational notes
    4. 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
    5.  
      How to choose SAN Client and Fibre Transport hosts
    6.  
      About NetBackup SAN Client support for agents
    7.  
      About NetBackup SAN Client support for clustering
    8.  
      About NetBackup SAN Client support for Windows Hyper-V Server
    9.  
      About NetBackup SAN Client unsupported restores
    10.  
      About Fibre Transport throughput
    11.  
      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 HBAs for SAN clients and Fibre Transport media servers
    4.  
      When selecting the HBA ports for SAN Client
    5.  
      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
    3. Configuring SAN clients
      1.  
        About configuring firewalls on 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.  
      Rescanning for Fibre Transport devices from a SAN client
    3.  
      Viewing SAN Client Fibre Transport job details
    4.  
      Viewing Fibre Transport traffic
    5.  
      Adding a SAN client
    6.  
      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
  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.  
      Backups failover to LAN even though Fibre Transport devices available
    7.  
      Kernel warning messages when Veritas modules load
    8.  
      SAN client service does not start
    9.  
      SAN client Fibre Transport service validation
    10.  
      SAN client does not select Fibre Transport
    11.  
      Media server Fibre Transport device is offline
    12.  
      No Fibre Transport devices discovered

How to identify the HBA ports

If the computer on which you mark ports contains multiple HBAs, it may be difficult to determine how the World Wide Names (WWNs) relate to the HBAs. The NetBackup nbhba command that marks the HBA ports requires the port WWN. The port WWN also may be known as the World Wide Port Name (WWPN).

To avoid problems, you can install all of the QLogic HBAs in a NetBackup media server that has no other Fibre Channel HBAs installed. You can mark all HBA ports and then install the HBAs in the appropriate NetBackup media servers.

Warning:

A QLogic HBA may exist as a chipset on a motherboard. To avoid problems, you should determine if the computer contains built-in QLogic ports.

If you cannot mark ports in a computer that has only the QLogic HBAs that you want to mark, the following may help:

  • The HBA may identify the port WWNs on the card. Examine the HBA for the WWNs.

  • The Fibre Channel switch may display WWNs for attached and operational HBA ports.

  • The SAN utility software may provide the capability to list the WWNs of the HBA ports.

  • On Solaris 10, you can list WWNs for native drivers by using the fcinfo hba-port command.

  • The NetBackup nbhba command -l option lets you compare the port WWN addresses easily. (The computer must be in nbhba mode.) For the QLA-234x series, the port WWNs on the same card differ in the second byte and the sixth byte. The following example shows two, two-port HBAs. Lines 1 and 2 are one HBA; lines 3 and 4 are the other HBA.

    /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

    This output also shows that the ports are in initiator mode. The second rightmost column shows 0, and the rightmost column does not begin with 8.

  • If the HBA contains LEDs on the metal mounting bracket, the color changes to green after you mark a port (yellow is initiator mode). (The computer must be in nbhba mode.) You can see if you marked the ports in the correct card. If you did not, you can return those ports to initiator mode and then mark other ports until you mark the correct ones.