The VM failed to complete the reprotect operation following a successful failover

Products

• VMware Live Recovery

Issue/Introduction

Symptoms:

vSphere Replication failed with the error: "No connection to VR server."

Environment

vSphere Live Recovery (all version)

 

Cause

The issue occurred because isolated clusters and hosts were not excluded from vSphere Replication using the VR.disallowed tag. As a result, during the reprotect operation, vSphere Replication attempted to communicate with these unreachable resources, leading to replication job failures.

Resolution

1) Verify Host Connectivity : Ensure that vSphere Replication can establish connectivity with all ESXi hosts in the inventory.

2) Exclude Isolated Hosts (if needed) : Apply the com.vmware.vr.disallowedHost tag to hosts that should not be used by vSphere Replication. Refer to the article for instructions on adding the tag to ESXi hosts Exclude hosts from registration in vSphere Replication

3) Cleanup VRMS Database. Remove stale host entries associated with the disallowed tag from the VRMS database using sqlite3 /etc/vmware/hbrsrv.*.db "DELETE FROM HostInfo;". Refer to the document for HostInfo cleanup vSphere Replication Appliance trying to register system under 'Replication Servers' that is not an appliance/ESXi host.

4) Reboot the vSphere Replication Appliance.