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
Configuring the media server Fibre Transport services
You must configure the media server FT services before you configure the SAN clients. The FT server must run on the media servers so that the client operating system discovers the target mode driver (the FT device). Two services (nbftsrvr and nbfdrv64) comprise the NetBackup FT server that runs on media servers.
The nbftsrv_config script configures the media server for Fibre Transport. In this process, the script does the following:
Installs the required drivers
Installs the FT server start-up scripts
Starts the FT server
When the FT server starts, the NetBackup target mode driver binds automatically to the QLogic HBA ports that you marked. (The default QLogic driver is bound already to the ports that are not marked.) The HBA ports operate in target mode until you configure them to use the standard initiator mode again.
Ends the nbhba mode on the computer (if it was in nbhba mode)
Configure the FT services on every NetBackup media server that connects to SAN clients.
For procedures, see the following:
You must be the root user.
To configure Fibre Transport services on Linux
- Run the nbftsrv_config script. The following is an example; output on your system may differ:
/usr/openv/netbackup/bin/admincmd/nbftsrv_config Installing the Jungo driver and Fibre Transport Server. The following automatic startup and shutdown scripts (respectively) have been installed. They will cause the NetBackup Fibre Transport Server daemon to be automatically shut down and restarted each time the system boots. /etc/rc.d/rc2.d/S21nbftserver /etc/rc.d/rc3.d/S21nbftserver /etc/rc.d/rc5.d/S21nbftserver /etc/rc.d/rc0.d/K03nbftserver /etc/rc.d/rc1.d/K03nbftserver /etc/rc.d/rc6.d/K03nbftserver It may be necessary to temporarily unload your QLogic drivers to free up the ports for the nbhba drivers. This is an optional step. If you choose not to do this, you may not have access to all of the HBA ports until a subsequent reboot. Would you like to uninstall and reinstall your native QLogic drivers now? [y,n] (y) y
- The Qlogic drivers must be unloaded temporarily so that the stub driver (ql2300_stub) can bind to the marked HBA ports during this session.
If you answer y, you do not have to reboot the computer during this configuration process. However, any critical devices that are attached to QLogic HBAs in the computer may be unavailable during this session. To ensure that the critical devices remain available, answer n. Then, you must reboot when prompted. The stub driver binds to the marked ports during the boot process, and the default QLogic drivers bind to the unmarked ports.
If you answer n, go to step 5.
If you answer y, you are prompted again to unload each QLogic driver, as follows:
Are you sure you want to unload QLogic driver: qla2300? [y,n] (y) y
- To unload the QLogic driver, answer y. The process continues as follows:
Removing qla2300 Adding qla2300. Adding qla2xxx. Would you like to start the SANsurfer agent (qlremote)? [y,n] (y) y
- If the QLogic SANsurfer agent was loaded, the configuration process asks if you want to start the agent. To start the QLogic SANsurfer agent, answer y. The process continues as follows:
Starting qlremote agent service Started SANsurfer agent. /etc/udev/permissions.d/50-udev.permissions updated with Jungo WinDriver permissions. NetBackup Fibre Transport Server started. Would you like to make these changes persist after a reboot? [y,n] (y) y
- To ensure that the FT server always starts after a computer reboot, answer y. The process continues as follows:
Running mkinitrd. Previous initrd image is saved at /boot/initrd-2.6.9-11.ELsmp.img.05-21-07.11:24:03.
If you answered y in step 2, the FT services are started, and the target mode driver binds to the marked HBA ports.
- If you answered n in step 2, reboot the computer when prompted.
The FT services are started, and the target mode driver binds to the marked HBA ports.
To configure Fibre Transport services on Solaris
- Run the nbftsrv_config script. The following is an example; output on your system may differ:
/usr/openv/netbackup/bin/admincmd/nbftsrv_config Installing the Jungo driver and Fibre Transport Server. Waiting for driver references to ql2300_stub to free up (this may take some time). The following automatic startup and shutdown scripts (respectively) have been installed. They will cause the NetBackup Fibre Transport Server daemon to be automatically shut down and restarted each time the system boots. /etc/rc2.d/S21nbftserver /etc/rc0.d/K03nbftserver Adding "pci1077,2312.1077.101" to qlc. No third party drivers found with conflicting driver aliases. Done copying driver into system directories. Done adding driver.MUST REBOOT TO COMPLETE INSTALLATION.
- Reboot the host.
The FT services are started, and the target mode driver binds to the marked HBA ports.