VMotion fails for Virtual Machine protected by Veeam CDP

Products

• VMware vCenter Server

Issue/Introduction

A Veeam protected VM may fail to migrate and hang when migrating between ESXi hosts. 

Vmware.log will have an entry related to disconnecting CBT similar to the one found below.  (located in the VM folder on it's respective datastore - /vmfs/volumes/<Datastore UUID>/<vm-name>)

YYYY-MM-DDTHH:MM:SS.###Z In(05) vmx - MigrateSetState: Transitioning from state MIGRATE_TO_VMX_PREPARING (2) to MIGRATE_TO_VMX_PRECOPY (3).
YYYY-MM-DDTHH:MM:SS.###Z In(05) vcpu-0 - MigratePreCopyStartForHWMMUTreeInVMM: numPages=8388608 numVcpus=8 sharedBitmapSizeInPages=1 endBPN=0x4000800000 maxTraceable=10240
YYYY-MM-DDTHH:MM:SS.###Z In(05) vcpu-0 - MigrateSetState: Transitioning from state MIGRATE_TO_VMX_PRECOPY (3) to MIGRATE_TO_VMX_CHECKPT (4).
...
YYYY-MM-DDTHH:MM:SS.###Z In(05) vcpu-0 - DISKLIB-CBT   : Shutting down change tracking for untracked fid 3284715.
YYYY-MM-DDTHH:MM:SS.###Z In(05) vcpu-0 - DISKLIB-CBT   : Successfully disconnected CBT node.

The vmware.log entry for the destination VM shows similar timeout warnings:

YYYY-MM-DDTHH:MM:SS.###Z In(05) vmx - MigrateSetState: Transitioning from state MIGRATE_FROM_VMX_WAITING (9) to MIGRATE_FROM_VMX_PRECOPY (10).
YYYY-MM-DDTHH:MM:SS.###Z In(05) worker-####### - MigrateBusMemPrealloc: BusMem preallocation begins.
YYYY-MM-DDTHH:MM:SS.###Z In(05) worker-####### - MigrateBusMemPrealloc: BusMem preallocation completes.
YYYY-MM-DDTHH:MM:SS.###Z In(05) vmx - MigrateWaitForData: Waited for 142.78 seconds.
YYYY-MM-DDTHH:MM:SS.###Z Wa(03) vmx - Migrate: timed out waiting for data from the source.

 

One or more VMDKs for the VM contain the following values:

ddb.iofilters = "veecdp"
ddb.longContentID = "#############################"
ddb.sidecars = "veecdp_1,###########-####-################.vmfd"

veedcp.log logs indicate a WorkGroup wait entry for the vmdk  (Located at /var/run/log/veedcp.log)

YYYY-MM-DDTHH:MM:SS In(158) veecdp[2107493]: [0002107809] 495 (I) {########-####-####-####-############} [########-####-####-####-############] [Transceiver] [DAT] Destroying, self: 0xf4e40e4650
YYYY-MM-DDTHH:MM:SS Er(155) veecdp[2107493]: [0002107809] 495 (E) [Timer] Failed to remove timer, this: 0xf48db130e8, status 'Object not found'
YYYY-MM-DDTHH:MM:SS In(158) veecdp[2107493]: [0002107809] 495 (I) [WorkGroup] WorkGroup wait started, self: 0xf48da9b5f0

However,  the finish and destroy logs below will not be generated:

YYYY-MM-DDTHH:MM:SS In(158) veecdp[2107493]: [0002107809] 495 (I) [WorkGroup] WorkGroup wait finished, self: 0xf48da9b490
YYYY-MM-DDTHH:MM:SS In(158) veecdp[2107493]: [0002107809] 495 (I) [WorkGroup] WorkGroup destroying, self: 0xf48da9b490

Environment

ESXi 7.X
ESXi 8.X

Resolution

Please engage Veeam Support for additional assistance.