Achieving High Availability with Windows 2008 R2 HyperV André Keartland Inobits Consulting VIR303 Agenda Positioning virtualization and high availability Host vs guest clustering Quick Migration and Live Migration ID: 773214
Download Presentation The PPT/PDF document "Achieving High Availability with Windows..." is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Achieving High Availability with Windows 2008 R2 Hyper-V André Keartland Inobits Consulting VIR303
Agenda Positioning virtualization and high availability Host vs. guest clustering Quick Migration and Live MigrationCapacity planning for Hyper-V HAVirtual Machine Manager and clustering
Virtualization and High Availability Traditional Non-Virtualized Environment Downtime is bad, but affects only one workload Virtualized Environment Value of the physical server goes up Downtime is far worse because multiple workloads are affected Virtualization and High-Availability Go Hand in Hand
Virtualization Takes Business Continuity to the Next Level More options for effective disaster recovery Companies previously unable to afford disaster recovery can now implement Companies can cost justify additional applications According to a March, 2009 study by Enterprise Resource Group, 31% of businesses surveyed said DR will be their main driver for Virtualization in 2009
Business Continuity with Virtualization Adding virtualization to your business continuity plan will reduce costs and minimize business downtime by: Increasing the availability of server infrastructure Affordably extend protection to more applications Minimizing time and resources needed to support infrastructure Disaster Recovery High Availability Backup and Recovery Business Continuity Secondary Site Primary Site Storage Array Storage Array Disaster Recovery Backup/Recovery Backup/Recovery Quick/Live Migration VHD Shared Storage Backup/Recovery Clustering
High-availability infrastructure is not just for availability … Host servicing Load management Power management
Agenda Positioning virtualization and high availability Host vs. guest clustering Quick Migration and Live MigrationCapacity planning for Hyper-V HAVirtual Machine Manager and clustering
Server Virtualization Failover Clustering Support: Two models Host to Host Cluster storage SAN or iSCSI connection Child to Child Cluster storage iSCSI connection
Cluster storage SAN or iSCSI connection Server Virtualization Failover Clustering Support: Host to Host Move Virtual Machine from Host to Host VM is the failover unit (resource group) Can fail over all or single VMs Each VM on storage accessible by all hosts (SAN/iSCSI) Hyper-V: Host server must be Windows Server 2008 Enterprise or Datacenter Edition Child partitions and applications do not need to be cluster-capable Reduces scheduled and unscheduled downtime
Cluster storage iSCSI connection Server Virtualization Failover Clustering Support: Child to Child AKA Guest Clustering Cluster VMs on same or different hosts VM (Guest) is the cluster node Application in guest is a resource group Application is cluster capable (cluster-aware or Generic ) OS is cluster capable (Windows 2000/2003/3008 Enterprise or Datacenter) Protects against failure of Child If VM or application fails, then failover to other VM on same host or on another host Requires iSCSI or SAN storage on the host
Host vs. Guest Clustering Host Clustering Guest Clustering Cluster physical machines Cluster virtual machines Virtual machine is monitored for health Application is monitored for health Guards against host OS and hardware failures Guards against guest OS and application failures Application running on virtual machine does not need to be cluster aware Application running on virtual machine needs to be cluster aware
Agenda Positioning virtualization and high availability Host vs. guest clustering Quick Migration and Live MigrationCapacity planning for Hyper-V HAVirtual Machine Manager and clustering
Microsoft Hyper-V Quick Migration Quick Migration requires failover clustering between the hosts Failover cluster feature Used when virtual machine fails over from one host to another in cluster.Requires Windows Server 2008 Enterprise or Datacenter Edition on host Requires shared storage for virtual machine dataSystem Center virtual Machine Manager is not required but it can use Quick Migration
Hyper-V Quick Migration Fundamentals Planned Downtime Steps: Initiate failover Save state Save entire virtual machine state Suspend virtual machine Move virtual machine Move storage connectivity from origin to destination host Restore state and Run Restore virtual machine and run Shared Storage VHD Memory state Memory state Memory state
Hyper-V Quick Migration Fundamentals Unplanned Downtime Steps: Host fails Cluster detects failure Initiate failover Move virtual machine Move storage connectivity from origin to destination host Run virtual machine Cold boot No state info to load Shared Storage VHD Heartbeat
Quick Migration – How Quick Is It? Affected by speed of storage and size of VM memory You need to select the configuration that matches the requirements of your app VM Memory 1 GbE iSCSI 2 Gb FC 4 Gb FC 512 MB ~8 seconds ~ 4 seconds ~2 seconds1 GB ~16 seconds ~8 second ~ 4 seconds2 GB~32 seconds~16 seconds~8 seconds4 GB~64 seconds~32 seconds~16 seconds8 GB~2 minutes~64 seconds~32 seconds
Windows Server 2008 R2 Hyper-V Live Migration What is it? Live-migration of VMs between servers with no loss of service Planned failover solution Benefits No dropped network connections Leverages Failover Clustering Enables dynamic IT environment
Failover Cluster How Does Live Migration Work? Prerequisites: Source and Destination computers running WS08 R2 Source and destination nodes must be part of a Failover Cluster Files used by the VM must be located on shared storage .BIN .VSV .XML . VHD Source Node Destination Node Storage
How Does Live Migration Work? Phase 1: Setup Create TCP connection between source and destination nodes Transfer VM configuration data to destination node Create a new VM on the destination node .BIN .VSV .XML . VHD Source Node Destination Node Network Storage Configuration Data
How Does Live Migration Work? Phase 2: Memory transfer Transfer the content of the VMs memory to the destination node Track pages modified by the VM, retransfer these pages Pause the VM before the final transfer pass .BIN .VSV .XML . VHD Source Node Destination Node Network Storage Memory Content
How Does Live Migration Work? Phase 3: State transfer and VM restore Save register and device state of VM on source node Transfer running state and storage ownership to destination node Start running VM on destination node Cleanup VM on source node .BIN .VSV .XML . VHD Source Node Destination Node Network Storage Running State
SAN Storage Management During Live Migration Live Migration requires VMs to use shared storage SAN LUNs managed by the Failover Clustering service Traditionally, each VM needs its own LUN Volumes cannot be concurrently mounted on multiple nodes .BIN .VSV .XML .VHD .BIN .VSV .XML . VHD .BIN .VSV .XML .VHD
SAN Storage Management During Live Migration The migration of a VM with a dedicated LUN requires that the ownership of the LUN is moved from the source to the destination node Time-consuming, requires the volumes on the LUN to be offlined on the source node and onlined on the destination nodeIs part of the blackout period .BIN .VSV .XML .VHD .BIN .VSV .XML .VHD .BIN .VSV .XML.VHD
SAN Cluster Shared Volumes (CSV) New feature of Failover Clustering in Windows Server 2008 R2 Single consistent namespace for the volumes on all nodes % SystemDrive %\ ClusterStorage \ VolumeX .BIN .VSV .XML .VHD .BIN .VSV .XML.VHD.BIN .VSV.XML.VHD
SAN CSV and Live Migration Moving the files of a VM during a migration becomes as simple as closing the files on the source node and opening the files on the destination node Additionally, CSV significantly simplifies the administration of the SAN .BIN .VSV .XML .VHD .BIN .VSV .XML .VHD .BIN .VSV .XML .VHD
Quick Migration vs. Live Migration Quick Migration (Windows Server 2008 Hyper-V) Save state Create VM on the target Write VM memory to shared storage Move virtual machine Move storage connectivity from source host to target host via Ethernet Restore state & Run Take VM memory from shared storage and restore on Target Run Live Migration (Windows Server 2008 R2 Hyper-V) VM State/Memory Transfer Create VM on the targetMove memory pages from the source to the target via EthernetFinal state transfer and virtual machine restore Pause virtual machine Move storage connectivity from source host to target host via Ethernet Un-pause & Run Host 1Host 2Host 1Host 2
Quick/Live Migration – Planned Downtime Active server requires servicing Move virtualized workloads to a standby server Minimal downtime per virtual machine Virtualization Hosts System Center Virtual Machine Manager Windows Server 2008 Failover Cluster Manager VHDs on SAN Domain Controller Ethernet Storage Connectivity
Quick/Live Migration – Unplanned Downtime Active server loses power Virtual machines automatically restart on the next cluster node If there is not enough memory, the failover automatically moves to the next node until done SCVMM can manage this process Virtualization Hosts System Center Virtual Machine Manager Windows Server 2008 Failover Cluster Manager VHDs onSANDomainControllerEthernet Storage Connectivity
Setup a highly available VM and Live Migration Demo:
Agenda Positioning virtualization and high availability Host vs. guest clustering Quick Migration and Live MigrationCapacity planning for Hyper-V HAVirtual Machine Manager and clustering
Capacity planning for Hyper-V HA Number of servers required will be number of VMs divided by VM to server ratio Example: for a 1:15 ratio, 30 VMs/15 = 2 hosts To provide high-availability you need to add servers Enough spare capacity for other hosts to handle one server failure, add one server; to handle two failures, add two servers, etc. If you need to provide redundancy for an entire datacenter, you might need to add an equal number of servers elsewhere 15 15 10 15 10 10 15 30 ? 7 15 87815
Storage requirements All VM data is stored on shared disks, e.g. NAS or SAN Local disks on hosts store only host OS The shared storage device needs to be …… big enough for all the virtual machine hard disks (OS, apps, data) … fast enough to handle the cumulative disk IO of all VMs CRITICAL SUCCESS FACTOR
Storage HA and distributed clusters Protects against host failure and datacenter failure Single storage device = single point of failure
Storage HA and distributed clusters Protects against host failure and datacenter failure Single storage device = single point of failure Requires a 3 rd party solution that replicates the storage Failover will probably require scripts or a 3 rd party storage failover manager. OK OK OK OK
Agenda Positioning virtualization and high availability Host vs. guest clustering Quick Migration and Live MigrationCapacity planning for Hyper-V HAVirtual Machine Manager and clustering
Maximize Resources Centralized virtual machine deployment and management for Hyper-V, Virtual Server, and VMware ESX servers Intelligent placement of Virtual Machines Fast and reliable P2V and V2V conversion Comprehensive application and service-level monitoring with Operations Manager Integrated Performance and Resource Optimization (PRO) of VMs Increase Agility Rapid provisioning of new and virtual machines with templates Centralized library of infrastructure componentsLeverage and extend existing storage infrastructure and clustersAllow for delegated management and access of VMs Leverage SkillsFamiliar interface, common foundation Monitor physical and virtual machines from one console Fully scriptable using Windows PowerShell A centralized, heterogeneous management solution for the virtual datacenter
SCVMM 2008 support for host clustering Uses Quick/Live Migrate when moving VMs Intelligent placement SCVMM's intelligent placement system will ensure that you don't over commit the resources on your cluster during automatic failover. Cluster aware management Once you have configured a host cluster, SCVMM recognizes this and lets you manage this group of servers as a unit within your host group. Cluster reserve You can specify how many node failures you want the cluster to be able to withstand while keeping the VMs running Easy setup VM can be made highly available by simply checking a check box. Automatically configures the appropriate cluster settings and resource groups.
SCVMM 2008 support for host clustering
Performance and Resource Optimization
Related Content WSV202 Failover Clustering Feature Roadmap for Windows Server 2008 R2 Mon 3 Aug (17:15 - 18:15) | 200 - Intermediate| Session Room A6 | Speaker: Andre Keartland Required Slide Speakers, please list the Breakout Sessions, TLC Interactive Theaters and Labs that are related to your session. VIR301 Achieving High Availability with Hyper-V Tue 4 Aug (10:50 - 11:50) | 300 - Advanced| Session Room A5 | Speaker: Andre Keartland WSV306 Innovating High Availability with Cluster Shared Volumes Wed 5 Aug (09:00 - 10:00) | 300 - Advanced| Session Room D3 | Speaker: Andre Keartland
question & answer
Resources For more information on Microsoft Virtualization including: Whitepapers Product Downloads Case Studies ROI Calculators Solutions with Partners Visit: www.microsoft.com/virtualization
www.microsoft.com/teched Sessions On-Demand & Community http://microsoft.com/technet Resources for IT Professionals http://microsoft.com/msdn Resources for Developers www.microsoft.com/learning Microsoft Certification & Training Resources Resources
Complete an evaluation on CommNet and enter to win! Required Slide
© 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION. Required Slide