VDP duplicate backup jobs / Case #07653893 — Backup job failed. Reported that there is a duplicate job

[LEWISF]

So I have an issue where I had a few jobs reporting that there was a duplicate job. Since the job was duplicated, I could not edit the job to make any changes. I ended up cloning the job, deleting the job that reported it was duplicated, and renaming the cloned job back to the original. Ran an active full and so far all looks good.

The reason for my post is I am trying to figure out why this happened? I'm wondering if our DR testing could account for the duplicate job issue?

Any info is appreciated.

[david.domask]

Hi LEWISF,

Thank you for sharing the case number, but may I ask is it the correct one? The case discussion is about snapshot creation failures and I'm not seeing where duplicate jobs are mentioned -- do I understand correctly that after cloning the jobs and deleting it the snapshot issues began or did the cloning end up resolving the issues when the job ran on schedule?

I don't see any details in the case on what was done during the DR testing either, so cannot comment on if it's related, so if you could clarify the above would be great.

If this is related to the same issue in the case, I would advise please ensure it's documented in the case as well so Support can review the details.

[LEWISF]

Hi David -

That's the correct case info.

Lewis

[david.domask]

ah, apologies, I must have gotten to wrong case somehow, please ignore the above post.

Looks like Support is confirming the resolution steps, but still needs to review how this happened in the first place so please continue with Support regarding why we ended up with this error.

Off the top of my head, if there was perhaps an unexpected server shutdown during a Move Backup or legacy backup upgrade operation, this may have resulted in the situation you're experiencing. Just guesses though, Support will be able to tell more from the logs. (To be clear, the error looks to be about duplicate _backups_ associated with the same job -- cloning the job and mapping helps because it removes this unexpected situation)

So please continue with Support to try to understand how we ended up in the situation with two backups assigned to the original jobs, and proceed with the current solution to get the jobs running again.