When attempting to protect a VM with Zerto Virtual Replication, an administrator may receive an error of the following type:
VM [vmname] disk [diskname].vmdk was associated with a different solution that is not compatible with Zerto Virtual Replication. Dissociate it in order to continue replication.
This error indicates that the VM was previously configured for replication with a different replication solution, and was not correctly dissociated from that solution. This solution article explains the steps necessary to verify that this is the case, and to make the VM compatible with Zerto Virtual Replication.
Note: starting with ZVR 3.5, the system will try to specify which application is associated to the disk in question, such as in the case of vSphere Replication with “Host Based Replication” (HBR) or VMware View with the “Content-Based Read Cache” (CBRC).
If a VM is still associated with vSphere Replication’s HBR, do the following to disable it:
- SSH to your ESXi host
- Identify the vmid of the VM in question with the following command:
vim-cmd vmsvc/getallvms | grep -i <VM name>
- Check the replication configuration for the vmid with the following command:
vim-cmd hbrsvc/vmreplica.getConfig <vmid>
- Disable replication with the following command:
vim-cmd hbrsvc/vmreplica.disable <vmid>
If a VM is still associated with VMware View’s CBRC, try the following three fixes (in order of intrusiveness):
Disable CBRC on this particular VM:
- Ensure the VM is powered off.
- Navigate to https://[ESXi IP]/mob.
- Navigate to ha-root-folder -> ha-datacenter -> ha-folder-vm.
- Obtain the host’s vmid for the VM in question.
- Browse https://[ESXi IP]/mob/?moid=ha-cbrc-manager.
- Press ConfigureDigest_Task.
- Set enabled to false.
- Fill in the host’s vmid (not vCenter’s vmid) in the spec section.
- Fill the device key (get it by opening vc mob, go to vm -> config -> hardware) in the spec section.
- Press invoke method.
- Invoke QueryDigestRuntimeStatus with VM id and device key to see if CBRC is enabled.
- Go to the backing info of the disk on the mob and verify that digestEnabled is false.
- Power on the VM.
*Note: to minimize downtime, if desired, it is sufficient to skip steps 1 and 13, and simply restart the VM after following the remaining steps.