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

Examples of using vxlogview to view unified logs

The following examples demonstrate how to use the vxlogview command to view unified logs.

Note:

Only the following types of users can access the logs: root and service users in Linux systems, and users present in the administrators group of Windows systems.

Table: Example uses of the vxlogview command

Item

Example

Display all the attributes of the log messages

vxlogview -p 51216 -d all

Display specific attributes of the log messages

Display the log messages for NetBackup (51216) that show only the date, time, message type, and message text:

vxlogview --prodid 51216 --display D,T,m,x

Display the latest log messages

Display the log messages for originator 116 (nbpem) that were issued during the last 20 minutes. Note that you can specify -o nbpem instead of -o 116:

# vxlogview -o 116 -t 00:20:00

Display the log messages from a specific time period

Display the log messages for nbpem that were issued during the specified time period:

# vxlogview -o nbpem -b "05/03/15 06:51:48 AM" 
    -e "05/03/15 06:52:48 AM"

Display results faster

You can use the -i option to specify an originator for a process:

# vxlogview -i nbpem

The vxlogview -i option searches only the log files that the specified process (nbpem) creates. By limiting the log files that it has to search, vxlogview returns a result faster. By comparison, the vxlogview -o option searches all unified log files for the messages that the specified process has logged.

Note:

If you use the -i option with a process that is not a service, vxlogview returns the message "No log files found." A process that is not a service has no originator ID in the file name. In this case, use the -o option instead of the -i option.

The -i option displays entries for all OIDs that are part of that process including libraries (137, 156, 309, etc.).

Search for a job ID

You can search the logs for a particular job ID:

# vxlogview -i nbpem | grep "jobid=job_ID"

The jobid= search key should contain no spaces and must be lowercase.

When searching for a job ID, you can use any vxlogview command option. This example uses the -i option with the name of the process (nbpem). The command returns only the log entries that contain the job ID. It misses related entries for the job that do not explicitly contain the jobid=job_ID.