Note: Before re-registering the service, validate these:
- NTP (System Time synchronization)
- DNS records and shortnames
- Also, ensure you populate the VC/Lookup service address along with the FQDN on the VR server's /etc/hosts.
To work around this issue, use any one of these options:
- Redeploy the vSphere Replication appliance and configure all replications. If possible, reuse the existing .vmdk files as initial copies.
- Power off the old vSphere Replication appliances.
- Remove any temporary hbr* files from the target datastore folders.
- Deploy new vSphere Replication appliances and connect the sites.
- Configure all replications, reusing the existing replica .vmdk files as initial copies.
- If you cannot redeploy the vSphere Replication appliance, use the VAMI to connect vSphere Replication to the original vCenter Server instance:
- Reconnect the ESXi host to vCenter Server.
- Connect to the VAMI of the vSphere Replication server at https://vr_server_address:5480.
- Select the Configuration tab.
- Type username:password@vcenter_server_address in vCenter Server Address.
Where username and password are credentials of the vCenter Server administrator.
- Type the correct managed object id of the appliance VM in ApplianceVM MO value. Use the vCenter Server MOB to obtain the appliance id.
- Click Save and Restart Service.
If you use the VAMI solution, you must repeat the steps each time that you change the vSphere Replication certificate.