Error with Virtual Machine change tracking. It may be necessary to power cycle the vm, or contact VMware support regarding the QueryChangedDiskAreas API.
Have anyone faced this issue before and have an idea to solve it?
The issue I ran into occurs when QueryDiskChangedAreas API is called to list all of the allocated blocks. The allocated blocks returned by the API has had sector 0 missing and I was unable to boot a VM post restore. Although, the same sector issue can return incorrect information in a backup as well
Please provide some additional details.
CV Version
Vmware version
I’ve included a link that may help answer some of your questions.
Never had this issue, but as the CBT attribute is managed by VMWare I would try to manually reset the attribute for 1 VM and see if it fixes the issue for that VM.
The issue I ran into occurs when QueryDiskChangedAreas API is called to list all of the allocated blocks. The allocated blocks returned by the API has had sector 0 missing and I was unable to boot a VM post restore. Although, the same sector issue can return incorrect information in a backup as well
Please provide some additional details.
CV Version
Vmware version
I’ve included a link that may help answer some of your questions.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.