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

Disabling a Fibre Transport media server

You can disable an FT media server and remove the operating system FT startup scripts from the media server. The process also removes the nbhba driver and exits nbhba mode. The media server then does not support NetBackup Fibre Transport.

See About disabling SAN Client and Fibre Transport.

Warning:

On Solaris systems, /etc/driver_aliases file entries may remain after you remove the FT services and the nbhba driver. The entries are in the form of qla2300 "pci1077,xxx" or qla2300 "pciex1077,xxx. The entries are harmless; however, if you attempt to remove them, the system may not boot. Sun Microsystems recommends that you do not edit the /etc/driver_aliases file.

To disable an FT media server and remove drivers

  1. On the FT media server, run the following script:

    /usr/openv/netbackup/bin/admincmd/nbftsrv_config -d

  2. Verify that the following startup scripts were removed:

    On Linux systems, the following are the scripts:

    /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/rc6.d/K03nbftserver
/lib/modules/ 2.6.*smp/kernel/drivers/misc/ql2300_stub.ko
/lib/modules/ 2.6.*smp/kernel/drivers/misc/windrvr6.ko

    On Solaris systems, the following are the scripts:

    /etc/rc2.d/S21nbftserver
/etc/rc0.d/K03nbftserver
/usr/kernel/drv/windrvr6.conf
/usr/kernel/drv/sparcv9/windrvr6
/usr/kernel/drv/sparcv9/ql2300_stub
  3. If the startup scripts were not removed, delete them manually.
  4. Run the following script:

    /usr/openv/netbackup/bin/admincmd/nbftconfig -ds ft_server_host_name