Veritas NetBackup™ SAN Client and Fibre Transport Guide

Last Published:
Product(s): NetBackup (8.3.0.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.  
      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 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
      10.  
        Configuring the media server Fibre Transport services for a 16-gigabit target mode HBA support
      11.  
        Displaying the FTMS state for a 16-gigabit target mode HBA support
      12.  
        Identifying 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.  
        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.  
      Enabling or disabling the Fibre Transport services for a 16-gigabit target mode HBA support
    3.  
      Rescanning for Fibre Transport devices from a SAN client
    4.  
      Viewing SAN Client Fibre Transport job details
    5.  
      Viewing Fibre Transport traffic
    6.  
      Adding a SAN client
    7.  
      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
    4.  
      Disabling 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.  
      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.  
      Stopping and starting 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 Veritas 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 offline
    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 configuring tape drive device files in AIX
      1.  
        About non-QIC tape drives on AIX
      2.  
        About no rewind device files on AIX
      3. Creating AIX no rewind device files for tape drives
        1.  
          Example of creating a no rewind device file
  10. Appendix B. HP-UX Specific Configuration Details
    1.  
      HP-UX Reference Information
    2.  
      Before you begin configuring NetBackup on HP-UX
    3.  
      About HP-UX device drivers for legacy device files
    4.  
      About legacy robotic control device files
    5.  
      About legacy tape drive device files
    6.  
      About legacy pass-through paths for tape drives
    7.  
      Creating device files for SAN Clients on HP-UX
    8. About configuring legacy device files
      1. Creating legacy SCSI and FCP robotic controls on HP-UX
        1.  
          Example of how to create a sctl device file for SCSI (PA-RISC)
        2.  
          Example of how to create a sctl device file for FCP (PA-RISC)
        3.  
          Example of how to create sctl device files for FCP (Itanium)
      2.  
        About creating legacy tape drive device files
      3.  
        Creating tape drive pass-through device files
  11.  
    Index

About non-QIC tape drives on AIX

Variable length block and fixed length block refer to how the operating system reads from and writes to a tape. Variable-mode devices allow more flexibility to read previously written tapes. Many tape devices can be accessed in either mode. NetBackup assumes variable length for non-quarter inch cartridge (QIC) drives.

For more information, see the chdev(1) and smit(1) man pages and the system management guide. The smit application is the most convenient way to change from fixed to variable-length-block devices manually.

Warning:

For NetBackup, you must configure non-QIC tape drives as variable-length-block devices. Otherwise NetBackup can write data but may not be able to read it correctly. During a read, you may see a not in tar format error.

When you add a non-QIC tape drive to NetBackup, NetBackup issues the chdev command to configure the drive as a variable length block device. For reference, the following is the command that NetBackup uses to configure a drive for variable mode:

/usr/sbin/chdev  -l Dev -a block_size=0

Dev represents the logical identifier for the drive (for example: rmt0 or rmt1).

Therefore, you do not have to configure the drive manually for variable mode.