Problem
Vault catalog backup fails with status 294 and 239.
Error Message
Status Code294: vault catalog backup failed
Status Code 239: the specified client does not exist in the specified policy
The vault sessiondetail.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
Cause
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.
Solution
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 media server. This mismatch between media server as the CLIENT_NAME and the master server name in the policy caused the vault catalog backup to fail.