I was just listening to “BC3197 – High Availability – Internals and Best Practices” by Marc Sevigny. Marc is one of the HA engineers and is also my primary source of information when it comes to HA. Although most information can be found on the internet it’s always good to verify your understanding with the people who actually wrote it.
During the session Marc explains, and I’ve written about in this article, that when a dual host failure occurs the global startup order is not taking into account. The startup order will be processed per host with the current version. In other words “Host a” first with taking startup order into account and then “Host B” with taking startup order into account.
During the session however Marc revealed that in a future version of HA global startup settings(Cluster based) will be taken into account for any number of host failures! Great stuff, another thing to mention is that they are also looking into an option which would enable you to pick your primary hosts. For blade environment this will be really useful. Thanks Marc for the insights,
Bouke Groenescheij says
This is indeed great progress! I’m just wondering – when would HA monitor services status inside a VM?
Free Avatars says
Good read. Like your blog design too.
Marc Sevigny says
Note that the global start up order (based on VM priorities) now works for multiple (near) simultaneous host failures in vCenter 4.1. All hosts that fail within a 15-second window will have their failed VMs considered and sorted by priority before making placement decisions.
M-A Verpaelst says
bonjour Marc, es-tu la personne que je connaît? (Stoke) 😉 si oui récrit moi à mon mail..:) merci 🙂
Marc Sevigny says
Je ne pense pas que c’était moi, puisque je ne sais pas ce que Stoke est!