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
Stopping and starting Fibre Transport services
Fibre Transport services run on both the FT media servers and SAN clients.
The following are the FT services that run on media servers:
The nbftsrvr service manages the server side of the FT pipe.
The nbfdrv64 service controls the target mode drivers on the media server.
The nbftsrvr service starts the nbfdrv64 service. If you stop one, the other stops. If one ends abnormally, the other stops.
The nbftclnt FT service runs on SAN clients:
These services do not appear in the NetBackup Activity Monitor; they do appear in the operating system process displays.
In normal operation, you should not have to start or stop the services. A Veritas support engineer may direct you to stop and restart services for troubleshooting purposes.
Alternatively, you can use the UNIX kill command without the -9 option to stop the services. The NetBackup bp.kill_all command stops the FT services, but it stops all other NetBackup services also.
Warning:
Do not use the UNIX kill -9 command and option to stop the nbfdrv64 process. It does not allow the process to stop gracefully, and the SAN clients cannot detect the FT devices when the nbfdrv64 process dies. You then may have to reboot the client systems so they detect the FT devices again (after you restart nbfdrv64).
The NetBackup bp.start_all command starts all NetBackup services, including the FT services.
More Information