Discussions specific to the VMware vSphere hypervisor
Post Reply
davecla
Enthusiast
Posts: 26
Liked: 4 times
Joined: Feb 03, 2016 9:40 pm
Full Name: Dave Clarke
Contact:

Corruption in Backup Copy Job

Post by davecla » Dec 06, 2017 11:55 pm

#02413081

I have a backup copy job failing with the error -

Failed to generate points Error: Agent: Failed to process method {Transform.Patch}: There is an item with the specified name and another type.
Failed to merge full backup file Error: Agent: Failed to process method {Transform.Patch}: There is an item with the specified name and another type.

It apprears there is some corruption in the copy.

Tech Support have suggest I just delete the backup copy and start again. This isn't my favorite fix - it takes about a week to make a full copy to the remote location.

Can anyone suggest a better approach to correcting this - surely I can keep one of the good copies as a seed??

veremin
Product Manager
Posts: 17005
Liked: 1455 times
Joined: Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin
Contact:

Re: Corruption in Backup Copy Job

Post by veremin » Dec 07, 2017 10:01 am

Storage level corruption might have been the reason of invalid backup chain, but support team should be able find the root cause. If you're not satisfied with the level of support provided and don't accept re-creating chain from a scratch as an answer (which is understandable), you can always escalate the case, using "Talk to Manager" button. Thanks.

davecla
Enthusiast
Posts: 26
Liked: 4 times
Joined: Feb 03, 2016 9:40 pm
Full Name: Dave Clarke
Contact:

Re: Corruption in Backup Copy Job

Post by davecla » Dec 11, 2017 8:57 pm

There was a (full) backup job in the chain from a month again that was marked "incomplete" - basically everything after that was no good.
I ended up removing all the jobs since my last good full (2 months ago) and starting again from there.

Disappointing that Tech support seems to be focused on getting the call closed as quickly as possible without spending any time sorting the underlying issue or assisting with recovery options.
Also seems odd that incrementals forward of the incomplete full backup ran successfully when the underlying "full" backup was incomplete.

veremin
Product Manager
Posts: 17005
Liked: 1455 times
Joined: Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin
Contact:

Re: Corruption in Backup Copy Job

Post by veremin » Dec 12, 2017 12:43 pm

There was a (full) backup job in the chain from a month again that was marked "incomplete" - basically everything after that was no good. Also seems odd that incrementals forward of the incomplete full backup ran successfully when the underlying "full" backup was incomplete.
Incomplete doesn't mean corrupted - most likely, the specified sync interval was too short for a backup copy job to complete full cycle, during subsequent run the job should have copied missing blocks for full backup as well as new blocks for incremental one.
Disappointing that Tech support seems to be focused on getting the call closed as quickly as possible without spending any time sorting the underlying issue or assisting with recovery options.
Next time, kindly, do not hesitate to escalate the ticket, whenever you feel there is a need to.

Thanks.

Post Reply

Who is online

Users browsing this forum: Google [Bot], zonich and 14 guests