Details about why policy based monthly duplicate backups will fail.

Article:TECH87512  |  Created: 2009-01-07  |  Updated: 2014-01-16  |  Article URL http://www.symantec.com/docs/TECH87512
Article Type
Technical Solution

Product(s)

Environment

Issue



Details about why policy based monthly duplicate backups will fail.


Error



e0009444 - The requested source duplicate backup sets catalog record could not be found. Perhaps the media containing the source backup sets was previously deleted.

UMI-V-79-57344-1538 , V-79-57344-37956


Solution



This technote explains the behavior exhibited by the scenario described in the related document "324099 : Only policy based monthly duplicate backups fail."

Only policy based monthly duplicate backups will fail with either one of the following errors:
e0000602 - A query for media on which the data set being read is continued was unsuccessful. Insure that all media in the family have been inventoried and cataloged.
e0009444 - The requested source duplicate backup sets catalog record could not be found. Perhaps the media containing the source backup sets was previously deleted.


How does a policy based duplicate backup work?

A policy based duplicate backup works principally the same way as manual duplicate backups. A manually executed duplicate backup (Menu File - New - Duplicate Backup sets Job) uses the catalog entry of the backup set to be duplicated, to find the media from where the duplication will take place.
 
The policy based duplicate job also has a selection list containing catalog entries of the backup sets created by the backup job with which it is linked. The catalog entries in the duplicate backup selection list are maintained dynamically as explained below:
 
1) If the backup to be duplicated, took place "n" times, the duplicate backup selection list will contain "n" entries indicating the "n" occurrences of the backup whose backup sets are to be duplicated.
 
2) When a duplicate backup has successfully duplicated all the related backup sets, the duplicate backup selection list is cleared.
 
Activities in the above points 1 and 2 keep reoccurring during the lifetime of the policy based monthly duplicate backup.
 
Why does only the duplicate monthly backup fail?
 
If every occurrence of the backup overwrites its last backup set, "<catalog entry not found>" is shown in the duplicate backup selection list. If the duplicate backup encounters such entries in its selection list, it fails with the above mentioned error.
 
 
 
 
 
 
 
Why does the weekly duplicate backup work?
 
The weekly duplicate backup of the full backup would work fine because the source of the duplication i.e the source backup set will still be available because of its overwrite protection period.
 

Supplemental Materials

SourceError Code
Valuee0009444
Description

The requested source duplicate backup sets catalog record could not be found. Perhaps the media containing the source backup sets was previously deleted.


SourceError Code
Valuee0000602
Description

A query for media on which the data set being read is continued was unsuccessful. Insure that all media in the family have been inventoried and cataloged.


SourceUMI
ValueV-79-57344-1538
Description

- A query for media on which the data set being read is continued was unsuccessful. Insure that all media in the family have been inventoried and cataloged.


SourceUMI
ValueV-79-57344-37956
Description

The requested source duplicate backup sets catalog record could not be found. Perhaps the media containing the source backup sets was previously deleted.



Legacy ID



322882


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


Terms of use for this information are found in Legal Notices