Veritas NetBackup™ SAN Client and Fibre Transport Guide

Last Published:
Product(s): NetBackup (8.1.1, 8.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.  
      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 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.  
      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

Configuring the media server Fibre Transport services

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). Two services (nbftsrvr and nbfdrv64) comprise 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 HBA ports that you marked. (The default QLogic driver is bound already to the ports that are not marked.) The HBA ports operate in target mode until you configure them to use the standard initiator mode again.

  • Ends the nbhba mode on the computer (if it was in nbhba mode)

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

You must be the root user.

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
    Installing the Jungo driver and Fibre Transport Server.
    The following automatic startup and shutdown scripts 
    (respectively) have been installed.  They will cause the 
    NetBackup Fibre Transport Server daemon to be automatically shut 
    down and restarted each time the system boots.
    /etc/rc.d/rc2.d/S21nbftserver
    /etc/rc.d/rc3.d/S21nbftserver
    /etc/rc.d/rc5.d/S21nbftserver
    /etc/rc.d/rc0.d/K03nbftserver
    /etc/rc.d/rc1.d/K03nbftserver
    /etc/rc.d/rc6.d/K03nbftserver
    It may be necessary to temporarily unload your QLogic drivers
    to free up the ports for the nbhba drivers.
    This is an optional step.  If you choose not to do this, you may 
    not have access to all of the HBA ports until a subsequent 
    reboot.
    Would you like to uninstall and reinstall your native QLogic 
    drivers now? [y,n] (y) y
  2. The Qlogic drivers must be unloaded temporarily so that the stub driver (ql2300_stub) can bind to the marked HBA ports during this session.

    If you answer y, you do not have to reboot the computer during this configuration process. However, any critical devices that are attached to QLogic HBAs in the computer may be unavailable during this session. To ensure that the critical devices remain available, answer n. Then, you must reboot when prompted. The stub driver binds to the marked ports during the boot process, and the default QLogic drivers bind to the unmarked ports.

    If you answer n, go to step 5.

    If you answer y, you are prompted again to unload each QLogic driver, as follows:

    Are you sure you want to unload QLogic driver: qla2300? [y,n] 
    (y) y
  3. To unload the QLogic driver, answer y. The process continues as follows:
    Removing qla2300
    Adding qla2300.
    Adding qla2xxx.
    Would you like to start the SANsurfer agent (qlremote)? [y,n] 
    (y) y
  4. If the QLogic SANsurfer agent was loaded, the configuration process asks if you want to start the agent. To start the QLogic SANsurfer agent, answer y. The process continues as follows:
    Starting qlremote agent service
    Started SANsurfer agent.
    /etc/udev/permissions.d/50-udev.permissions updated with Jungo 
    WinDriver permissions.
    NetBackup Fibre Transport Server started.
    Would you like to make these changes persist after a reboot? 
    [y,n] (y) y
  5. To ensure that the FT server always starts after a computer reboot, answer y. The process continues as follows:
    Running mkinitrd.  Previous initrd image is saved at 
    /boot/initrd-2.6.9-11.ELsmp.img.05-21-07.11:24:03.

    If you answered y in step 2, the FT services are started, and the target mode driver binds to the marked HBA ports.

  6. If you answered n in step 2, reboot the computer when prompted.

    The FT services are started, and the target mode driver binds to the marked HBA ports.

To configure Fibre Transport services on Solaris

  1. Run the nbftsrv_config script. The following is an example; output on your system may differ:
    /usr/openv/netbackup/bin/admincmd/nbftsrv_config
    Installing the Jungo driver and Fibre Transport Server.
    Waiting for driver references to ql2300_stub to free up (this 
    may take some time).
    The following automatic startup and shutdown scripts 
    (respectively) have been installed.  They will cause the 
    NetBackup Fibre Transport Server daemon to be automatically shut 
    down and restarted each time the system boots.
    /etc/rc2.d/S21nbftserver
    /etc/rc0.d/K03nbftserver
    Adding "pci1077,2312.1077.101" to qlc.
    No third party drivers found with conflicting driver aliases.
    Done copying driver into system directories.
    Done adding driver.MUST REBOOT TO COMPLETE INSTALLATION.
  2. Reboot the host.

    The FT services are started, and the target mode driver binds to the marked HBA ports.