Running Vcenter 6.7 cluster and HA with 4 ESXI hosts
Today my NFS storage crashed and my VCSA primary was on that datastore.
The Data on the drive is good I can access the files from my computer.
I see a lot of .lck files in the folders of the VM's
1. It continues to try to migrate and fails.
2. How can I recover the Primary VCSA?
The Witness and Passive VCSA are still operational.
Any thoughts on what I can do?
Thank you
Tom
One way to do it is to break the cluster, have a standalone VC and the reconfigure it.
Recovering from Isolated vCenter HA Nodes
Also, look at this link : Resolving Failover Failures
Hi,
Login on any ESXi server where datastore is accessible and import vm from storage location.
My active node is down can not start it at all.
From vcenter I can not access any of the files on the datastore where this vm resided
I only can access them from my computer.
Can I restore just the active node?
I disable Ha on the vcenter
So how can I restore my active node?
why restore ? if the active node goes down the witness initiated a failover to the passive, so the passive is the new active.
just look if your vcsa with "-passive" in the name has the active role. if so just destroy ha and reenable it
Bewe
Yes I understand that when the active node goes down the witness triggers a failover to the passive Node which is what happened.
My question is how do I rebuild the active node VM?
Currently the active node that failed has been removed from inventory because it was on a corrupt datastore.
I need to know how to rebuld that VM
currently I only have the witness and passive nodes up and running
need to create the third Node
the error on vcenter is
Center HA cluster has lost a node. Verify if the Passive node with IP address 10.14.10.15 is up and reachable.
Thanks
Tom
and ? have you checked that the passive 10.14.10.15 is accessible ?
are you able to login to vcenter although the old active is lost ? that means that the passive is now the active one
just destroy vcha (with deletion of witness) and reconfigure vcha.
you dont need to recover the vm - the deploy process creates all necessary vm for you
I had it before so with me I created a new dir and moved every .lck to it, then go ahead and power on your VM
insane additional step after powering the primary on, I destroyed VCHA and rebuild it again