Changing in VMware HA with vSphere 5.x

VMware is a great virtualization solution but since the first version the High Availability feature had a weakness that I never liked.

A vSphere 4.x cluster for example use a primary/secondary node architecture: the first 5 hosts that join the VMware HA cluster are automatically selected as primary nodes.  All the others are automatically selected as secondary nodes.

That means that no matter how many nodes your cluster has, if all the 5 primary nodes are down, your entire virtualization environment is unusable.

Microsoft Hyper-V doesn’t have this limitation because uses a classic Windows Clustering feature that uses node and disk majority.

Now with vSphere 5.x the HA feature has changed to avoid this behaviour.

The concept of master and slave still exist but it’s dynamically assigned so if the master fall down, a new master role will be assigned to a slave.

This great article can explain in depth the changes made to the vShpere 5.x architecture.

http://www.yellow-bricks.com/vmware-high-availability-deepdiv/

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s