WSV 403: Failover Clustering & Hyper-V: Planning your Highly-Available Virtualization Environment

2. WSV 403: Failover Clustering & Hyper-V: Planning your Highly-Available Virtualization Environment Symon Perriman Program Manager IIClustering & High-Availability Microsoft Corporation

3. Failover Clustering & Hyper-V • Foundation of the Dynamic Datacenter Vision • Increase VM Availability • Hardware health detection • Host OS health detection • VM health detection • Application/service health detection • Automatic recovery • VM mobility • Deployment flexibility • Focus is on Windows Server 2008 R2

4. Failover Clustering & Hyper-V Guest vs. Host Cluster Deployment & Validation Optimizing for Hyper-V Datacenter Management

5. Host Clustering • Cluster service runs inside (physical) host and manages VMs • VMs move between cluster nodes • Live Migration – No downtime • Quick Migration – Session state saved to disk CLUSTER SAN

6. Why use Host Clustering? • Never rely on a single server for critical systems • “Do not put all your eggs in 1 basket” • Survive Host Crashes • VMs restarted on another node • Restart VM Crashes • VM OS restarted on same node • Recover VM Hangs • VM OS restarted on same node • Zero Downtime Maintenance & Patching • Live migrate VMs to other hosts • Mobility & Load Distribution • Live migrate VMs to different servers to load balance

7. Guest Clustering • Cluster service runs inside a VM • Apps and services inside the VM are managed by the cluster • Apps move between clustered VMs CLUSTER iSCSI

8. Why use Guest Clustering? • Application Health Monitoring • App or service within VM crashes or hangs and moves to another VM • Application Mobility • Apps or services moves to another VM for maintenance or patching of guest OS CLUSTERc iSCSI

9. Guest vs. Host: Health Detection

10. Guest vs. Host: Storage Options

11. Host + Guest Clustering • Optimal solution offer the most flexibility and protection • VM high-availability & mobility between physical nodes • Application & service high-availability & mobility between VMs • Increases complexity GUEST CLUSTER CLUSTER CLUSTER iSCSI SAN SAN

12. Mixing Physical and Virtual • Mixing physical & virtual nodes is supported • Must still pass “Validate” • Requires iSCSI storage • Scenarios: • Backup node is a VM in a farm • Test cluster CLUSTER iSCSI

13. Common Workloads in a Guest Cluster • Exchange • Exchange 2007 SP1 (and later) supported for guest and host clustering • Exchange 2007 SP1 HA solutions are supported for guest clustering • Does not support mixing Guest and Host Clustering • Support Policy: http://technet.microsoft.com/en-us/library/cc794548.aspx • File Server • Fully Supported • Live migration is a great solution for moving the file server to a different physical system without breaking client TCP/IP connections • SQL • Host and guest clustering supported for SQL 2005 and 2008 • Supports guest live and quick migration • Support policy: http://support.microsoft.com/?id=956893 • Other Server Products: http://support.microsoft.com/kb/957006

14. Failover Clustering & Hyper-V Guest vs. Host Cluster Deployment & Validation Optimizing for Hyper-V Datacenter Management

15. SKUs & Hyper-V Server • Microsoft Hyper-V Server 2008 R2 • FREEHost OS – Download it today! • Built on Server Core for even higher availability • Failover Clustering, Hyper-V, CSV, Live Migration • 16-node Support • More information: http://www.microsoft.com/hyper-v-server/en/us/default.aspx • All solutions still have 2 requirements for support: • Every component must be logoed • The entire solution must pass “Validate”

16. Validating a Cluster • For Microsoft support, cluster must pass the built-in Validate a Cluster Configuration (“Validate”) test • Run during configuration or after deployment • Best practices analyzed if run on configured cluster • Series of end-to-end tests on all cluster components • Configuration info for support and documentation • Networking issues • Troubleshoot in-production clusters • More information http://go.microsoft.com/fwlink/?LinkID=119949

17. Cluster Validation & Support Joachim Nasslander Senior Solution Architect Microsoft Infrastructure Dell Inc. & Cluster MVP demo

18. PowerShell Support • Improved Manageability • Run Validate • Easily Create Clusters & HA Roles • Generate Dependency Reports • Built-in Help (Get-Help Cluster) • Hyper-V Integration • Create VMs: Add-ClusterVirtualMachineRole • Quick migration: Move-ClusterGroup • Live migration: Move-ClusterVirtualMachineRole • Add a disk to CSV: Add-ClusterSharedVolume • Move CSV disk: Move-ClusterSharedVolume • Update VM Configuration: Update-ClusterVirtualMachineConfiguration • Server Core, Hyper-V Server 2008 R2& RSAT Client • Replaces cluster.exe as the CLI tool

