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 SAN client Fibre Transport service
You must enable the SAN Client Fibre Transport Service on the NetBackup clients that you want to function as SAN clients. During this process, the SAN client operating system discovers the FT devices on the FT media servers.
NetBackup SAN clients cannot also be NetBackup servers. Therefore, only configure a client to be a SAN client on systems on which the NetBackup client software only is installed.
To configure a NetBackup client to be a SAN client
- Verify that the Veritas PBX service is active on the client, as follows:
On UNIX and Linux systems, run theNetBackup bpps -x command and verify that the pbx_exchange process is active.
On Windows systems, use the Computer Management console to verify that the Veritas Private Branch Exchange service is active.
- On the client, run the following command to enable the SAN Client Fibre Transport Service (nbftclnt):
UNIX and Linux:
/usr/openv/netbackup/bin/bpclntcmd -sanclient 1
install_path\NetBackup\bin\bpclntcmd.exe -sanclient 1
Do the following to start the SAN client FT service:
Linux: Boot the system, which also begins operating system device discovery. (Alternatively, you can run the NetBackup bp.start_all command to start the client FT service.)
AIX, HP-UX, and Solaris: Run the NetBackup bp.start_all command. The command resides in the following directory:
Windows: Boot the system, which also begins operating system device discovery.
- On the systems that were not booted in step 3, perform the action that forces the SAN client operating system to discover devices.
The operating system must discover two FT devices for each media server HBA port that is in target mode.
The SAN Client Fibre Transport Service (nbftclnt) validates the driver stack functionality during device discovery. If validation fails, Fibre Transport is not enabled on the client.
After the client OS discovers the FT devices, the SAN client is registered with NetBackup. You should not have to add the SAN client either manually or by using the Device Configuration Wizard.
- Alternatively, you can try a scan operation for FT devices on a client system.
If the client system does not discover the FT devices, verify the following:
The Fibre Channel driver is installed on the SAN client.
The SAN client HBA port is active on the Fibre Channel switch.
The media server HBA port is active on the Fibre Channel switch.
The SAN client is logged into the Fibre Channel switch name server.
The FT media server is logged into the Fibre Channel switch name server.
The FT media server port is zoned with the SAN client port.
The zone is included in the active configuration.