VMware Cloud Community
tlaramie
Contributor
Contributor

Issues when deploying 'Additional Replication Server'

To identify possible WAN network traffic I'm deploying an additional VR server on a separate VLAN from the VRM server. Deployment through vCenter goes on with an issue and on first boot I'm able to connect the VRS and have it visible when setting up replication. Unfortunately when I enable replication from the protected to the recovery site I get the following vague error:

A runtime error occurred in the vSphere Replication Management Server. Exception details: 'Error getting local VC view'.

Cause:

Cannot complete login due to an incorrect user name or password.

I've checked the hms.log and hbrsvr.log but no further detail. After logging into the VRS and making some changes (setting the hostname to a resolvable FQDN, etc) and rebooting the server comes back but hbrsrv isn't listening on the usual ports (8123, 31031 + 44046). Attempting to reconnect the to the server also generates a new error :


A generic error occurred in the vSphere Replication Management Server. Exception details: 'org.apache.http.conn.HttpHostConnectException: Connection to https://10.128.18.111:8123 refused'.

In the past I've seen something similar which caused the VMWare Engineers to throw in the towel and tell me to re-install the VRMS appliance from scratch. I don't have that luxury this time as I'm in the midst of site migration and can't risk the time it'll take to reseed the data (plus the other VRS is running without problems).

Has anyone ever been able to resolve this or at least identify what's causing the hbrsrv to fail on the VRS side of things? Like I said above I _really_ don't want to have to re-install everything since it seems like this sort of problem crops up more then I'd like.

Reply
0 Kudos
2 Replies
squebel
Contributor
Contributor

Did you ever find a solution to your problem?

Reply
0 Kudos
virtualg_uk
Leadership
Leadership

Check the time is correct on your ESXi hosts, the vSphere Replication Servers and the vCenter server.

If it is out by more than even a few seconds then it can throw errors of this kind. Post back if you need assistance in changing the time etc.


Graham | User Moderator | https://virtualg.uk
Reply
0 Kudos