19. Scripting Cluster Deployment Joachim Nasslander Senior Solution Architect Microsoft Infrastructure Dell Inc. & Cluster MVP demo

20. Failover Clustering & Hyper-V Guest vs. Host Cluster Deployment & Validation Optimizing for Hyper-V Datacenter Management

21. Hyper-V Only Cluster Shared Volumes Data over any network Coordinator Node Every node can access storage SAN 1 LUN : Many VMs VHD VHD VHD

22. Live Migration Entire VM memory copied Memory content is copied to new server Live Migrate SAN May be additional incremental data copies until data on both nodes is essentially identical VHD

23. Live Migration Client directed to new host Session state is maintained No reconnections necessary Clients stay connected to a “live” VM SAN • ARP redirects clients to new node • Old VM deleted after success VHD

24. Configuring VM Health Monitoring • Enable VM heartbeat setting • Requires Integration Components (ICs) installed • Health check for VM OS from host • User-Mode Hangs • System Crashes CLUSTER SAN

25. AD Considerations • Same AD Requirements as 2008 • Nodes must be in the same domain • Need an accessible writable DC, cannot use only a Read-Only DC (KB 2008654) • DCs can be run on nodes, but use 2+ nodes (KB 281662) • Do not put all your DCs on clustered VMs • DC needed for authentication and starting cluster service • Must have at least 1 DC on physical hardware

26. NICs & Networks in a Cluster • Best Solution • Internal / Cluster / CSV / ‘Heartbeat’ • Public network for clustered Apps, Services & VMs • Storage: iSCSI • Hyper-V: VM Guest Management • Hyper-V: Live Migration • Minimum is 2 networks: • Internal & Live Migration • Public & VM Guest Management • Use ‘Network Prioritization’ to configure your networks

27. NIC Teaming & Network Prioritization Joachim Nasslander Senior Solution Architect Microsoft Infrastructure Dell Inc. & Cluster MVP demo

28. Settings: Heartbeat for Guest Clusters • Configured in Guest Cluster • Tolerance for network responsiveness during live migration • SameSubnetThreshold & SameSubnetDelay • SameSubnetDelay (default = 1 second) • Frequency heartbeats are sent • SameSubnetThreshold (default = 5 heartbeats) • Missed heartbeats before an interface is considered down

29. Settings: AntiAffinityClassNames • AntiAffinityClassNames • Groups with same AACN try to avoid moving to same node • http://msdn.microsoft.com/en-us/library/aa369651(VS.85).aspx • Enables VM distribution across host nodes • Better utilization of host OS resources • Failover behavior on large clusters: KB 299631

30. Settings: Auto-Start • Mark groups as lower priority • Enables the most important VMto start first • Group property • Enabled by default • Disabled VMs needs manual restart to recover after a crash

31. Settings: Persistent Mode • HA Service or Application will return to original owner • Better VM distribution after cold start • Enabled by default for VM groups • Disabled by default for other groups

32. Settings: Root Memory Reserve(d) • Different behavior in 2008 R2 RTM and 2008 R2 SP1 • 2008 R2 RTM • The cluster property, RootMemoryReserved, watches host memory reserve level during VM startup • Prevent crashes and failovers if too much memory is being committed during VM startup • Sets the Hyper-V registry setting, RootMemoryReserve (no ‘d’) across all nodes • Cluster default: 512 MB, max: 4 GB • PS > (get-cluster <cluster name>).RootMemoryReserved=1024 • 2008 R2 SP1 • Hyper-V will use a new memory reservation setting for the parent partition memory reserve • Based on “memory pressure” algorithm • Admin can also configure a static reserve value • The cluster nodes will use this new value for the parent partition • Configuring RootMemoryReserved in the cluster does nothing

33. Settings: Dynamic Memory • WS2008 R2 SP1 & Hyper-V Server 2008 R2SP1 • Upgrade the Guest Integration Components • Higher VM density across all nodes • Memory allocated to VMs is dynamically adjusted in real time • “Ballooning” makes memory pages non-accessible to the VM, until they are needed • Does not impact Task Scheduler or other memory-monitoring utilities • Memory Priority Value is configurable per VM • Higher priority for those with higher performance requirements • Ensure you have enough free memory on other nodes for failure recovery

34. Refreshing the VM Configuration • Make configuration changes through Failover Cluster Manager or SCVMM • Hyper-V Manager is not cluster aware, changes will be lost • “Refresh virtual machine configuration” • Looks for any changes to VM or Cluster configuration • PS > Update-ClusterVirtualMachineConfiguration • Storage • Moves disks into correct group with new VMs • Ensures VM on correct CSV disk with updated paths • Network • Applies changes to cluster network properties • Checks live migration compatibility • Several other checks performed

