Scribd
Upload
323 views

Code 239

The document describes two problems with NetBackup backups failing with status code 239 due to a mismatch between the client name specified in the backup policy and the client name being passed during backup operations. The resolution in both cases is to modify configuration files so the client name matches between the policy and backup operations.

Uploaded by

subhrajitm47
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
323 views

Code 239

The document describes two problems with NetBackup backups failing with status code 239 due to a mismatch between the client name specified in the backup policy and the client name being passed during backup operations. The resolution in both cases is to modify configuration files so the client name matches between the policy and backup operations.

Uploaded by

subhrajitm47
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Problem

Vault catalog backup fails with status 294 and 239.

Solution

Error Codes(s)/Message(s): Status Code 294: vault catalog backup failed Status Code 239: the specified client does not exist in the specified policy Overview: User-directed backup requests present the configured CLIENT_NAME of the requesting host to the master server when initiating a backup. The master server confirms that the requested client name matches a client in the policy before submitting the job. A mismatch will result in a failure to queue the job, including vault catalog backups which are user-directed backup requests submitted from the master server to itself. A mismatch will not affect scheduled catalog backups because they are initiated directly from the policy, not user-directed. Troubleshooting: The vault session detail.log will confirm that the vault catalog backup failed with status 239.
STEP = catalog_backup

...snip...
09:00:08.073 [2828.6648] <2> vltrun@DoCatalogBu^32: Catalog Backup job starts with policy "catalog_vault" and schedule "full_catalog_vault"... 09:00:11.260 [2828.6648] <2> vltrun@DoCatalogBu^32: Catalog Backup job ends with status = 239 09:00:11.260 [2828.6648] <2> vltrun@VaultJobMonitor::_send_try_msg^32: At 1226595611 sent TRY_MSG: VAULT_CTLG_BKUP_FAILED 1226595611 09:00:11.260 [2828.6648] <16> vltrun@DoCatalogBu^32 Catalog Backup step failed! 09:00:11.260 [2828.6648] <16> vltrun@DoCatalogBu^32 FAILed NB_EC=239 NB_MSG=the specified client does not exist in the specified policy

Resolution: The bp.conf file should contain only one CLIENT_NAME. It must match the client specified in the policy for the vault catalog backup to be successful.

In this case, the site had mistakenly added multiple CLIENT_NAME keywords to the bp.conf file, one for each SERVER keyword. Thus all user-directed client operations initiated on the master server were using the last CLIENT_NAME, which was the name of a mediaserver. This mismatch between mediaserver as the CLIENT_NAME and the master server name in the policy caused the vault catalog backup to fail.

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

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

Solution
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:
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.

You might also like