This post is part of a series on deploying Highly Available vCenter and Platform Services Controllers.
Part 5: vCenter HA: Deploy vCenter
Part 7: vCenter HA: License vCenter
Part 11: vCenter HA: Configure vCenter HA
Part 12+: Advanced Tasks (Coming soon)
Now we get to the best part about 6.5 and that is HA vCenter. You can do this with the Windows installation and Microsoft Failover Clustering, but thats just a tad more difficult. The appliances have made things so much easier and it has been a long time coming. I have always been weary of the appliances because of more limited functionality, but as of this release, I don’t know that the appliances can’t do anything that the Windows version can do. Fully managed Update Manager also.
So there are a couple things to note here. vCenter HA doesn’t work with Datastore Clusters. So I propose that you create three specific LUNs with enough space for vCenter+overhead+snapshot+10%. Nobody likes running out of space. Another thing that I haven’t seen other people highlight is that you don’t need to do load balancing or a VIP. The appliances are Active/Passive and a vCenter failover will assume the name and IP address. Here is a bulleted list of requirements/recommendations.
- three Datastores for vCenter appliances
- Distributed Port Group for a separate subnet for HA traffic
- three IPs for HA traffic on a separate subnet: one for vCenter primary, one for failover node, one for witness
That is pretty much all you need. The first thing you need to do is create the port group for HA traffic.
Just follow the screenshots or return to the previous post for port group creation.
Now you have an HA port group.
Click the Home button at the top to return to the home page.