RecoverPoint for VMs: Protecting Shared Disk VMs into a New or Existing Consistency Group Stays Disabled and Does Not Start Initialization
Summary: Protecting Shared Disk Virtual Machines into a new or existing Consistency Group(CG) succeeds and group is created but it stays in a disabled state.
Symptoms
The wizard for protecting the VMs ends successfully, the Virtual Machines are added but replication does not start.
In vSphere tasks, multiple failures in the Source VMs site for reconfiguring the VM. The tasks are from the user configured for RecoverPoint Cluster. Task failures show the cause "The operation is not supported on the object."
Checking RecoverPoint for VM site control log of Source VMs in vi_connector.log, shows the following Exception:
2022-05-23 11:31:47,073 [pool-6-thread-6] (ActionInfo.java:61) ERROR - Action failed: Task:task-275217 @ https://1.1.1.1:443/sdk state: 'Error', error Message: The operation is not supported on the object. 2022-05-23 11:31:47,074 [pool-6-thread-6] (BaseAction.java:42) ERROR - ReconfigManagedVMAction Failed. com.emc.recoverpoint.connectors.actions.infra.ActionFailedException: The operation is not supported on the object. at com.emc.recoverpoint.connectors.actions.infra.ActionFailedException.createException(ActionFailedException.java:31) ~[vsphere_actions.jar:?] at com.emc.recoverpoint.connectors.actions.infra.ActionInfo.isCompleted(ActionInfo.java:67) ~[vsphere_actions.jar:?] at com.emc.recoverpoint.connectors.actions.infra.ActionInfo.verifySuccess(ActionInfo.java:129) ~[vsphere_actions.jar:?]
In the vCenter vpxd log file, we trace the task ID above to figure out more insight on why the task is not supported. In here, it mentions the following reason:
2022-05-23T11:31:45.068Z info vpxd[06722] [Originator@6876 sub=vpxLro opID=5ce3ac78] [VpxLRO] -- BEGIN task-275216 -- vm-70 -- vim.VirtualMachine.reconfigure -- 522b7638-f4de-90e1-79c7-d569f57774f3(52c51b4a-9449-b844-e60e-b7949e783e1f)
2022-05-23T11:31:45.072Z info vpxd[06722] [Originator@6876 sub=vpxLro opID=5ce3ac78-01] [VpxLRO] -- BEGIN lro-99207295 -- vm-70 -- vim.VirtualMachine.reconfigure -- 522b7638-f4de-90e1-79c7-d569f57774f3(52c51b4a-9449-b844-e60e-b7949e783e1f)
2022-05-23T11:31:45.075Z info vpxd[12910] [Originator@6876 sub=vpxLro opID=3ff079f1] [VpxLRO] -- BEGIN task-275217 -- vm-69 -- vim.VirtualMachine.reconfigure -- 522b7638-f4de-90e1-79c7-d569f57774f3(52c51b4a-9449-b844-e60e-b7949e783e1f)
2022-05-23T11:31:45.075Z info vpxd[06722] [Originator@6876 sub=VmCheck opID=5ce3ac78-01] CompatCheck results: (vim.vm.check.Result) [
--> (vim.vm.check.Result) {
--> vm = 'vim.VirtualMachine:a4383d50-c0fa-4b69-aedb-d0d21ee58a61:vm-70',
--> host = 'vim.HostSystem:a4383d50-c0fa-4b69-aedb-d0d21ee58a61:host-21',
--> error = (vmodl.MethodFault) [
--> (vmodl.fault.NotSupported) {
--> faultMessage = (vmodl.LocalizableMessage) [
--> (vmodl.LocalizableMessage) {
--> key = "com.vmware.vim.vpxd.vmcheck.cbtAndMultiwriterVmNotSupported",
--> }
--> ],
--> msg = ""
--> }
--> ],
--> }
--> ]
To confirm if Changed Block Tracking (CBT) is enabled, follow the steps in the VMware KB article: https://kb.vmware.com/s/article/1020128
Cause
Resolution
Disable the CBT option if there is no specific need for it. To disable the CBT option, follow the VMware KB article: https://kb.vmware.com/s/article/1020128