STATUS CODE 227: When using Veritas NetBackup (tm), the parent job for a hot catalog backup fails with a Status 227, even though the child jobs complete with a Status 0 (successful).

Overview:
It is possible for the parent job of ahot catalog backup to fail with a Status 227 even though the child jobs completewith a Status 0.  This will occur when the Disaster Recovery (DR)information is missing from the hot catalog backup policy.  This has alsobeen seen when the DR information can be entered, but is not properly saved whencreating the hot catalog backup policy.  The Status 227 will occur for theparent job after the child jobs complete successfully.  The failure willoccur when the bpdbm daemon attemptscannot find the catdirinfo file which contains the DR information fromthe policy.

Troubleshooting:
It will be necessary to check theDisaster Recovery tab of the hot catalog backup policy to see if a DR path hasbeen specified. (Figure 1)  To verify the DR settings do thefollowing:
1. Launch the NetBackup Java Administration Console
2. Go totthe Policies section and double click on the hot catalog policy
3.Click on the Disaster Recovery tab to display the DR settings
Thefollowing example show a policy where no DR settings have beenadded.

Figure 1 - Disaster Recoverytab of the hot catalog backup policy

 

It is also possible to check the policy directory forthe existence of the catdirinfo file.   The following example isfrom a Solaris 9 master server which shows the catdirinfo file does notexist.
# ls -l/usr/openv/netbackup/db/class/<hot_catalog_policy>
total8
-rw-------   1root  other    102 Mar  6 17:32clients
-rw-------   1root  other    809 Mar  6 17:32info
drw-r-xr-x   4root  other    512 Apr 19 13:30schedule

Log Files:
The /usr/openv/netbackup/logs/bpdbm/log.<date> file will show thefollowing errors when trying to load the DR information for the hot catalogbackup policy.
<2>exec_catalog_DR_protection: classname=Hot_Catalog,fqDRImagePath=<image_dir>Hot_Catalog_1142615109_FULL, status=0
<32> wimageproblem: Failed toload DR record from policy Hot_Catalog (227)
<2> db_error_add_to_file:dberrorq.c:midnite = 1142571600
<2> db_error_add_to_file:dberrorq.c:midnite = 1142571600
<16> exec_catalog_backup:Unable to execute DR protection for Hot_Catalog_1142615109_FULL (227)
<2> bpdbm: request complete:exit status 227 no entity was found

Resolution
It will be necessary to configure thedisaster recovery information for the hot catalog backup policy.  This canbe done by adding a valid path name to the Path: section of the DisasterRecovery tab of the policy. (Figure 1)  It is also possible to enable theemailing of the DR information to the system administrator.  To do thisclick the Send in an E-mail attachment (recommended) option and enter avalid email address.  Once a valid path name has been added the policy canbe saved and the catalog backups will no longer fail with a Status227.  

When selecting a path name to use for the DR informationVeritas recommends that the directory not reside on the root file system or thefile system on which NetBackup is installed.  The DR information contains alisting of the catalog media used to perform the backup and is necessary toperform a hot catalog recovery.

In situations where the DR informationwill not properly save delete and re-create the hot catalog backuppolicy.  This should allow the DR information to save correctly and preventthe Status 227 from occurring.