"Operation canceled due to an unexpected error" when replicating VM's that use LWD Filters in Cloud Director Availability 4.x
search cancel

"Operation canceled due to an unexpected error" when replicating VM's that use LWD Filters in Cloud Director Availability 4.x

book

Article ID: 315025

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

Symptoms:

  • When attempting to replicate VM's it is failing with the following Error message:
Operation canceled due to an unexpected error
  • In the /opt/vmware/h4/replicator/log/replicator.log file on the source Replicator appliance, you see messages similar to:
2024-03-06 11:29:05.959 WARN- [UI-########-####-####-####-########069f-r305-2m-2Y-Di-71] [pc-task-monitor-2] c.v.h.c.e.ExceptionConversionService : Unable to convert exception. Using fallback exception instead.
com.vmware.vim.binding.vim. fault.ReplicationDiskConfigFault: The vSphere Replication configuration for disk with key 2,000 of the virtual machine has an issue: Replication not supported for disk type or backend.
...
  • In the /var/log/hostd.log file on the ESXi host where the source Virtual Machine is running, you see messages similar to:
2024-03-06T11:23:40.879z info hostd [2700094] [Originator@6876 sub-Solo. Vmomi opID-UI-########-####-####-####-########ea696-r483-rI-Vk-3k-dl-37-92-8f8e user-vpxuser: VSPHERE. LOCAL\Administrator] Activation finished; <<########-####-####-####-########81b0, <TCP '127.0.0.1: 8307'>, <TCP '127.0.0.1: 48748'>>, ha-hbr-manager, vim. HbrManager.retrieve ReplicationConfig>
2024-03-06T11:23:40.8792 verbose hostd [2700094] [Originator@6876 sub-Solo. Vmomi opID-UI-########-####-####-####-########ea696-r483-rI-Vk-3k-dl-37-92-8f8e user-vpxuser: VSPHERE. LOCAL\Administrator] Arg vm:
--> 'vim.VirtualMachine:101'
2024-03-06T11:23:40.8792 info hostd [2700094] [Originator@6876 sub-Solo. Vmomi opID-UI-########-####-####-####-########a696-1483-rI-Vk-3k-dl-37-92-8f8e user-vpxuser: VSPHERE. LOCAL\Administrator] Throw vim.fault.ReplicationVmConfigFault
2024-03-06T11:23:40.8792 info hostd [2700094] [Originator 6876 sub-Solo. Vmomi opID-UI-########-####-####-####-########a696-r483-rI-Vk-3k-dl-37-92-8f8e user-vpxuser: VSPHERE.LOCAL\Administrator] Result:
--> (vim.fault.ReplicationVmConfigFault) {
-->
--> reason "replication NotEnabled",
vmRef 'vim. VirtualMachine:101',
msg-"",
-->
2024-03-06T11:23:40.932z info hostd [2105275] [Originator@6876 sub-Vimsvc.TaskManager opID-UI-########-####-####-####-########ea696-r483-r1-vk-3k-dl-1a-0-8f8f user-vpxuser: VSPHERE.LOCAL\Administrator] Task Created: haTask--vim. HbrManager.enable Replication-13555636
2024-03-06T11:23:40.9322 error hostd [2105276] [Originator@6876 sub-Hbrsvc opID-UI-########-####-####-####-########a696-1483-rI-Vk-3k-dl-1a-0-8f8f user-vpxuser: VSPHERE.LOCAL\Administrator] VM is LWD protected can't replicate
2024-03-06T11:23:40.932Z error hostd [2105276] [Originator@6876 sub-Hbrave opID-UI-########-####-####-####-########a696-r483-rI-Vk-3k-dl-la-0-8181 user-vpxuser: VSPHERE.LOCAL\Administrator] Failed to configure replication for VM (id-101): Disk with replication-incompatible type specified (devKey-2000)
2024-03-06T11:23:40.932Z info hostd [2105276] [Originator@6876 sub-AdapterServer opID-UI-########-####-####-####-########a696-r483-rI-Vk-3k-dl-1a-0-8f8f user-vpxuser: VSPHERE. LOCAL\Administrator] AdapterServer caught exception; <<########-####-####-####-########81b0, <TCP '127.0.0.1: 8307'>, <TCP '127.0.0.1: 48748'>>, ha-hbr-manager, vim. HbrManager.enableReplication>, N3Vim5Fault26ReplicationDisk ConfigFault 9ExceptionE (Fault cause: vim.fault.ReplicationDiskConfigFault-->>
--> [context]zKq7AVICAgAAABAEVQEPaG9zdGQAANJCF2xpYn2tYWNvcmUuc28AAehnT2hvc3RkAAEO HQBkH10Ad6EdAG8o3QBta10AbB4cg115PBsaWJ2aW0tdHlwZXMuc28AATqcUgDMxy0AVAMUAAIRPWM7fQBsaWJwdGhyZWFkLnNvLjAABG3RDmxpYmMuc28uNgA-[/context]


Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware Cloud Director Availability 4.x

Cause

The issue occurs when there is a pre-existing LWD I/O filter being applied to the source Virtual Machine you at attempting to replicate via Cloud Director Availability. This filter can be applied on the Virtual Machine by third party backup tools.

Resolution

To resolve this issue remove the affected Virtual Machine from any third part backup or recovery tools that use LWD I/O filters before configuring it for replication via Cloud Director Availability.