Failover Clustering and Network Load Balancing Team Blog
Hi Cluster Fans,
One of the Clustering and High Availability team’s Senior Program Managers, Steven Ekren, recently published an article in TechNet Magazine on Virtualization: Achieving High Availability for Hyper-V (http://technet.microsoft.com/en-us/magazine/cc837977.aspx). As one of Microsoft’s leading experts in HA for Hyper-V, Steven has provided some great information which both beginners and pros can appreciate.
Here’s an overview:
Server virtualization is poised to make a significant impact in enterprise IT departments, and Hyper-V with Windows Server 2008 can make it a reality. The consolidation of servers onto fewer physical machines has huge advantages in resource and cost savings, but two key factors need to be considered during the planning process. Users have increasing expectations regarding the availability of their software, including both line-of-business (LOB) applications and tools such as messaging and collaboration platforms. Furthermore, problems or failure on servers can have a significantly greater impact on operations. Windows Server 2008 and Hyper-V provide solutions that can be implemented to provide high availability (HA) of virtual machines (VMs) as well as to the workloads being hosted inside the VMs.
We hope you enjoy this article!
The Clustering and High Availability team
PingBack from http://www.easycoded.com/virtualization-achieving-high-availability-for-hyper-v/
PingBack from http://blog.a-foton.ru/index.php/2008/10/01/virtualization-achieving-high-availability-for-hyper-v/
Now that I have Hyper-V clustered and failing over with no issues I'm wondering what happens when my iSCSI attached storage device needs to reboot. Will the cluster recover with no intervention or do I need to make sure that all clustered virtual computers are shut down before the attached storage is taken off line for a reboot?
I would put your VM in a "Saved" state, that way when your storage comes back online you can simply start your VM from where you left off, rather than rebooting the entire VM.
If you want to eliminate your iSCSI array as a single point of failure, you may want to look at my company's Hyper-V replication solution, DataKeeper. It will keep your VMs in sync across disparate storage arrays, and integrates directly with WSFC allowing you to move VMs across different servers AND different storage.
Here is a blog post that describes the solution and has a link to a video demonstration.
David Bermingham, MCSE
Director of Product Management