Veritas 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
- 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
- Appendix A. AIX Specific Configuration Details
- 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
Backups failover to LAN even though Fibre Transport devices available
If a NetBackup FT media server has multiple network interfaces for VLANs, backups may failover to LAN transport if the NetBackup host name order is configured incorrectly.
See About Fibre Transport media servers and VLANs.
For all of the hosts that participate in the backups, examine their Additional Servers lists on their NetBackup Administration Console host properties Servers pages. Verify that the FT server's primary host name appears before any other interface names for that FT media server host in. If it does not, fix the incorrect host name order as described in the following table.
Table: How to fix an incorrect host name order in NetBackup
Task | Procedure |
|---|---|
Stop the FT services on the media server | |
Delete the FT server from the NetBackup EMM database | Use the following NetBackup command to delete the host from the NetBackup EMM database as an FT media server: nbftconfig -deleteserver -Me hostname The host remains in the EMM database as a NetBackup media server. |
Re-order the list on each host | If necessary, delete all of the network interface names of the FT media server from the list. Then, add the primary host name first and then the remainder of the host names in any order. The list appears in the host properties Servers page for that host. See the NetBackup Administrator's Guide, Volume I: |
Start the FT services on the media server | |
Scan for FT devices from each SAN client | When the FT media server is discovered during the rescan operation, NetBackup adds it to the EMM database as an FT media server. See Rescanning for Fibre Transport devices from a SAN client. |