Vcenter Crash, then restore and now "can not find vsphere has master"

[marinador]

Good afternoon,

A few days ago at work we had problems with the server VCenter and to restore it from a previous copy (since then machine names have been changed and new machines have been created) is giving us the problems that you can see in the capture "can not find vsphere has master agent 5.5 " and others problems ... According to what I have researched in the forums of VMWare, the solution is to disconnect the host from the vcenter and reconnect them.

Can you tell me how to proceed with this error and if the fact of disconnecting the host from the web client of the vcenter and reconnecting it supposes the loss of data, the shutdown of the machine in service or something similar?

thank you very much, greetings

[rcporto]

Did you try disable vSphere HA on cluster and enable it again? And when you say machine names changed, if you talking about the vSphere ESXi hosts, are the DNS records reflecting the new names?

[marinador]

As for the names I mean that there are virtual machines that changed their name and new virtual machines created since the last copy of the Vcenter that accessing the ips of the ESXs themselves with the Vsphere Client but they are not seen in the Vcenter, also when I try to open a machine from the Vcnter web via Launch console it does not leave me and the following error comes out: "Unable to connect to the MKS: vim.fault.NoHost".

As for the vSphere HA, I leave you capturing the options as they are in the datacenter.

Thanks for your help!

[rcporto]

The vSphere HA is enable, try first disable the vSphere HA... then disconnect the host from vCenter, which do not require shutdown the VMs, reconnect the hosts and then enable vSphere HA again.

[marinador]

You mean disconnect as you see in the capture?

[rcporto · Accepted solution]

Yes, see: Disconnect a Managed Host in the vSphere Web Client

[marinador]

Thank you very much for your help, it has been solved!