Important Update: Cohesity Products Documentation


All Cohesity product documentation are now managed via the Cohesity Docs Portal: https://docs.cohesity.com/HomePage/Content/home.htm. Some documentation available here may not reflect the latest information or may no longer be accessible.

NetBackup™ SAN Client and Fibre Transport Guide

Last Published:
Product(s): NetBackup (11.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.  
      Supported systems and periphials
  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
    3.  
      When upgrading SAN Client and Fibre Transport
  5. Configuring SAN Client and Fibre Transport
    1.  
      Overview of 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.  
        Start nbhba mode
      8.  
        Mark the Fibre Transport media server HBA ports
      9.  
        Configure the media server Fibre Transport services
      10.  
        Configure the media server Fibre Transport services for a 16-gigabit target mode HBA support
      11.  
        Display the FTMS state for a 16-gigabit target mode HBA support
      12.  
        Identify 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.  
        Configure the SAN Client Fibre Transport service
    4. Configuring SAN clients in a cluster
      1.  
        Register a SAN client cluster virtual name
      2.  
        Setting NetBackup configuration options by using the command line
    5.  
      About configuring Fibre Transport properties
    6.  
      Configure Fibre Transport properties
    7. Fibre Transport properties
      1.  
        About Linux concurrent FT connections
    8.  
      Configure SAN client usage preferences
    9.  
      SAN client usage preferences
  6. Managing SAN clients and Fibre Transport
    1.  
      Enable or disable the Fibre Transport services
    2.  
      Enable or disable the Fibre Transport services for a 16-gigabit target mode HBA support
    3.  
      Rescan for Fibre Transport devices from a SAN client
    4.  
      View the SAN client Fibre Transport job details
    5.  
      View the Fibre Transport traffic
    6.  
      Delete a SAN client
  7. Disabling SAN Client and Fibre Transport
    1.  
      Disable a SAN client
    2.  
      Disable a Fibre Transport media server
    3.  
      Disable 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.  
      View the 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.  
      Stop and start the Fibre Transport services
    6.  
      Stop and start the 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 Cohesity 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 not active
    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 non-QIC tape drives on AIX
    7.  
      About no rewind device files on AIX
    8.  
      Create AIX no rewind device files for tape drives
    9.  
      Disable the AIX dynamic tracking

Configure the SAN Client Fibre Transport service

You must enable the SAN Client Fibre Transport Service on the NetBackup clients that you want to function as SAN clients. During this process, the SAN client operating system discovers the FT devices on the FT media servers.

Warning:

NetBackup SAN clients cannot also be NetBackup servers. Therefore, only configure a client to be a SAN client on systems on which the NetBackup client software only is installed.

To configure a NetBackup client to be a SAN client

  1. Verify that the PBX service is active on the client, as follows:
    • On UNIX and Linux systems, run theNetBackup bpps -x command and verify that the pbx_exchange process is active.

    • On Windows systems, use the Computer Management console to verify that the Private Branch Exchange service is active.

  2. On the client, run the following command to enable the SAN Client Fibre Transport Service (nbftclnt):

    UNIX and Linux:

    /usr/openv/netbackup/bin/bpclntcmd -sanclient 1

    Windows:

    install_path\NetBackup\bin\bpclntcmd.exe -sanclient 1

  3. Do the following to start the SAN client FT service:

    • Linux: Start the system, which also begins operating system device discovery. (Alternatively, you can run the NetBackup bp.start_all command to start the client FT service.)

    • AIX and Solaris: Run the NetBackup bp.start_all command. The command resides in the following directory:

      /usr/openv/netbackup/bin

    • Windows: Start the system, which also begins operating system device discovery.

  4. On the systems that were not started in step 3, perform the action that forces the SAN client operating system to discover devices.

    The operating system must discover two FT devices for each media server HBA port that is in target mode.

    The SAN Client Fibre Transport Service (nbftclnt) validates the driver stack functionality during device discovery. If validation fails, Fibre Transport is not enabled on the client.

    After the client OS discovers the FT devices, the SAN client is registered with NetBackup.

  5. If the client system does not discover the FT devices, verify the following:

    • The Fibre Channel driver is installed on the SAN client.

    • The SAN client HBA port is active on the Fibre Channel switch.

    • The media server HBA port is active on the Fibre Channel switch.

    • The SAN client is logged into the Fibre Channel switch name server.

    • The FT media server is logged into the Fibre Channel switch name server.

    • The FT media server port is zoned with the SAN client port.

    • The zone is included in the active configuration.

    Alternatively, you can try a scan operation for FT devices on a client system.