The vReplication node is not working, and vSphere Replication is showing as disconnected.
search cancel

The vReplication node is not working, and vSphere Replication is showing as disconnected.

book

Article ID: 396128

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:

vSphere Replication Management Server could not establish a connection to the remote vSphere Replication Management Server at 'VR_ServerName'

vSphere Replication Management Server could not establish a connection to the vSphere Replication Server at 127.0.0.1:8123

HTTP failure response for https://VR_FQDN.com/plugins/com.vmware.drui.plugin~8.6.0.20554592~-1118885595/VR_FQDN.com-443/drplugin/requestHandlers/getIsCloudFlag: 500 OK

Environment

vSphere Live recovery (all versions)

Cause

If a vSphere Replication server is moved between vCenter instances, reconfiguration may fail or the replication server may remain in a disconnected state.

This occurs because the VRMSDB retains the UUID of the previously associated vCenter. When attempting to reconfigure, a conflict arises between the old and new vCenter UUIDs stored in the database, resulting in a failure.

Resolution

1) Unregister vSphere Replication Appliance at source and destination site. Refer the document for unregistering vsphere replication Unregister and Remove a vSphere Replication Server

2) Power off the appliance from vcenter inventory. 

3) Deploy a new vsphere replication appliance at source and destination site. Refer the document for deploying vsphere replication appliance Deploy the vSphere Replication Virtual Appliance

Refer the document for registering vsphere replication appliance  Configure the vSphere Replication Appliance to Connect to a vCenter Server instance

Refer the document for pairing the sites.Configure vSphere Replication Connections

Refer the document creating a replication using the seeds.Replicating Virtual Machines Using Replication Seeds