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
Configuring SAN clients in a cluster
The SAN Client FT service is not a cluster application. To protect the SAN clients that are in a cluster, you must configure all of the SAN clients in the cluster correctly.
See Setting NetBackup configuration options by using the command line.
Table: Process to configure a SAN client in a cluster
Step | Action | Description |
|---|---|---|
Step 1 | Install the NetBackup client software on each failover node | See the NetBackup Installation Guide for UNIX and Windows: |
Step 2 | Configure the SAN client on each failover node | Ensure that the FT service is active on all of the failover nodes. See About configuring firewalls for SAN clients. |
Step 3 | Register the virtual node name with the EMM server | |
Step 4 | Configure the NetBackup local cache | On each SAN Client in the cluster, set the NetBackup LOCAL_CACHE option to NO. See About NetBackup SAN Client support for clustering. See Setting NetBackup configuration options by using the command line. Warning: Do not change the LOCAL_CACHE value on the FT media servers or the master server. |