Sometimes Data Protector cannot enable CBT for a certain Virtual Machine.
Then we will probably see an error message like this in the session log:
[Major] From: VEPALIB_VMWARE@myserver "/mydatacenter" Time: 01/01/2016 00:01:01
Virtual Machine 'test': Could not enable changed block tracking ...
This could be caused by this Virtual Machine having existing user snapshots which prevent CBT from being enabled.
If there are no snapshots, or the issue persists after deleting them. We can try to manually enable CBT by following this VMware KB:
If CBT cannot be enabled by following the above KB, then we should contact VMware support for help.