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 Fibre Transport service validation
The SAN Client Fibre Transport Service (nbftclnt) validates the client system's kernel and driver stack when it starts and during device discovery. Validation verifies that the kernel and the drivers are at supported levels.
If validation succeeds, the SAN client supports FT pipe transfers; FT pipe transfer can occur. If validation fails, FT pipe transfer cannot occur.
To manage the validation failure, the following occurs:
The SAN Client Fibre Transport Service writes check driver messages in its log file.
NetBackup sets the FT device status to offline for all FT target devices in the client's SAN zone. (For other clients in the zone that pass the validation, the FT devices are online.)
To see the FT device status from the client, select the client in the Media and Device Management > Devices > SAN Clients window in the NetBackup Administration Console.
The check driver messages in the nbftclnt log file are similar to the following:
VerifyCheckConditions:failed on <OS Device Name> - check driver VerifyCheckConditions:failed on <OS Device Name>; <System Error Message>
The following describes the variables in the messages:
OS Device Name is the device name the SAN Client uses to open the OS device driver.
System Error Message can be any OS-dependent system error message for a failure that is associated with the request.
If validation fails, install the correct operating system version, operating system patches, or driver version.
For supported kernel and driver levels, see the NetBackup Release Notes.
More Information