- Downgrade the affected ESXi hosts to version 5.5, and downgrade the virtual Hardware Version from 11 to 10, if necessary. For more information, see Reverting to a previous version of ESXi (1033604) and Downgrading the virtual machine hardware version in ESX/ESXi (1028019).
- Shutdown the virtual machine before doing an incremental backup.
- Do a full virtual machine backup rather than an incremental backup.
Veeam users have one more option, and that is to disable the use of CBT data in the advanced job settings. Your backups and replicas will remain incremental, but they will take longer, because the job will need to read the entire source disk to determine the changes. Disabling CBT is essential – otherwise, even Active Full backup may contain corruption, because CBT data is used there too to determine and skip zeroed regions of virtual disks. On the other hand, 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.