Veritas NetBackup™ SAN Client and Fibre Transport Guide
- Introducing SAN Client and Fibre Transport
- Planning your deployment
- Planning your SAN Client deployment
- About SAN Client best practices
- 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
- 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 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
- 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
- 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
SAN client driver requirements
The operating systems of the NetBackup SAN clients may require device drivers that allow SCSI pass-through methods for the Fibre Transport traffic.
If the SAN client operating system is configured correctly, it recognizes each media server HBA port in target mode as two ARCHIVE Python devices.
Table: SAN client operating system driver requirements lists the driver requirements for each supported SAN client operating system.
Table: SAN client operating system driver requirements
Operating system | Driver requirements |
|---|---|
AIX | Client systems require the standard tape driver. The driver should work without modification. For information about how to configure the driver, see the NetBackup Device Configuration Guide, available at the following URL: |
HP-UX | Client systems require the sctl driver and pass-through device files. For information about how to configure the driver, see the NetBackup Device Configuration Guide, available at the following URL: |
Linux | Client systems require the SCSI Generic (sg) driver and pass-through device files. For information about how to configure the driver, see the NetBackup Device Configuration Guide, available at the following URL: |
Solaris | You must modify the /kernel/drv/st.conf file so that Solaris recognizes the FT devices on the NetBackup media servers. For information about how to do so, see the NetBackup Device Configuration Guide, available at the following URL: |
Windows | A device driver is not required. The media server FT devices appear in the Windows Device Manager "Other devices" section as ARCHIVE Python SCSI Sequential Devices. |
Some operating systems require specific patch and driver updates. For information about them, see the NetBackup Release Notes: