Transform Patch Failed

[b.vanhaastrecht]

Hi,

Recently one of the drives in a local RAID set failed. This resulted in a heavy rebuild and storage glitches while a copy job was targeted to this storage. After we sovled the storge glitch, the copy jobs transform failed with "Patch Failed". On other setups we've seen the same error occour when network glitches accour, or when the copy job for some reason hangs and we need to hard cancel it. Result is Patch Failed, this means it comes accross corruption within the target backup file and can't continieu. We've contacted support (#00615991), and they stated there's currently no method or procedure to recover from this corruption, only checks to help you point our the corrupted file. They advised to start a new copy chain, so we did.

Doing a new sync, wel in a LAN is not a real plroblem, but you loose your history in the gui. In order to start a new backup copy, you need to remove the previous one from Veeam (delete from backups), then rename the backup folder. Then initiate the copy job again. Result, target repository folder naming overhead/management, Disk chain history gone; customer unhappy. (You could import, but stays on imported, doesn't get linked back to the original chain.)

Why isn't there any recover method to replace the corrupted part of the chain, while having the source on your primary repository. Or, when you don't got it anymore, cut out that particular restore point.

Regards,
Bastiaan