You are on page 1of 2

Problem

NetBackup for Microsoft SQL Server database agent backup failed with Status Code 230

Error
Status Code 230: the specified policy does not exist in the configuration database

Solution
The backup script specified a value for the POLICY keyword that was different from the policy that started the backup, or the batch file was executed manually from the client and there was no policy on the master server matching the value of the POLICY keyword. Solution: Remove the POLICY keyword from the backup script, or set its value to an existing policy name.

Problem
STATUS CODE 230: After modification of disk staging storage unit

Solution
ERROR MESSAGE the specified policy does not exist in the configuration database OVERVIEW: Attempts to change a Disk Staging Storage Unit schedule change may cause all DSSU schedules to revert to the default settings and attempts to run those jobs will return a NetBackup status code 230 if there are extra files located in the /usr/openv/netbackup/db/sched directory. TROUBLESHOOTING: Attempts to run the schedule will show the following type errors in the nbpem log:
03/26/2009 10:52:54.857 [jobid=-1 job_group_id=-1 client= type=2 server= task=ID:0x8f70fbc policy=__DSSU_POLICY_XXX] 4 [PemTask::setCompletionStatus] (ID:0x8f70fbc) Status on task changed from PEM_EC_INCOMPLETE (-2) to EC_no_such_class (230) 03/26/2009 10:52:54.857 [jobid=-1 job_group_id=-1 client= type=2 server= task=ID:0x8f70fbc policy=__DSSU_POLICY_XXX] 1 V-116-189

[ExtReqTask::run_specificPolicy] Failed to retrieve policy __DSSU_POLICY_XXX, 230

An additional indication this issue exists is running of the following command returns no data:
/usr/openv/netbackup/bin/admincmd/bpschedule -U

SOLUTION: Administrators can correct this issue by removing the extra files form the /usr/openv/netbackup/db/sched directory. In at least one case, removal of extra files named "days" and "info" files from under the main directory corrected this issue. These files should only exist in the /usr/openv/netbackup/db/sched/schedule_name directory. Example of the above: ls of /usr/openv/netbackup/db/sched showing days and info files directly under the this directory:
-rw------- 1 root root 42 Mar 23 14:39 days drwxr-xr-x 2 root root 4096 Mar 25 13:51 DISK_BACKUP_XXX -rw------- 1 root root 433 Mar 23 14:39 info

Instead the files should exist under the schedule name directory.
/usr/openv/netbackup/db/sched/DISK_BACKUP_XXX: -rw------- 1 root root 47 Mar 25 13:51 days -rw------- 1 root root 473 Mar 25 13:51 info