What is VMHA?
It is a High Availability package for VMware ESX 2.x,
It supports when one ESX host is dies, another ESX member will Take-over and Power-on all VM in 3 minute.
VMHA discussion In VMware Communities
How it works?
It detect the heartbeat between 2 ESX member and use ESX functions to control vm status.
View Demo
Benefits:
For the most mission critical applications high availability, we use middle-ware
such as Microsoft and Veritas clustering software to bind two redundant servers into a hot-standby pair.
VMware supports 3 types for Clustering:
- Cluster in a Box
- Cluster Across Boxes
- Physical to Virtual Clustering
There are using same clustering software as physical to physical machine clustering.
Thus it reduced Hardware cost allows implementation of HA,
but it still must at least double licenses for OS and Application.
The VMHA is a Physical ESX level cluster, it bind two redundant ESX servers into a hot-standby pair.
When ESX Server 1 is down, the ESX Server 2 will take-over all VMs on ESX Server1.
You only spend the VMs Power-on time.
Download:
Free for Trial, download ONIX-VMHA 0.9 beta version from here.
Document:
ONIX-VMHA Installation Guide (HTML | PDF)
Feedback:
If you have any questions about this program or have it up and running, we would like to hear from you:
please send e-mail to cmliu86@gmail.com

3 comments:
Hi there,
Quick question VMHA is currently on BETA…
When it becomes properly available – will it be open-source or for a fee…
Regards
Mike
Hi,
I've come across your site and I was interested in your program. I was wondering if it's possible using your program to only bring up a select number of virtual machines. Like say I only wanted to bring up the production servers but not all the testing/development servers. Would that be possible?
Kevin Margulieux
L-3 Communications
Hello,
we would like to use your VMHA Tool for securing our ESX Servers. We made
some initial testing with the Software and have some questions.
1. is it normal that from shutting down one node until the first Heartbeat
detection it takes about 2 Minutes ? Is there some way to speed this up ?
2. From the first detection of the quorum timeout until the takeover
process it takes about 10-15 minutes. is this behaviour intended ? Is
there some
way to speed this up ? (Here i attached the output of the vmha.log)
2006/1/5 10:39:54: [HeartBeat] HeartBeat no response for 1 times.
2006/1/5 10:39:54: [HeartBeat]
3. Are there other implementations of takeover Scripts like yours ?
Thank you in advance for your answer !
Mit freundlichen Grüssen,
kind regards,
Markus Löffler
System-Engineer (CCEA - CNE - VCP)
KUMAtronik Systemhaus GmbH
Sedanstraße 10
89077 Ulm
Tel: +49(0)731 935 10 52
Fax: +49(0)731 935 10 23
http://www.kumagroup.de
Post a Comment