in vSphere 8.0U2 Changed Block Tracking (CBT) files may become inconsistent leading to backups not capturing the right data.
Symptoms may include:
We strongly recommend to contact your backup software vendor to verify whether they have evolved steps to assist in recovering existing backups.
Migration of a powered-on VM after growing a disk can result in data corruption.
[VMC on AWS] VMDK Hot-extend operation and potential data loss
Powering VMs off and then back on again, hot-remove and hot-add of virtual disks, and suspending and resuming VMs, will cause the VM to be temporarily unavailable for production.
For some guest operating systems, creating a snapshot in virtual disks can fail, cause slowness or other problems. This particularly happens with very high input-output VMs such as database servers, and also with multi-writer servers, many of which are also often database servers.
For the CBT reset work-around, resetting CBT on VMs will cause the next backups to be full backups, which may require more resource bandwidth or time to process. These VMs may need their changes to be staggered to avoid oversaturation of the system, depending on your resources.