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
About Linux concurrent FT connections
NetBackup uses the Maximum concurrent FT connections Fibre Transport host property to configure the number of concurrent connections to a Fibre Transport media server, up to the total that is allowed per host.
See Fibre Transport properties.
/usr/openv/netbackup/db/config/NUMBER_DATA_BUFFERS_FT
Table: Supported values for buffers per FT connection shows the values that NetBackup supports for the NUMBER_DATA_BUFFERS_FT file. NetBackup supports 644 buffers per media server for Fibre Transport.
Table: Supported values for buffers per FT connection
| Total concurrent connections: NetBackup 5230 and 5330 and later appliances | Total concurrent connections: Linux FT media server |
|---|---|---|
16 | 40 | 40 |
12 | 53 | 53 |
10 | 64 | 64 |
If you want, you then can limit the number of connections for a media server or media servers by using the of the Fibre Transport host properties.