Today Veeam has released a fix for the VMware CBT Data Corruption problem. http://kb.vmware.com/kb/2090639
This issue occurs when expanding a virtual disk (vmdk) file with Change Block Tracking (CBT) enabled. This may incorrectly calculate the in-use blocks in the vmdk file. This can cause possible data corruption in backups after extending disk size past the 128G boundary on VMware.
Prior to apply this fix make sure you are running Veeam Backup and Replication 220.127.116.111 (patch 4)
Remember that regardless of your B&R version, the hotfix addresses CBT corruption for new virtual disk extensions only. So you still need to reset CBT manually for all VMs that may have been impacted.
You can download the fix here http://www.veeam.com/kb1940
You can also find a PowerCLI script to reset CBT manually for all VMs that may have been impacted.
Veeam Backup and Replication 8 has a built-in solution for this issue.