Policy based duplicate jobs configured to start on a timed schedule fail when using week number scheduling

Article:TECH53097  |  Created: 2007-01-13  |  Updated: 2014-01-19  |  Article URL http://www.symantec.com/docs/TECH53097
Article Type
Technical Solution

Product(s)

Environment

Issue



Policy based duplicate jobs configured to start on a timed schedule fail when using week number scheduling

Error



e00081d2 - The script associated with this job contained no valid selections.
e0009444 - The requested source duplicate backup sets catalog record could not be found. Perhaps the media containing the source backup sets was previously deleted.

Solution




Scenario:

Within a policy, the monthly full backup-to-disk (b2d) jobs are configured to run during week 1 of each month and the weekly full b2d jobs are configured to run during weeks 2 to 5. Within the same policy, duplicate jobs to tape are configured to run the day after the original b2d jobs using a similar week based schedule.

Problem:

Depending on the history of previous jobs and the media retention configuration of the media server the following will be experienced:
  • The duplicate job will fail reporting "e0009444 - The requested source duplicate backup sets catalog record could not be found. Perhaps the media containing the source backup sets was previously deleted."
  • The duplicate job will fail reporting "e00081d2 - The script associated with this job contained no valid selections."
  • The duplicate job will complete successfully but will have used an incorrect media set for the tape based media
  • The duplicate job will complete successfully but will have protected data from an earlier instance of one of the original weekly or monthly jobs instead of that backed up the previous day.
Cause:

This behavior is experienced because the end of the month occurs between the start of the original b2d job and the start of the duplicate job. This means that the original job is being run as a weekly job based on week 4 or week 5, but the monthly duplicate job starts the next day because the date is now within the week 1 period. The jobs which start the following week will also be affected as the initial b2d job will be based on week 1 resulting in a monthly job, but the duplicate will be based on week 2. Once an error has occurred within the policy, the later operation of duplicate jobs within the same policy can also fail.

Workaround:

Within the affected policy, edit the templates for both the duplicate weekly and monthly jobs and enable the schedule option entitled "Run only according to rules for this template."


Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.
This issue is currently under investigation by Symantec Corporation. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release.  If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Symantec Sales representative or the Symantec Sales group to discuss these concerns.  For information on how to contact Symantec Sales, please see    http://www.symantec.com
Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.



Supplemental Materials

SourceETrack
Value1110458
DescriptionPolicy based duplicate jobs configure to start on a timed schedule fail when using week number scheduling

SourceUMI
ValueV-79-57344-3324
DescriptionThe script associated with this job contained no valid selections

SourceUMI
ValueV-79-57344-37956
DescriptionThe requested source duplicate backup sets catalog record could not be found. Perhaps the media containing the source backup sets was previously deleted.


Legacy ID



290577


Article URL http://www.symantec.com/docs/TECH53097


Terms of use for this information are found in Legal Notices