Please enter search query.
Search <book_title>...
Veritas NetBackup™ SAN Client and Fibre Transport Guide
Last Published:
2018-02-16
Product(s):
NetBackup (8.1.1, 8.1)
- 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 does not select Fibre Transport
If either of the following are true, a SAN client may not be able to select Fibre Transport during a backup or restore operation:
The FT media server host operating system domainname command returns fully qualified domain names and NetBackup is configured to use short names.
The FT media server host operating system domainname command fails because of: DNS, NIS, or network problems and NetBackup is configured to use fully qualified domain names.
If so, the backup or restore may fail or it may occur over the LAN rather than the SAN.
To work around this problem, add an alias for the FT media server to the EMM database.
The following are the command syntaxes:
To add a short name alias:
nbemmcmd -machinealias -addalias -alias shortservername -machinename servername.fully.qualified -machinetype media
To add a fully qualified domain name alias:
nbemmcmd -machinealias -addalias -alias servername.fully.qualified -machinename shortservername -machinetype media