vmware es ha

8/3/2019 Vmware Es HA

http://slidepdf.com/reader/full/vmware-es-ha 1/7

How to Configure VMware High Availability(VMHA)

Introduction

I am not biased to one virtualization solution or another but I know a great product and amazing features when I see them. VMwareESX Server and the VMware Infrastructure suite has a lot of amazing features that really “set the bar” for other virtualizationproducts. One of those features is VMware’s High Availability feature – dubbed VMHA.

When a physical server goes down or loses all network connectivity, VMHA steps in and migrates the virtual guest machines off of that server and onto another server. This way, the virtual machines can be up and running again in just the time that it takes them toreboot.

Home Articles & Tutorials

VMware ESX Articles

VMotion & DRS & High Availability

What VMware’s High Availability solution is and how to configure it. Published: Jan 27, 2009 Updated: Oct 01, 2009 Section: VMotion & DRS & High Availability Author: David Davis Rating: 4.4/5 - 32 Votes

of 7How to Configure VMware High Availability (VMHA)

30/10/2010http://www.virtualizationadmin.com/articles-tutorials/vmware-esx-articles/vmotion-drs-hi ...



Figure 1: VMware High Availability (VMHA) - Image Courtesy of VMware.com

This is a very powerful feature because it means that any operating system and appliance can have high availability just by runninginside the VMware Infrastructure.

There are a number of requirements to make this happen and there are both good and bad qualities of VMHA. I will cover all of thatand show you how to configure VMHA in this article.

Let’s get started.

What is required to make VMHA work?

There are a number of requirements that you will have to meet to make VMHA work. Those requirements are:

VMware Infrastructure Suite Standard or Enterprise (no you cannot do it with the free ESXi nor can you do it with theVMware Foundations Suite).

At least 2 ESX host systems. A shared SAN or NAS between the ESX Servers where the virtual machines will be stored. Keep in mind that with VMHA

the virtual disks for the VMs covered by VMHA never move. What happens when a host system fails is that the ownership of those virtual machines is transferred from the failed host to the new host.

CPU compatibility between the hosts. The easiest way to test this is to attempt a VMotion of a VM from one server to another

and see what happens. Here is what CPU incompatibility looks like when it fails:

Figure 2: CPU Incompatibility

If you cannot achieve CPU compatibility between hosts in the HA resource pool, then you will have to configure CPU Masking (seeVMworld: VMotion between Apples and Oranges).

Highly Recommended – to have VMware management network redundancy (at least two NICs associated with the VMwareport used for VMotion and iSCSI). If you do not have this, you will see:





Figure 3: Configuration issues because there is no VMware management network redundancy

What is great about VMHA?

Here are some of the great features of VMHA:

Provides high availability for all virtual machines at a low cost (compared to purchasing a HA solution on a per machinebasis).

Works for any OS that runs inside VMware ESX. That means that even if I create a Vyatta virtual router running inside ESXServer, that ESX Server is in a HA resource pool, and the server it is running on goes down, then that Vyatta virtual router OSwill migrate and have it reboot on the ESX host system.

VMHA is easy to configure. If you have the right equipment, licenses, and VMware Infrastructure already set up, you canconfigure VMHA in just a few minutes.

Works with DRS (distributed resource scheduler) such that when a VMs are going to be brought to other hosts in the resourcepool due to host failure, DRS is used to determine where that load should be placed and to balance that load.

What is “not so great” about VMHA?

Just like with any solution, there are some features of VMHA that are not as great. Those features are:

CPUs on each host must be compatible (almost exactly) or you will have to configure CPU masking on every virtual machine. Virtual machines that are on the host system that goes doem WILL have to be restarted. VMHA is unaware of the underlying applications on those VMs. That means that if the underlying application data is corrupt

from an application crash and server reboot, then even though the VM migrates and reboots from a crashed machine, theapplication still may be unusable (not that this is necessarily VMware’s fault).

How do I configure VMHA?

Configuration of VMHA is easy, just follow these steps:

Note:

The following assumes that you already have two ESX Server host systems, the VMware Infrastructure Suite (VI Suits), the CPUs onthe host systems are compatible, you have a shared storage system, and all licensing related to VMHA and the VMHA feature is inplace.

