#Veeam backup copy job Patch
#Veeam backup copy job full

We still have two jobs that won't autostart and only work if we manually sync them.

Since we did these changes here's what else ended up happening: Seems that when we fix something it completely breaks some other jobs. However other backup copy jobs that were running before and now failing with timeout issues. And it does seem like it helped the jobs autostart issues as about 90% of them seem to be autostarting correctly now after the parent backup jobs run. Now our 5 jobs have data that is going offsite. Really weird, but we ended up cleaning the new restore points, removing the chain from the configuration again, rescanning and remapping the data to the new job and that fixed the issue. But only the new data, the old chain was still in the correct location. So backup copy data for one job was under the folder of another backup copy job. This fixed some of them, but on others we ended up discovering that data was going to incorrect locations, as if Veeam had pulled the backup location from another job, then appended the location it wanted to it.

Edited every other backup copy jobs and clicked next through all options without changing any settings.

Mapped the new backup copy jobs to the data that was imported.

Ran a rescan against all the repositories to re-import the backup copy data.

Created brand new backup copy jobs with the same settings as the broken jobs.

Removed the data for each job form the Veeam configuraiton (right-click -> remove from configuration).

Disabled and renamed all broken jobs (jobs that wouldn't even run when issuing a sync now).

Still no help from support, we ended up fixing some of the issues by ourselves. It took a few days to escalate from tier 1 to 2, and now we're not sure how long the escalation from tier 2 to 3 will be. I guess the question is where do we go at this point, is there something we should be trying to do without support? I know the forum posts are not designed to speed up case resolution but we're not sure where else to go from here. If we were to have a disaster requiring offsite recovery right now we'd only have nearly 3 week old restore points to recover with for 1/4th of our critical production SQL servers. We have data that is more than 2 weeks out of our RPO for offsite and there's been no way to get the data updated.

#Veeam backup copy job full

If it was a smaller issue it wouldn't be that big of a deal, but at this point the case has been open for 2 full weeks (9 business days if you exclude July 4th) and we are no closer to a solution or even work arounds. From our point of view support has been abysmal the whole case, multiple instances of scheduling remote sessions days out or reviewing logs for extended periods of time. The case supposedly is set to be escalated to tier 3 or R&D, but we really are getting desperate at this point. At this point we have someone manually kicking off every backup copy job every day, and while that somewhat works for the jobs that do run, there are multiple jobs that don't run even with triggering the sync manually. Not really sure, but at this point we've tried everything we could, duplicating jobs, creating brand new jobs, everything just doesn't seem to be working.

#Veeam backup copy job Patch

I never saw a fix in the patch notes for that specific problem, but the tech confirmed it would resolved the issue and sure enough after installing the patch the backup copy job corruption stopped happening.Д«ut something tells me the corruption was somewhere else in the database and all we did was move it somewhere else, and now that corruption is wherever the job triggers are stored or something else related to core backup copy job function. But we were having jobs getting 'corrupted' by about 2-3 times a week for almost a month until the first patch for V11 came out. Eventually the tech recommended editing the broken job and clicking next through all the prompts without changing settings and then saving it, and that would fix the job. History wise, when we updated to V11 we started having a strange issue with backup copy jobs constantly failing reporting timeout issues (previous case 04696697). So something actually tells me that this has something to do with a bug in V11 at this point.