Verify that the Private Branch Exchange (PBX) service is installed and running. Run the bpps -x command to ensure that pbx_exchange is listed in the processes that are running.

Verify that the client is configured as a SAN Client. Run the bpclntcmd -sanclient command to return the current state of the SAN Client. A response of 0 (zero) indicates that SAN Client is not configured. Rerun the command as bpclntcmd -sanclient 1.

Verify that the client is not also a media server, master server, or EMM server. The SAN Client process runs only on a NetBackup client.

Verify that a valid license for the SAN Client feature resides on the master server. SAN Client is a separately licensed feature which requires a key called "SAN Client" on the master server.

Verify that no server entries for the SAN Client exist on the NetBackup master server. Remove any SERVER=clientname entry in the master server for the SAN Client. If the master server has the SAN Client listed also as a server, it may shut down the SAN Client.

Restart the SAN Client service. The SAN Client restarts when the server reboots, but does not automatically restart after you run the bpclntcmd command. To start the SAN Client service, run the client startup script or use the Service Manager in Windows.