1. In the VI Client, Inventory View, Right-click on your datacenter and click on New Cluster.





Figure 4: Adding a New HA Cluster

2. This brings up the New Cluster Wizard. Give the Cluster a name and (assuming you are only creating a HA cluster), check theVMware HA cluster feature.

Figure 5: Naming the HA Cluster

3. Next, you will be given a chance to configure the HA options for this cluster. There is a lot to consider here – how many hostscan fail, if guests will be powered on if the proper amount of resources is not available, host isolation, restart priority, andvirtual machine monitoring. To learn more about these settings, please read the VMware 3.5 Documentation.





Figure 6: Configuring HA Options

4. Select the swapfile location – either with the VM on your shared storage or on the host. I recommend keeping the swapfilewith the VM on your shared storage.

5. And finally, you are shown the “ready to complete” screen where you can review what you are about to do and click Finish.

6. Once the HA cluster is created, you need to move ESX host systems into the cluster by clicking on them and dragging theminto the cluster. You can also move VMs to the cluster in the same way. Here are my results:

Figure 7: HA Cluster created with ESX Server hosts and VMs inside





7. At this point, you should click on the cluster to see if there are any configuration issues (as you see in Figure 3). Also, noticehow the cluster has its own tabs for Summary, Virtual Machines, Hosts, Resource Allocation, Performance, Tasks & Events,Alarms, and Permissions.

8. Even though I had configuration issues (no redundant management network), my VMHA cluster was still functional. To getaround the “insufficient resources to satisfy configured failover level for HA” error message when powering up a VM, Ichanged the HA configuration to “Allow VMs to be powered on even if they violate availability constraints”.

Let’s test it.

How do I know if VMHA worked?

To test VMHA, I had two low end Dell Servers in my cluster. I had one Windows Server 2008 system running on ESX host “esx4”.To perform a simple HA test, I rebooted host “esx4” without going into maintenance mode. This caused the Windows 2008 Server tomove from “esx4” to “esx3” and be rebooted. Here is the “before and after”:

Figure 8: Before causing the failure of server ESX4

Figure 9: After the failure of server ESX4 – proving the VMHA was successful

In this test, we saw that the Windows 2008 VM was moved from “esx4” to “esx3” when “esx4” we restarted.

Conclusion

In this article, you learned what VMware’s High Availability solution is and how to configure it. We started off with therequirements to use VMHA. From there, you saw what was good and what was not so good about VMHA. After showing you how toconfigure VMHA, I demonstrated exactly how it works in a real server failure. VMHA is really the leader when it comes tovirtualization high availability.

About David DavisDavid Davis is Director of Infrastructure at TrainSignal.com. He has a number of certifications including CCIE#9369, MCSE, CISSP,VCP & vExpert. Additionally, David has authored over three hundred articles and anumber of video training courses including Windows XP, Wireless Networking, Linux+ Administration, ISAServer, A+ Certification, Microsoft Virtual Server, VMware Server & Workstation, & VMware ESX Server.

Click here for David Davis's section.





Latest articles by David Davis

Powering up your VirtualBox Using VMware vSphere Storage Views What is VMware Guided Consolidation? Installing the Hyper-V Tools for Remote Management in Windows 7 5 things Microsoft must do to stay in the virtualization game

Related links

Set Your Desktop Free: Discover Benefits of IBM Virtual Client Solution IT Decision-Maker Perspective on Storage Solutions in Enterprise VMware Environment SAN/iQ: Enabling Technology for Effective VMware Deployments Charlotte County Finds An Ideal Business Continuity Solution Building A Virtual SAN Using VMware ESX Internal Storage

Receive all the latest articles by email!

Receive Real-Time & Monthly VirtualizationAdmin.com article updates in your mailbox. Enter your email below!Click for Real-Time sample & Monthly sample

Become a VirtualizationAdmin.com member!

Discuss all your Virtualization issues with other experts. Click here to join!

About Us : Email us : Product Submission Form : Advertising Information VirtualizationAdmin.com is in no way affiliated with Microsoft Corp. *Links are sponsored by advertisers.

Copyright © 2010 TechGenix Ltd. All rights reserved. Please read our Privacy Policy and Terms & Conditions.

EnterEmail


vmware es ha

Documents