high availability

While there is a reasonable amount of information about how HA works in vROps I have found there is still some confusion as to how HA actually works with vROps or rather what are the benefits and perhaps more importantly the cost for enabling the feature. HA is a great feature and in my opinion should be considered seriously with any deployment (where possible). Not only does HA protect your Master node (which essentially behaves as an index for your vROps cluster and if lost will render your cluster dead unless you have a working backup of your cluster) it will also allow your cluster to tolerate a data node failure.

One of the great new features included in vROps is High Availability, however when you look a little closer at how it works careful thought needs to go into whether you want to use it or not. I have had several discussions with my colleagues on the subject about whether you should or should not enable it in any given deployment of a vROps cluster. So the following are my thoughts and bullet points for you to consider when faced with same dilemma.

Now that the prerequisites for the IaaS layer have been completed, it’s time to move on to the actual installation of the IaaS components, starting with the database. We then move onto the first Web server, which also imports the ModelManagerData configuration to the database, populating the database with all of the info the IaaS layer needs out of the box. We then install the second Web server before moving on to the active Manager server.