Problem

STATUS CODE 199: NetBackup for Microsoft SQL Server database agent backup failed with status 199

Error

operation not allowed during this time period

Solution
An MS-SQL-Server policy must contain a schedule of type Application Backup. If a backup is attempted during a period where there is no open window in the Application Backup schedule, the backup will fail with Status Code 199 (operation not allowed during this time period).

To resolve this issue, modify the Start Window of the Application Backup schedule so that there is an open window covering, at least, the expected backup time period.

An Application Backup schedule called Default-Application-Backup and with a 24x7 open window is set automatically when an MS-SQL-Server policy is created. Except for selecting the desired retention level, it is generally recommended to accept the default settings for this schedule.

Problem
STATUS CODE 199: could not deassign media due to Media Manager error when performing bpsyncinfo -delete

Error

premature eof encountered could not deassign offline catalog backup media in Media Manager volume database Media Manager error 199, the media is allocated for use, host = server1

Solution
Overview: In NetBackup, the cold (off-line) catalog backup can be configured to use two tapes alternately, each with a unique media ID. It may be the case that at some point, the existing tapes need to be replaced by new tapes with different media IDs. This would require the existing tapes to be deleted from the NetBackup Catalog configuration, which is usually done by running the command bpsyncinfo -delete <media_id>. This TechNote describes how the command may fail if NetBackup finds that the media is currently allocated for use. Log files: Outputs of the following commands:
/usr/openv/volmgr/bin/vmoprcmd -d /usr/openv/netbackup/bin/admincmd/bpsyncinfo /usr/openv/netbackup/bin/admincmd/bperror -problems -hoursago <number_of_hours>

Troubleshooting: The output of the bpsyncinfo command shows the following tapes to be used for catalog backups:
Server: server1 Sequence # 1 Last Media Used: BRN104 Written Allocated Type Density ------------------- ------------------- ---------1 03/04/2008 00:56:36 01/03/2008 23:53:04 RMedia dlt 2 never 03/07/2008 09:53:49 RMedia dlt Media ----BRN040 BRN104

The following error occurred, when attempting to delete tape BRN040 from the configuration:
#bpsyncinfo -delete brn040 premature eof encountered

When the -delete option is used with the bpsyncinfo command to delete the tape from the configuration, NetBackup would try to deassign the tape. On this occasion, the deassignment failed as can be seen in the bperror output:
03/07/2008 10:40:31 server1 - could not deassign offline catalog backup media BRN040 in Media Manager volume database 03/07/2008 11:02:22 server1 - Media Manager error 199, the media is allocated for use, host = server1

The log above states that the tape is allocated for use. Checking the output from vmoprcmd, it was found that there was a pending request for this tape:
PENDING REQUESTS ReqId User RecMID ExtMID Density Mode Time Barcode VolGroup

6419

BRN040 dlt

Write 00:55 BRN040

---

Resolution: 1. From the GUI, cancel the pending request for the catalog backup. 2. Attempt to delete the catalog tape again from the NetBackup catalog configuration, by rerunning the bpsyncinfo command:
#cd /usr/openv/netbackup/bin/admincmd #./bpsyncinfo -delete <media_id>

Problem
STATUS CODE 199: Oracle Proxy Copy fails with a NetBackup Status Code 199 (operation not allowed during this time period).

Solution
Overview: Oracle Proxy Copy backups fail with NetBackup Status Code 199 (operation not allowed during this time period) when a Full Proxy Copy backup is required and the backup was initiated by an Incremental schedule. A Full Proxy Copy backup is required if one or more of the following conditions occur: 1) A data file was added to the instance. 2) The number of streams for the backup has changed. 3) There is no record of a previous full backup in the same policy. 4) The schedule name, recorded in the environmental variable NB_ORA_PC_SCHED, is not specified in the backup request (lost in the script or an external scheduler for example). Troubleshooting: If the Proxy Copy backup fails with a NetBackup Status Code 199, check to see if the backup was initiated by an incremental schedule and one of the above listed conditions apply. Then, if a Full schedule in the same policy does not have a window open during this time, the backup fails as described. Log files: N/A Resolution: The solution to this problem is to temporarily add an open schedule window to the Full automatic schedule, in the same backup Policy, that is concurrent with the next incremental schedule window or to wait for a full backup to be initiated by the policy.