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 Fibre Transport media servers and VLANs
For an FT media server that has multiple network interfaces for VLANs, NetBackup must recognize the primary network interface of the host before any other network interfaces for the host. Each NetBackup host recognizes other NetBackup hosts by using its list. The list appears in the NetBackup Administration Console host properties Servers page for that host.
Ensure that the FT server's primary host name appears before any other interface names for that FT media server host. Do so in the Additional Servers lists of the following NetBackup hosts:
The master server.
The FT media server.
All of the SAN clients that the FT media server backs up.
You may be able to use operating system commands to determine the primary interface. UNIX-type operating systems have a hostname command, which displays the short name of the primary interface. They also have a domainname command, which shows the domain name of the primary interface. On Windows, you can use the ipconfig -all command to display host and domain information.
See Backups failover to LAN even though Fibre Transport devices available .