The first patch to vSphere 6.5 was released last week. You can find the release notes here
That means that you may be looking to patch your vCenter HA enabled vCenter Server Appliance(s).
Continue reading “Patching/Updating a VCHA enabled vCenter Server Appliance”
When VCHA is enabled, a new OS user “vcha” is created and used for the file based replication.
This morning I experienced an issue on one of my VCHA setups (but not the other) where replication was failing when I arrived into the office.
Update 23/01/2017 – This is a real issue and not a once off. VMware Engineering are aware.
I’ve been playing around with VCHA and had been taking snapshots and have encountered some issues using snapshots on a VCHA enabled VCSA 6.5
You need to exercise caution when using snapshots on a VCSA that is enabled for VCHA.
Important: This is only when snapshot tasks are being done to the VCSA 6.5 VM. For all other VMs in your inventory there is no issue.
This includes taking snapshots of the current Active, reverting to snapshots of the current Active and deleting snapshots of the current Active.
For any and all of those tasks, ensure that the VCHA Cluster is in “Disabled” mode.
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:
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.
Continue reading “vSphere 6.5 Feature Preview: vCenter High Availability”
have you tried reinstalling? 