NetBackup catalog archiving fails with "failed to get last catalog archive backup image: no entity was found (227)."
Problem
Unable to successfully run catalog archiving for any clients.
The ' bpcatlist ' command returns successfully and shows there is are valid backups suitable for archiving. The ' bpcatlist ' command passes all, or a defined section of backup images (specific client, policy, date/time), to the ' bpcatarc ' command, which creates a job to archive the backup image FILES files to reduce the overall NetBackup catalog size.
NB: bpcatlist, bpcatarc, bpcatrm all exist within the folder ' /usr/openv/netbackup/bin/admincmd
Error Message
# bpcatlist | bpcatarc | bpcatrm
bpcatarc: failed to get last catalog archive backup image: no entity was found (227)
The Catarc (Catalog Archive) job will start and complete with a status 0 in the Activity Monitor. The Catarc job will perform a backup of the necessary backup image FILES file(s), however, as the failure occurs before the catalog ID (Catarcid) can be applied to the backup image being archived, the FILES file(s) is NOT archived from the images database and these should NOT be manually removed. When the problems are resolved and the backup images can be archived successfully using the ' bpcatlist | bpcatarc | bpcatrm ' commands, then the backup images will be successfully archived.
Cause
The first "SERVER" entry in the NetBackup configurations file ( /usr/openv/netbackup/bp.conf ) must be the valid server name for the master server. This name must also match the master server name configured in the "catarc" policy.
In this case, the first ' SERVER ' entry in the ' bp.conf ' file was an IP address. The master server was configured with a host name in all other configuration settings.
This issue can occur if the ' bp.conf ' file is configured with the short name for the master server and the "catarc" policy is using the fully qualified domain name, and vice-versa .
BPDBM log
04:52:03.056 [20788] <2> db_logimagerec: protocol version 9 qtype 82 vers 0 client <INVALID_MASTER_NAME> policy catarc
...
04:52:03.056 [20788] <2> image_db: Q_IMAGE_LAST_BACKUP
04:52:03.056 [20788] <2> get_last_backup_lock: ?
04:52:03.056 [20788] <2> image_dir: ?
04:52:03.056 [20788] <2> image_dir_name: ?
04:52:03.056 [20788] <2> get_last_backup_lock: No images for client <INVALID_MASTER_NAME>
04:52:03.057 [20788] <2> process_request: request complete: exit status 227 no entity was found; query type: 82
Solution
Remove/replace the <INVALID_MASTER_NAME> entry in the ' /usr/openv/netbackup/bp.conf ' file, with the valid/correct master server hostname. The FIRST ' SERVER ' entry in the ' bp.conf ' NetBackup configuration file must be the master server hostname.
Applies To
This issue was seen on a UNIX/Linux NetBackup 7.1 master server.