Word of warning: When you get to vSphere 6.5, your vCenter Servers are stuck to whatever PSC Site they are currently located in!
This post should hopefully help you understand what is and what is not protected by VCHA and also what to expect depending on the situation.
For more on VCHA please see my previous posts:
There are a few gotcha’s and known issues that I have found with vCenter HA. Hopefully the following will be of use and avoid the need to engage VMware Support to resolve.
For more on VCHA please see my previous post which also includes short videos of both deployment methods.
One of the most anticipated features of vSphere 6.5 is native high availability for vCenter Server. No additional product like vCenter Server Heartbeat or no third party feature like MSCS/WFCS is needed.
The first thing to point out is that this feature is exclusive for the vCenter Server Appliance 6.5.
Windows vCenter Server 6.5 will still support MSCS/WFCS to provide high availability.
The vCenter Server Appliance has come a long way from it’s first iteration way back with vSphere 5.0. A moment of silence for the VCSA 5.0 with embedded DB2 database.
With the vSphere 6.5 release, the vCenter Server Appliance not only gains 100% parity with it’s Windows counterpart, but actually now exceeds it with some exclusive features.
You can interpret the fact that the VCSA is now getting exclusive features however you want to.
Please don’t ask me “Is the Windows vCenter going away?” – because I honestly don’t know the answer.