-
Title
Change Block Tracking not enabled on SCSI (0:x) -
Description
CBT is enabled, but logs show failing.
In taks log you may see messages that the CBT is not enabled or has failed for a certain disk.
-
Cause
This can be cause by multi-disk virtual machine with disks on different datastores.
For example; a 3 disk VM has 2 disks on one datastore (vm_name.vmdk & vm_name_1.vmdk) and the third disk is on a second datastore (vm_name.vmdk). What happens is the third disk on second data store gets named the same as the base disk in the first datastore. So when a snap shot is opened on the VM you get
datastore 1:
vm_name-000001.vmdk
vm_name-000001-ctk.vmdk
and
vm_name_1-000001.vmdk
vm_name_1-000001-ctk.vmdk
Datastore 2:
vm_name-000002.vmdk
vm_name-000002-ctk.vmdk
For some reason VMware sees the same named disk in second datastore as first disk and gives it a 000002 so it looks like there are 2 snapshots on base disk when there should be only one level of snapshots on each disk.
As vRanger is expecting to see 000001-ctk on all disks will show as not enabled and failed for other disks.
-
Resolution
If you want to use change block tracking on this VM you will have to rename disk on VM. This can be done several different ways, the following is a link to VMware KB covering renaming a VMDK.