Problem
STATUS CODE 239: NetBackup for Microsoft SQL Server backups fail with Status Code 239 when attempting to back up a SQL ClusterError Message
STATUS CODE 239: the specified client does not exist in the specified policySolution
Overview
NetBackup for Microsoft SQL Serverbackups fail with Status Code 239 when attempting to back up a SQLCluster. The exit status 239 is caused because the name being passed fromthe cluster does not reflect the name in the SQLpolicy.
Troubleshooting
Log Files: N/A
A review of the batch file ( .bch) being used to attempt thebackup of the SQL cluster shows something similar to thefollowing:
Where "VirtualNode" is the name of the virtual SQLserver, and "NodeA" is the active node of the SQL cluster.
Resolution
Modify the batch file so the " BROWSECLIENT"keyword reflects the virtual name of the SQL server, as shown in the followingsnippet:
Once these changes are made, perform the backupoperation again.
NetBackup for Microsoft SQL Serverbackups fail with Status Code 239 when attempting to back up a SQLCluster. The exit status 239 is caused because the name being passed fromthe cluster does not reflect the name in the SQLpolicy.
Troubleshooting
Log Files: N/A
A review of the batch file ( .bch) being used to attempt thebackup of the SQL cluster shows something similar to thefollowing:
OPERATIONBACKUP
DATABASE"$ALL"
SQLHOST"VirtualNode"
NBSERVER"MasterServer"
BROWSECLIENT"NodeA"
MAXTRANSFERSIZE0
BLOCKSIZE0
ENDOPERTRUE
Where "VirtualNode" is the name of the virtual SQLserver, and "NodeA" is the active node of the SQL cluster.
Resolution
Modify the batch file so the " BROWSECLIENT"keyword reflects the virtual name of the SQL server, as shown in the followingsnippet:
OPERATIONBACKUP
DATABASE"$ALL"
SQLHOST"VirtualNode"
NBSERVER"MasterServer"
BROWSECLIENT"VirtualNode"
MAXTRANSFERSIZE0
BLOCKSIZE0
ENDOPERTRUE
Once these changes are made, perform the backupoperation again.
