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 Server backups fail with Status Code 239 when attempting to back up a SQL Cluster. The exit status 239 is caused because the name being passed from the cluster does not reflect the name in the SQL policy.
Troubleshooting
Log Files: N/A
A review of the batch file ( .bch) being used to attempt the backup of the SQL cluster shows something similar to the following:
Where "VirtualNode" is the name of the virtual SQL server, 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 following snippet:
Once these changes are made, perform the backup operation again.
NetBackup for Microsoft SQL Server backups fail with Status Code 239 when attempting to back up a SQL Cluster. The exit status 239 is caused because the name being passed from the cluster does not reflect the name in the SQL policy.
Troubleshooting
Log Files: N/A
A review of the batch file ( .bch) being used to attempt the backup of the SQL cluster shows something similar to the following:
OPERATION BACKUP
DATABASE "$ALL"
SQLHOST "VirtualNode"
NBSERVER "MasterServer"
BROWSECLIENT "NodeA"
MAXTRANSFERSIZE 0
BLOCKSIZE 0
ENDOPER TRUE
Where "VirtualNode" is the name of the virtual SQL server, 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 following snippet:
OPERATION BACKUP
DATABASE "$ALL"
SQLHOST "VirtualNode"
NBSERVER "MasterServer"
BROWSECLIENT "VirtualNode"
MAXTRANSFERSIZE 0
BLOCKSIZE 0
ENDOPER TRUE
Once these changes are made, perform the backup operation again.
