Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Duplicate fails when DB is on SQL Express/MSDE

Created: 18 Nov 2010 | 2 comments
Jeremy Roberts's picture
2 Agree
0 Disagree
+2 2 Votes
Login to vote

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.

Comments

Ken Putnam's picture
13
Jan
2011
0 Votes 0
Login to vote

This is more a limitation of

This is more a limitation of SQL Express than BackupExec, isn't it?

If this response answers your concern, please mark it as a "solution"

Jeremy Roberts's picture
13
Jan
2011
0 Votes 0
Login to vote

After hammering away at it

After hammering away at it for a couple of days I think I have solved the problem, it would seem that if you use SQL express it will install a copy on all the Backup servers. When the job is run it writes to the local DB but when the CASO server kciks off the duplicate it can't find what to duplicate in its own DB untill you catalog the tapes. This is probally down to the way the software is installed on the second server, they may be a tick box or something that gets around this problem, though you can make changes to the behaviour by using the BEUtililty and mucking around with the DB settings.

Now that SQL Express 2008R2 allows for DBs of 10GB and given Backup Execs desire to restart SQL it makes sense to use this rather than a full copy of SQL on a separate server.