VCloud Director Vms and VSE systems with Change Block Track

[DaxUK]

Veeam B&R: 5.02.230
Vcloud DIrector: 1.01

Hi,

We are having an issue with some Vcloud Director(VCD) Provisioned VM's and Changed block tracking.

Firstly, some VCD provisioned systems have the following issue:

Verifying changed block tracking...
Disk "Hard disk 1" has incorrect changed block tracking configuration.

Backing up object "xxxxxxx"

One or more VM disks have incorrect changed block tracking configuration. To resolve this, open VMware vSphere Client, right-click the VM, choose Edit Settings, Options tab, select General, click Configuration Parameters, and set all entries with ‘ctkEnabled’ substring to false. Veeam Backup will then automatically re-enable changed block tracking with the correct settings during the next job run.

Now I know the easy fix for this but we do not want to have to fix this for every newly VCD provisoned system, is there a way to fix this in the long term?

Secondly, We are provisioning some Vshield Edge(VSE) Devices using VCD we are hitting this issues on all the provisioned VSE's

Enabling changed block tracking...
SetVmChangeTracking failed, vmRef "xxx", changeTrackingEnabled "True"
The method is disabled by 'VCD'

Has anyone seen this before?

Should I just disable Change Block Tracking on all these jobs?

Regards
Dax

[Vitaliy S.]

Hello Dax,

Yes, in order to remove that warning message you may want to disable CBT for these VMs completely, however I'm not sure your issue has anything in common with vCloud Director, as processing of VMware vCloud Director provisioned virtual machines should be supported, based on our sticky F.A.Q. topic.

Thanks.

[Gostev]

First issue definitely has nothing to deal with vCD, and there are plenty of topics about it here already.
Second issue looks to be vCD specific that we did not see because of not having VSE devices in our lab.
Thanks.