stevenrodenburg1 wrote:I too sensed a "CBT should be avoided" kind of reply but that response is unfounded. I mean, V5 never had a problem, then came V6 and the trouble started, then all off a sudden it's VMware's fault....
Cleanup of HotAdd disks can affect changed block tracking.
During backup or restore, disks may be HotAdded, and subsequently removed after task completion. This cleanup might remove the change tracking (ctk) file, so that changed block tracking (CBT) could fail. This issue should resolve itself automatically. If it does not, the workaround is to power cycle the virtual machine.
chriswu wrote:Hi guys
Please can someone tell me how to do:
we can try resetting the CBT for the VM
here is an instruction on how you can reset CBT on the guest VM:
1) power off VM
2) follow the steps shown below:
- You need to set "ctkEnabled" value to false
- You need to set "scsi0:x.ctkEnabled" value to false (false should be set for each disk of the VM in question)
3) power on VM
4) power off VM again (that step is needed to update CTK DataBase)
5) power on VM (from that time you may re-run the job and CTK will be automatically enabled).
I'm not sure how to do step 2.....Where is the settings for this?
Users browsing this forum: Bing [Bot] and 2 guests