Gostev wrote:Disabling CBT is sufficient to both prevent and remediate the issue, because this will make jobs physically compare latest state of disk in backup or replica with its actual state, and transfer any non-matching blocks over as a part of incremental backup (along with actually changed blocks), thus fixing any corruption that may already be in place.
Gostev wrote:No, this is not normal, as calculating hashes requires little to no CPU resources. And this is the only extra operation that proxy does when CBT is disabled, comparing to incremental runs with CBT enabled.
sphilp wrote:VMware appears to have issued a patch for this, it came through Update Manager an hour or so ago for us.
Patch ID: ESXi600-201511401-BG
KB Article: http://kb.vmware.com/kb/2137546
I'm curious about what the "recovery" process for our backups and replication should be. Is the suggestion that we run an Active Full against each job to get a "known good" set of backups after the VMware patch has been applied?
Users browsing this forum: No registered users and 1 guest