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

Fibre Transport properties

To access this setting, in the web UI select Hosts > Host properties. Select the host. If necessary, click Connect. Then click Edit primary server, or Edit media server, or Edit client. Click Fibre Transport.

Note that any usage preferences that you configure for an individual SAN Client in Storage > SAN Clients override the Fibre Transport properties that you configure in Host properties.

See Configure SAN client usage preferences.

NetBackup Fibre Transport properties control how your Fibre Transport media servers and SAN clients use the Fibre Transport service for backups and restores. The Fibre Transport properties apply to the host type that you select, as follows:

Table: Host types for Fibre Transport properties

Host type

Description

Primary server

Global Fibre Transport properties that apply to all SAN clients.

Media server

The Fibre Transport Maximum concurrent Fibre Transport connections property applies to the Fibre Transport media server that you select.

Client

The Fibre Transport properties apply to the SAN client that you select. The default values for clients are the global property settings of the primary server. Client properties override the global Fibre Transport properties.

The Fibre Transport properties contain the following settings. All properties are not available for all hosts. In this table, the Fibre Transport device is an HBA port on a Fibre Transport media server. The port carries the backup and restore traffic. A media server may have more than one Fibre Transport device.

Table: Fibre Transport properties

Property

Description

Maximum concurrent Fibre Transport connections

This property displays only when you select a Fibre Transport media server .

This property specifies the number of Fibre Transport connections to allow to the selected media server or media servers. A connection is equivalent to a job.

If no value is set, NetBackup uses the following defaults:

  • For NetBackup Appliance model 5330 and later: 32

  • For NetBackup Appliance model 5230 and later: 32

  • For NetBackup Fibre Transport media servers: 8 times the number of fast HBA ports on the media server plus 4 times the number of slow HBA ports. A fast port is 8 GB or faster, and a slow port is less than 8 GB.

You can enter up to the following maximum connections for the media server or servers to use:

  • On a Linux Fibre Transport media server host: 40.

    The recommended setting is 32 or fewer connections concurrently on Linux.

    On Linux hosts, you can increase that maximum by setting a NetBackup touch file, NUMBER_DATA_BUFFERS_FT.

    See About Linux concurrent FT connections.

  • For NetBackup Appliance model 5330 and later: 40.

  • For NetBackup Appliance model 5230 and later: 40.

  • On a Solaris Fibre Transport media server host: 64.

NetBackup supports 644 buffers per media server for Fibre Transport. To determine the number of buffers that each connection uses, divide 644 by the value you enter. If you have buffers per connection you see better performance for each connection.

Use defaults from the primary server configuration

This property displays only when you select a client .

This property specifies that the client follow the properties as they are configured on the primary server.

Preferred

The Preferred property specifies to use an FT device if one is available within the configured wait period in minutes. If an FT device is not available after the wait period elapses, NetBackup uses a LAN connection for the operation.

For the global property that is specified on the primary server, the default is Preferred.

Always

The Always property specifies that NetBackup should always use an FT device for backups and restores of SAN clients. NetBackup waits until an FT device is available before it begins the operation.

However, an FT device must be active and up. If not, NetBackup uses the LAN. An FT device may not exist because none is active, none have been configured, or the SAN Client license expired.

Fail

The Fail property specifies that NetBackup should fail the job if an FT device is not active and up. If the FT devices are active but busy, NetBackup waits until a device is available and assigns the next job to the device. An FT device may not exist because none are active, none have been configured, or the SAN Client license expired.

Never

The Never property specifies that NetBackup should never use a Fibre Transport pipe for backups and restores of SAN clients. NetBackup uses a LAN connection for the backups and restores.

If you specify Never for the primary server, Fibre Transport is disabled in the NetBackup environment. If you select Never, you can configure Fibre Transport usage on a per-client basis.

If you specify Never for a SAN client, Fibre Transport is disabled for the client.