Veritas NetBackup™ SAN Client and Fibre Transport Guide
- Introducing SAN Client and Fibre Transport
- Planning your deployment
- About SAN Client storage destinations
- Preparing the SAN
- Licensing SAN Client and Fibre Transport
- Configuring SAN Client and Fibre Transport
- Configuring a Fibre Transport media server
- Configuring SAN clients
- Configuring SAN clients in a cluster
- Fibre Transport properties
- Configuring SAN client usage preferences
- Managing SAN clients and Fibre Transport
- Disabling SAN Client and Fibre Transport
- Troubleshooting SAN Client and Fibre Transport
- About unified logging
About nbhba mode and the ql2300_stub driver
The first step of the process to configure the media server HBA drivers is to start nbhba mode. The nbhba mode binds the Veritas provided
ql2300_stub driver to all QLogic ISP2312 and ISP24xx HBA ports on the host.
ql2300_stub driver prevents the standard initiator mode driver from binding to the ports. If the QLogic driver binds to the HBA ports, the NetBackup nbhba command cannot mark the ports that you want to operate in target mode. The target mode driver also cannot bind to the HBA ports.
ql2300_stub driver also lets NetBackup read and modify the device ID in NVRAM of the QLogic ports. After you start nbhba mode and mark the ports of the QLogic HBAs that connect to the SAN clients, those ports operate in target mode.
The computer exits nbhba mode when the FT server starts.
For Linux operating systems, warning messages may be displayed in the console or the system log when the
ql2300_stub driver is loaded into the kernel.