Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Duplicate regularly fails to find backup sets

Created: 06 Nov 2012 • Updated: 15 Nov 2012 | 3 comments
IPG's picture
This issue has been solved. See solution.

Hi all,

I've been having this issue ever since upgrading to Backup Exec 2012 with my duplicate jobs.  When the duplicate job runs, about a thrid of the time I get the error message:

Duplicate -- The job failed with the following error: The requested source duplicate backup sets catalog record could not be found. Perhaps the media containing the source backup sets was previously deleted.

I know that my full & incremental jobs have successfully been duplicated before being deleted, so I don't understand what's causing this message.  I can fix this by deleting the duplicate job and recreating it, but then the error message comes back in about a week.  I have about 15 servers I'm backing up, and about 5 of them experience this issue.

Because Backup Exec 2012 has no way of viewing job selections for duplicate jobs I'm having a very hard time trying to figure out what's going on.

Can anyone advise me on how to troubleshoot this?!

Thanks

Comments 3 CommentsJump to latest comment

lmosla's picture

Hi IPG,

Have you checked out this Technote yet  http://www.symantec.com/business/support/index?page=content&id=TECH43264

and, have you installed all the available live updates, specifically SP1a resolves quite a few catalog and database issues.

IPG's picture

Hey lmosla,

I have read that technote, it seems to say the problems occur when a backup job fails or the catalog is deleted but my duplicate jobs are running less than 12 hours after the backup finishes successfully so I don't believe this to be the case.

Also it's difficult because that technote applies to older versions of Backup Exec, so I can't actually follow Solution 2 which I think would help a lot at determining what was missing.

Backup Exec is fully up to date.

Thanks for your reply.

IPG's picture

I ended up using duplicate jobs that run at the end of the full / incremental jobs rather than running on a schedule later on - I haven't had this problem since.

SOLUTION