Duplicate backup fails with error 0xe0009444 - The requested source duplicate backup sets catalog record could not be found

Article:TECH43264  |  Created: 2005-01-18  |  Updated: 2013-04-23  |  Article URL http://www.symantec.com/docs/TECH43264
Article Type
Technical Solution

Product(s)

Languages

Problem



Duplicate backups fail with error "Final error 0xe0009444 - The requested source duplicate backup sets catalog record could not be found."


Error



Final error: 0xe0009444 - The requested source duplicate backup sets catalog record could not be found. Perhaps the media containing the source backup sets was previously deleted.

V-79-57344-37956

Unable to determine ADAMM media identification. Catalog query failed.

 


Cause



CAUSE 1:
This error can occur if the corresponding catalog information of the source media for the duplicate backup job is either missing or deleted.

For Example:

If "Backup set A" was to be duplicated, then the catalog information for "Backup set A" is either missing or deleted.

CAUSE 2:
This error can occur with policy driven duplicate jobs. If a job is canceled or does not finish successfully it will try to duplicate the same data the next time it runs. If this source data is no longer available (e.g. if the Backup To Disk (B2D) file has been overwritten), this error will be generated.

Another common scenario is if a policy has a backup template that runs multiple days of the week but the duplicate template is set to only run once a week.  The duplicate job will attempt to duplicate all data backed up since the last duplicate job.  If the Overwrite Protection time is not sufficient to protect the media for the entire week some of the data may be overwritten and not available for duplication.  

For Example:

A policy is created with a backup template that runs Monday through Friday.  This policy also contains a duplicate template that is scheduled to run only on Saturday.  The duplicate template will attempt to duplicate all the data that was backed up Monday through Friday.  If any of the media used in the Monday through Friday backup is overwritten before the duplicate job runs the duplicate job will fail.


Solution



Note: Solutions 1 and 2 are valid for Backup Exec 2010 and earlier versions only.
 
Solution 1:
 
1.  In order to determine the source media, open the job log of the backup set  that needs to be duplicated and go to Device and Media information.

 Figure 1 shows the media that needs to be cataloged.
 
Figure 1
 
 
 
      2. Once the exact media(s) has been determined, it needs to be cataloged. To catalog right click on the media and select Catalog as shown in Figure 2 below.

      Figure 2
 
 
 
3. To confirm the catalog information, go to the Restore tab as shown in Figure 3
 
Figure 3
 
 
 

4. Run the duplicate backup job
  
 
Solution 2:
 
1.  Delete <catalog not found> entries in duplicate selection list
 
a.  Open the Backup Exec console and navigate to the Job Monitor tab
 
b.  Right-click the failed policy duplicate job and select "Edit Selection List"
 
c.  Click the "View Selection Details" tab and delete all "<Catalog not found> [SetX]/SUBDIR" entries
 
d.  Re-run the duplicate
 
2.  If a duplicate job was canceled or did not finish successfully, re-run the duplicate job manually before the original source data is overwritten.  Another possible solution would be to modify the Overwrite Protection time on the source media to make sure that it will be protected until the duplicate job runs again.  
 
3.  If a duplicate job that is part of a policy is failing because the source media has been overwritten, delete the duplicate template from the policy and recreate the duplicate template.  By recreating the duplicate template it will create a new selection list for the duplicate template.  If the duplicate template is not recreated it will continue to try and duplicate the missing data indefinitely.
 
4. Best practice is to run the duplicate with policy template immediately after the original backup job completes.
 
Solution 3:
 
In Backup Exec 2012 the solutions above are not available. As a workaround in 2012, open the job properties and review the duplicate stage settings, then remove the duplicate stage, and click OK.(Figure 4) Then re-open the job properties and add the duplicate stage back in using the previous settings.
 
Figure 4
 
 

 

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 being considered by Symantec Corporation to be addressed in the next major revision of the product.  There are no plans to address this issue by way of a patch or hotfix in the current or previous versions of the software at the present time.  Please note that Symantec Corporation reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests or introduces new risks to overall code stability.  Symantec's plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk. 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

SourceError Code
Value0xe0009444
Description

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

SourceUMI
ValueV-79-57344-37956
Description

The requested source duplicate backup sets catalog record could not be found.

SourceETrack
Value416529
Description

Failed request for media during a duplicate data job.

SourceETrack
Value2828519
Description

CORE: Duplicate backup fails with 0xe0009444 or 0xe0000602 error

Related Articles



Legacy ID



278589


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


Terms of use for this information are found in Legal Notices

Please Sign In

Login using SymAccount.

Knowledge Base Search

Knowledge Base Search

Rate this Article

Help us improve your support experience.

MySymantec

MySymantec

Contacting Support

Contacting Support