NetBackup for Microsoft SQL Server backups fail with Status Code 239 when attempting to back up a SQL Server Cluster

Article: 100017117
Last Published: 2009-01-01
Ratings: 0 0
Product(s): NetBackup & Alta Data Protection

Problem

NetBackup for Microsoft SQL Server backups fail with Status Code 239 when attempting to back up a SQL Server Cluster

Error Message

STATUS CODE 239: the specified client does not exist in the specified policy

Solution

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 from the 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 the following:

OPERATION BACKUP
DATABASE $ALL
SQLHOST "VirtualNode"
NBSERVER "MasterServer"
BROWSECLIENT "NodeA"
MAXTRANSFERSIZE 0
BLOCKSIZE 0
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 following snippet:

OPERATION BACKUP
DATABASE $ALL
SQLHOST "VirtualNode"
NBSERVER "MasterServer"
BROWSECLIENT "VirtualNode"
MAXTRANSFERSIZE 0
BLOCKSIZE 0
ENDOPERTRUE

Once these changes are made, perform the backup operation again.
 

 

Was this content helpful?