Not sure if you all are aware of this bug, it just recently came to light in an email from Veeam, here is a link to the Vmware
KBhttp://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2090639
Basically any disk on a VM that has been increased by 128GB or more is at risk of this CBT bug and that bug affects all versions of VMware form 4.x up to current and it means that backups may be no good. From what I can understand, there is a way to reset CBT on a VM but I am not clear if its necessary to run a full backup after doing this to resolve the issue. There is lots of chatter in the Veeam forums about this, its definitely a VMware issue and they have said no fix is forthcoming anytime soon which isn't good.
KBhttp://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2090639
Basically any disk on a VM that has been increased by 128GB or more is at risk of this CBT bug and that bug affects all versions of VMware form 4.x up to current and it means that backups may be no good. From what I can understand, there is a way to reset CBT on a VM but I am not clear if its necessary to run a full backup after doing this to resolve the issue. There is lots of chatter in the Veeam forums about this, its definitely a VMware issue and they have said no fix is forthcoming anytime soon which isn't good.