One or more VM disks have incorrect changed block tracking configuration.Disk "Hard disk #" has incorrect changed block tracking configuration One or more VM disks have incorrect changed block tracking configurationUnable to access file since it is locked. An error occurred while consolidating disks. One of the disks in this virtual machine is already in use by a virtual machine or by a snapshot. (In this case, the files will be there and there will be no locks present in the VM folders.)The operation is not supported on the object.
vMotion of a CBT-enabled VM having multi-writer disk(s) is not supportedThe operation is not allowed. Cannot attach a CBT enabled disk: /vmfs/volumes/########-####-####-####-############.vmdk to CBT enabled VM. Backup products take advantage of Changed Block Tracking (CBT) for incremental backups if CBT is enabled in the virtual machine. For more information on CBT, see Changed Block Tracking (CBT) on virtual machines.
The CBT feature of VMware which facilitates taking incremental backups on virtual machines running on VMware ESXi. CBT identifies and tracks block changes since the last backup, and stores these changes as logs for tracking the backups.
ctkEnabled parameter and then set its value to true.scsi0:0.ctkEnabled, and set its value to true.scsi0:0 in scsi0:0.ctkEnabled indicates the SCSI device assigned to the hard disk that is added to the virtual machine. scsi0:0, scsi0:1, or scsi 1:1. CBT is enabled (or disabled) individually on each disk.vmname-ctk.vmdk file.ctkEnabled parameter to FALSE for the ctkEnabled setting for the VM and for each SCSI disk(s)..vmsd file along with any ctk.vmdk files in the VM folder(s). You can create a subfolder and move them there or just delete them.QueryChangedDiskAreas API might not return any error or the data returned by QueryChangedDiskAreas might be incorrect.You can use these PowerCLI commands to disable and then enable CBT without powering off the virtual machine. This can be useful when one or more of the disks of the virtual machine is extended past a 128Gb boundary. Example shown uses VM_Name as the $vm variable this should contain the name of the vm you are reconfiguring.
$vm="VM_Name"$vmtest = Get-vm $vm| get-view$vmConfigSpec = New-Object VMware.Vim.VirtualMachineConfigSpec$vmConfigSpec.changeTrackingEnabled = $false $vmtest.reconfigVM($vmConfigSpec) $vmConfigSpec.changeTrackingEnabled = $true $vmtest.reconfigVM($vmConfigSpec) Note : If you enable or disable CBT using PowerCLI or the vSphere API while the virtual machine is powered ON, the configuration change is saved but CBT tracking does not immediately initialize. To complete the CBT enablement and generate the required tracking files (-ctk.vmdk), the VM must undergo a stun/unstun cycle. You must perform one of the following actions immediately after enabling CBT on a live VM: