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.
Warning: |
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 Symantec PBX service is active on the client, as follows:
On the client, run the following command to enable the SAN Client Fibre Transport Service (nbftclnt):
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.
If the client system does not discover the FT devices, verify the following:
Alternatively, you can try a scan operation for FT devices on a client system.
More Information