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
- AIX Reference Information
- Before you begin configuring NetBackup on AIX
- About AIX persistent naming support
- About configuring robotic control device files in AIX
- About device files for SAN Clients on AIX
- About non-QIC tape drives on AIX
- About no rewind device files on AIX
- Creating AIX no rewind device files for tape drives
- 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
Fibre transport properties
NetBackup Fibre Transport properties control how your Fibre Transport media servers and SAN clients use the Fibre Transport service for backups and restores. The Fibre transport properties apply to the host type that you select, as follows:
Table: Host types for Fibre transport properties
Host type | Description |
|---|---|
Primary server | Global Fibre transport properties that apply to all SAN clients. |
Media server | The Fibre transport Maximum concurrent FT connections property applies to the FT media server that you select. |
Client | The Fibre transport properties apply to the SAN client that you select. The default values for clients are the global property settings of the primary server. Client properties override the global Fibre transport properties. |
The properties contain the following settings. All properties are not available for all hosts. In this table, FT device is an HBA port on a Fibre Transport media server. The port carries the backup and restore traffic. A media server may have more than one FT device.
Table: Fibre transport properties
Property | Description |
|---|---|
Maximum concurrent FT connections | This property appears only when you select an FT media server . This property specifies the number of FT connections to allow to the selected media server or media servers. A connection is equivalent to a job. If no value is set, NetBackup uses the following defaults:
You can enter up to the following maximum connections for the media server or servers to use:
NetBackup supports 644 buffers per media server for Fibre Transport. To determine the number of buffers that each connection uses, divide 644 by the value you enter. More buffers per connection equal better performance for each connection. |
Use defaults from the primary server configuration | This property appears only when you select a client . This property specifies that the client follow the properties as they are configured on the primary server. |
Preferred | The Preferred property specifies to use an FT device if one is available within the configured wait period in minutes. If an FT device is not available after the wait period elapses, NetBackup uses a LAN connection for the operation. If you select this option, also specify the wait period for backups and for restores. For the global property that is specified on the primary server, the default is . |
Always | The Always property specifies that NetBackup should always use an FT device for backups and restores of SAN clients. NetBackup waits until an FT device is available before it begins the operation. However, an FT device must be online and up. If not, NetBackup uses the LAN. An FT device may be unavailable because none are active, none have been configured, or the SAN Client license expired. |
Fail | The Fail property specifies that NetBackup should fail the job if an FT device is not online and up. If the FT devices are online but busy, NetBackup waits until a device is available and assigns the next job to the device. An FT device may be unavailable because none are active, none have been configured, or the SAN Client license expired. |
Never | The Never property specifies that NetBackup should never use an FT pipe for backups and restores of SAN clients. NetBackup uses a LAN connection for the backups and restores. If you specify for the primary server, Fibre Transport is disabled in the NetBackup environment. If you select , you can configure FT usage on a per-client basis. If you specify for a media server, Fibre Transport is disabled for the media server. If you specify for a SAN client, Fibre Transport is disabled for the client. |
See Configuring Fibre Transport properties.
NetBackup provides one finer level of granularity for Fibre transport. SAN client usage preferences override the FT properties that you configure through Host properties.