Veritas NetBackup™ SAN Client and Fibre Transport Guide
- Introducing SAN Client and Fibre Transport
 - Planning your deployment
- Planning your SAN Client deployment
 - SAN Client operational notes
 - About SAN Client storage destinations
 - How to choose SAN Client and Fibre Transport hosts
 - About NetBackup SAN Client support for agents
 - About NetBackup SAN Client support for clustering
 - About NetBackup SAN Client support for Windows Hyper-V Server
 - About NetBackup SAN Client unsupported restores
 - About Fibre Transport throughput
 - Converting a SAN media server to a SAN client
 
 - Preparing the SAN
- Preparing the SAN
 - About zoning the SAN for Fibre Transport
 - About zoning the SAN for Fibre Transport for a 16-gigabit target mode HBA support
 - About HBAs for SAN clients and Fibre Transport media servers
 - About the 16-gigabit target mode HBAs for SAN clients and Fibre Transport media servers
 - When selecting the HBA ports for SAN Client
 - About supported SAN configurations for SAN Client
 
 - Licensing SAN Client and Fibre Transport
 - Configuring SAN Client and Fibre Transport
- Configuring SAN Client and Fibre Transport
 - Configuring a Fibre Transport media server
- About the target mode driver
 - About nbhba mode and the ql2300_stub driver
 - About FC attached devices
 - How to identify the HBA ports
 - About HBA port detection on Solaris
 - About Fibre Transport media servers and VLANs
 - Starting nbhba mode
 - Marking the Fibre Transport media server HBA ports
 - Configuring the media server Fibre Transport services
 - Configuring the media server Fibre Transport services for a 16-gigabit target mode HBA support
 - Displaying the FTMS state for a 16-gigabit target mode HBA support
 - Identifying the HBA ports for a 16-gigabit target mode HBA support
 
 - Configuring SAN clients
 - Configuring SAN clients in a cluster
 - About configuring Fibre Transport properties
 - Configuring Fibre Transport properties
 - Fibre Transport properties
 - About SAN client usage preferences
 - Configuring SAN client usage preferences
 
 - Managing SAN clients and Fibre Transport
- Enabling or disabling the Fibre Transport services
 - Enabling or disabling the Fibre Transport services for a 16-gigabit target mode HBA support
 - Rescanning for Fibre Transport devices from a SAN client
 - Viewing SAN Client Fibre Transport job details
 - Viewing Fibre Transport traffic
 - Adding a SAN client
 - Deleting a SAN client
 
 - Disabling SAN Client and Fibre Transport
 - Troubleshooting SAN Client and Fibre Transport
- About troubleshooting SAN Client and Fibre Transport
 - SAN Client troubleshooting tech note
 - Viewing Fibre Transport logs
 - About unified logging
 - Stopping and starting Fibre Transport services
 - Stopping and starting Fibre Transport services for a 16-gigabit target mode HBA support
 - Backups failover to LAN even though Fibre Transport devices available
 - Kernel warning messages when Veritas modules load
 - SAN client service does not start
 - SAN client Fibre Transport service validation
 - SAN client does not select Fibre Transport
 - Media server Fibre Transport device is offline
 - No Fibre Transport devices discovered
 
 - Appendix A. AIX Specific Configuration Details
 - Appendix B. HP-UX Specific Configuration Details
- HP-UX Reference Information
 - Before you begin configuring NetBackup on HP-UX
 - About HP-UX device drivers for legacy device files
 - About legacy robotic control device files
 - About legacy tape drive device files
 - About legacy pass-through paths for tape drives
 - Creating device files for SAN Clients on HP-UX
 - About configuring legacy device files
 
 - Index
 
About legacy pass-through paths for tape drives
Although NetBackup requires the /dev/rmt device files to configure tape drives, NetBackup uses pass-through device files for drive access.
On media servers, NetBackup automatically creates pass-through device files if the appropriate/dev/rmt tape drive device files exist. NetBackup creates the pass-through device files in the /dev/sctl directory.
NetBackup does not modify or delete any existing pass-through paths.
NetBackup does not detect the type of adapter cards that are installed in the system. Therefore, NetBackup creates pass-through paths for tape drives connected to the adapter cards that do not support pass through. These pass-through paths do not cause problems.
Although NetBackup uses the pass-through device files during tape drive operations, you specify the /dev/rmt device files when you configure the drives in NetBackup. NetBackup then uses the appropriate pass-through device files. 
Usually, you do not have to create pass-through paths for drives. However, instructions to do so are provided for reference.
NetBackup SAN clients require legacy pass-through device files.
Note:
Pass-through paths are not supported on HP-PB adapters such asHP28696A - Wide SCSI or HP 28655A - SE SCSI.