35. Failover Clustering & Hyper-V Guest vs. Host Cluster Deployment & Validation Optimizing for Hyper-V Datacenter Management

36. Virtual Machine Density • 1000 VMs per Cluster • Deploy them all across any number of nodes • 384 VM/node limit • Planning Considerations: • Hardware Limits • Hyper-V Limits • Reserve Capacity • Storage I/O & Latency

37. SCVMM: Live Migration • Detects if Live migration can be done • Node placed into ‘Maintenance Mode’ • Live-migrate (default) all running HA VMs Serialized multiple live migrations • Save-State (optional) • Ideal for host maintenance and patching • Automatically retries live migrations if a node is busy

38. SCVMM: Quick Storage Migration • Ability to migrate VM storage to new location • Minimizes downtime during transfer • Handled in a single seamless action

39. Capacity planning improves resource utilization Spreads VMs across nodes “Star-Rated” results for easy decision making Customizable algorithm SCVMM: Intelligent Placement

40. SCOM: Performance & Resource Optimization (PRO) • Alleviate the effects of host-level failure • Ensure efficient use of resources in the virtualized environment • Allow VMM Admins to react and manage resources independently • Integrated with SCVMM • SCOM sends alters to SCVMM to trigger live migration of VMs

41. Putting it Together

42. SCVMM Templates Joachim Nasslander Senior Solution Architect Microsoft Infrastructure Dell Inc. & Cluster MVP demo

43. Conclusion • 2008 R2 Failover Clustering is optimized for Hyper-V • Integrated setup, validation, configuration and management • Flexible options for host and guest clustering • Automated deployments are simplified with PowerShell • Scales to 1000 VMs with advanced datacenter management

44. Passion for High Availability? Are You Up For a Challenge? Become a Cluster MVP! Contact: ClusMVP@microsoft.com

45. Related Content Visit the Cluster Team in the TLC! We will be there every hour it is open! • Breakout Sessions • VIR309 - Disaster Recovery by Stretching Hyper-V Clusters Across Sites • WSV313 - Failover Clustering in 2008 R2: What’s New in the #1 High-Availability Solution • WSV403 - Failover Clustering & Hyper-V: Planning your Highly-Available Virtualization Environment • DAT210 - Mission Critical: High Availability Overview • DAT211 - Mission Critical: Comparing High-Availability Solutions • DAT212 - Mission Critical: Improving High-Availability • UNC303 - Microsoft Lync Server 2010 : Voice Architecture and Planning for High Availability • UNC401 - Microsoft Exchange Server 2010: High Availability Deep Dive • VIR321 - Advanced Storage Infrastructure Best Practices to Enable Ultimate Hyper-V Scalability • Interactive Sessions • WSV203-IS (R) - Failover Clustering 101: Everything you Wanted to Know but were Afraid to Ask • WSV306-IS - Failover Clustering with Hyper-V Unleashed in Windows Server 2008 R2 • DAT303-IS - Performance Scalability and Reliability with SQL Server 2008 R2 & WS 2008 R2 • UNC321-IS - Microsoft Exchange 2010 SP1 High Availability: Ask The Experts • VIR302-IS - Understanding How Microsoft Virtualization Compares to VMware • Hands-on Labs & Other Session Types • WSV01-HOL - Implementing High Availability • MGT201-LNC - Managing Your Virtual Environments • PRC05 - Microsoft Exchange Server 2010 High Availability and Disaster Recovery - Be Prepared

46. Failover Clustering Resources Visit the Cluster Team in the TLC! We will be there every hour it is open! • Cluster Team Blog: http://blogs.msdn.com/clustering/ • Cluster Resources: http://blogs.msdn.com/clustering/archive/2009/08/21/9878286.aspx • Cluster Information Portal: http://www.microsoft.com/windowsserver2008/en/us/clustering-home.aspx • Clustering Technical Resources: http://www.microsoft.com/windowsserver2008/en/us/clustering-resources.aspx • Clustering Forum (2008): http://forums.technet.microsoft.com/en-US/winserverClustering/threads/ • Clustering Forum (2008 R2): http://social.technet.microsoft.com/Forums/en-US/windowsserver2008r2highavailability/threads/ • R2 Cluster Features: http://technet.microsoft.com/en-us/library/dd443539.aspx

47. Session Evaluations Tell us what you think, and you could win! All evaluations submitted are automatically entered into a daily prize draw*  Sign-in to the Schedule Builder at http://europe.msteched.com/topic/list/ * Details of prize draw rules can be obtained from the Information Desk.

48. © 2010 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.

49. Demo Title Name Title Group demo