vSphere Replication servers won't connect after implementing new custom certificates

Products

• VMware Live Recovery

Issue/Introduction

Symptoms:

• vSphere Replication add-on status shows disconnected.
• The administrator received the green success message after clicking 'Connect,' but the appliances remain disconnected.
• Reconnection and reconfiguration were successful.
• There are no errors in the Site Recovery UI, but replication cannot be configured or removed from the vSphere Replication add-on server.

Environment

vSphere Live Recovery (all versions)

Cause

The issue occurred due to two reasons:

1) The custom certificate was changed.

2) The virtual machine, which was configured for replication, was removed from the vCenter inventory before it was properly unregistered from the replication configuration.

 

Resolution

Steps to update VRMSDB with correct movalue and remove stale replication:

1) SSH into vsphere replication as admin and change to root using sudo su

2) cd /opt/vmware/hms/conf 

3) Get password using cat embedded_db.cfg 

4) Enter into VRMS DB ./opt/vmware/vpostgres/current/bin/psql -U vrmsdb

5) Get hbrserver movalue using SELECT movalue from hbrserverentity where hbrservername like 'VM_Name';

6) Get sourcesite movalue using SELECT movalue, vsrv_address from hmsserverentity;

7) Update the values using in secondarygroupentity using UPDATE secondarygroupentity set sourcesite_movalue = 'HMSSRV-xxxxx-xxxx-xxxx-xxxxx-xxxxx' WHERE hbrserver_movalue = 'HBRSRV-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx';

8) Remove stale replication . Refer to the document for stale replication removal https://broadcomcms-software-agent.wolkenservicedesk.com/wolken/esd/knowledge-base-view/view-kb-article?articleNumber=381353