Reprotect fails with the error: VR synchronization failed for VRM group: Remote group is in passive replication state
book
Article ID: 330788
calendar_today
Updated On:
Products
VMware Live Recovery
Issue/Introduction
Symptoms: When running vSphere Replication, you experience these symptoms:
Reprotect operations fail
The vSphere Web Client produces an error similar to:
VR synchronization failed for VRM group test-group-clone-vr. Remote group 'GID-a4d0ec17-78c6-454f-9cc9-fbd37e544fff' is in passive replication state.
In the vmkernel.log file, located at /var/log/, from the ESXi host running the virtual machine at the Disaster Recovery (DR) site, you see entries similar to:
YYYY-MM-DD TIME.629Z cpu9:3108530)Hbr: 1064: Failed to find NetWorker for groupID=GID-c49da1ea-f4b1-4546-bf82-c52539d1cc89
YYYY-MM-DD TIME.642Z cpu20:8212)WARNING: Hbr: 4322: Failed to establish connection to [10.100.10.95]:31031(groupID=GID-c49da1ea-f4b1-4546-bf82-c52539d1cc89): Timeout
Cause
This issue occurs if synchronization between the DR site to the Primary site does not occur or is blocked.
Resolution
To allow synchronization to occur, ensure that outbound traffic from port 31031 on the ESXi host at the DR site is unobstructed. After the port is correctly configured synchronization data should flow as normal.
For more information on port requirements in vSphere Replication, see: