cancel
Showing results for 
Search instead for 
Did you mean: 

Duplicates Fail when DB is on SQL Express

Jeremy_Roberts
Level 3

When you put the Database on a version of SQL other than on a full copy, Duplicate Jobs that are run from any backup server than the one holding the Database fail with the following error

Completed status: Failed
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.
Final error category: Job Errors

Unable to determine ADAMM media identifcation.  Catalog query failed.

The work around is to catalog the tapes and then re run the jobs, which for us is not practicle.

This has been the case since the beginning of time and still it does not seem be recognised as a real problem by Veritas/Symantec.

As Backup Exec does stupid things like restart SQL when ever you make changes or install updates it is highly undesirable for it to sit on our main SQL server.

Surely it is about time athat they sorted out all these little database annoyances.

2 REPLIES 2

Striker_303
Level 6
Employee

1. Backup exec version

2. SQL express version you have tried

3. Size of BEDB .mdf and .ldf files

4. Do you see data to restore when on SQL express

5. What errors do you have in Event viewer?

Jeremy_Roberts
Level 3

Every version of backup exec we have ever used. Specifically version 8, 9, 10 12, 12.5, 2010, 2010 R2

Every cut down version of SQL, MSDE 2000, 2005 Express and 2008 Express.

Current DB size on the CASO server of a 5 day old installation is

mdf 27,480 KB

ldf 1,536 KB

the install also puts a copy of SQL express on the second server

mdf 14528KB

Lldf 1,280

s

Items on the original tape are not available for restore until the tapes are catalogued. The original backup completes with no errors.

The entries in the event log relate to failed duplicate task are the same as the ones in the original post

This error has only occured when we have used a MSDE/Express versions of SQL. It only occurs when the backup server doing the backup job is not the CASO server. Though not all duplicate jobs fail, but those that do are done by the second non CASO server.