1 / 39

Guest vs. Host Clustering: What ? Why? When?

Required Slide. SESSION CODE: WSV315. Guest vs. Host Clustering: What ? Why? When? . Steven Ekren Senior Program Manager Microsoft Corporation. Session Objectives And Takeaways. Session Objective(s): Understand host and guest clustering high availability advantages

slade
Download Presentation

Guest vs. Host Clustering: What ? Why? When?

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Required Slide SESSION CODE: WSV315 Guest vs. Host Clustering:What? Why? When? Steven Ekren Senior Program Manager Microsoft Corporation

  2. Session Objectives And Takeaways • Session Objective(s): • Understand host and guest clustering high availability advantages • Host and Guest clustering both have valuable high availability advantages for services and applications • Know when to pick the right solution

  3. Failover Clustering + Hyper-V • To increase the availability of VM’s and the applications they host: • Hardware health detection • Host operating system health detection • Virtual machine health detection • Application/service health detection • Automatic recovery • VM mobility Clustering keeps you from putting all your VM eggs in 1 basket

  4. Host Clustering

  5. What – is a Host Cluster? • Cluster service runs inside parent partition of a Hyper-V enabled server • Cluster manages VM’s • VM’s move from server to server SAN

  6. VM MobilityPlanned Downtime • VM’s can seamlessly move from one server to another with no client downtime • Live Migration – No downtime • Quick Migration – Session state saved to disk SAN

  7. VM MobilityUnplanned Downtime • Recovery from failures due to hardware or problem in parent partition • VM’s are cold restarted on a surviving server SAN

  8. OS Health Monitoring • Enables any app to be covered by increased availability • Virtual machines are health checked • Requires Integration Components installed SAN

  9. When – Host Clustering? • Zero Downtime Host Patching • Hardware changes • Software updates to parent partition • Load Distribution • Live migrate VM’s to different servers to load balance • Great answer for any / all Hyper-V deployments

  10. Key Differentiators Takeaway • Host clustering delivers two key values:

  11. Guest Clustering

  12. What – is a Guest Cluster? • Cluster service runs inside a Hyper-V guest • Application and services running inside the VM are managed by the cluster • Apps move from VM to VM iSCSI

  13. When – Guest Clustering? • Service or application health detection and automatic recovery • Move service or application to a different VM to allow update of OS or service/application running in guest iSCSI

  14. Why – App Mobility • Applications and services running inside the guest are health checked • Storage is presented to the VM directly via the Microsoft iSCSI Software Initiator iSCSI

  15. Key Differentiators Takeaway • Guest clustering delivers two key values:

  16. Host vs. Guest Clustering

  17. Quick Recap

  18. Health Detection

  19. Storage Options

  20. Host + Guest Clustering Best of both worlds • Provides the most flexibility and protection • VM and App mobility • Consider host VM action’s effects on guest cluster • Live migrate • Quick migrate • Shutdown VM • Pause VM • A cluster on a cluster does come at increased complexity…

  21. Using Host/Guest Clusters Steven EkrenSenior Program ManagerMicrosoft DEMO

  22. Demo Configuration CorpNet Internal iSCSI Target 1 Target 2 iSCSI

  23. Heartbeat Settings • SameSubnetThreshold & SameSubnetDelay • Where to configure: guest cluster • Effect: increase tolerance for network responsiveness during live migration Configure Heartbeat and DNS Settings in a Multi-Site Failover Cluster. http://technet.microsoft.com/en-us/library/dd197562(WS.10).aspx

  24. Keeping VM’s off the same Node • AntiAffinityClassName • Where to configure: host cluster • Effect: attempts to avoid hosting VMs on the same node How to configure Windows clustering groups for hot spare support KB Article: 296799

  25. Low Priority VM’s • AutoStart (Windows Server 2008 R2) • Where to configure: host cluster • Effect: if set to “no”, VM will not automatically start if there is a node or group failure.

  26. Ensuring Startup • Persistent mode (Windows Server 2008 R2) • Where to configure: host cluster • Effect: When enabled, and the cluster starts, VMs will attempt to be placed on node that they were last moved to.

  27. Mixing Physical and Virtual • Can mix having both physical nodes and VM’s in the same cluster • Supported – just pass validate • Requires iSCSI storage • Scenario: Workload regularly runs on physical node, but VM is secondary node iSCSI

  28. Guest Cluster WorkloadsSQL • Host and guest clustering supported for SQL 2005 and 2008 • Supports guest live and quick migration Support policy for Microsoft SQL Server products that are running in a hardware virtualization environment http://support.microsoft.com/?id=956893

  29. Guest Cluster WorkloadsExchange • Exchange 2007 SP1 (and later) supported for guest and host clustering • Exchange 2007 SP1 HA solutions are supported for guest clustering http://technet.microsoft.com/en-us/library/cc794548.aspx

  30. Guest Cluster WorkloadsFile Server • Supported • Live migration is a great solution for moving the file server to a different physical system without breaking client TCP/IP connections

  31. Summary • Configuring VM’s for high availability is the norm, not the exception • Each model has it’s advantages • Understand your customers goals to help choose what’s right for them • There is no general right or wrong answer

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

  33. Related Content • Breakout Sessions • WSV313 | Failover Clustering Deployment Success • WSV314 | Failover Clustering Pro Troubleshooting with Windows Server 2008 R2 • VIR303 | Disaster Recovery by Stretching Hyper-V Clusters across Sites • ARC308 | High Availability: A Contrarian View • DAT207 | SQL Server High Availability: Overview, Considerations, and Solution Guidance • DAT303 | Architecting and Using Microsoft SQL Server Availability Technologies in a Virtualized World • DAT305 | See the Largest Mission Critical Deployment of Microsoft SQL Server around the World • DAT401 | High Availability and Disaster Recovery: Best Practices for Customer Deployments • DAT407 | Windows Server 2008 R2 and Microsoft SQL Server 2008: Failover Clustering Implementations • UNC304 | Microsoft Exchange Server 2010: High Availability Deep Dive • UNC305 | Microsoft Exchange Server 2010 High Availability Design Considerations Visit the Cluster Team in the TLC Failover Clustering Booth WSV-7 • Interactive Sessions • VIR06-INT | Failover Clustering with Hyper-V Unleashed with Windows Server 2008 R2 • UNC01-INT | Real-World Database Availability Group (DAG) Design • VIR02-INT | Hyper-V Live Migration over Distance: A Multi-Datacenter Approach • BOF34-IT | Microsoft Exchange Server High Availability and Disaster Recovery: Are You Prepared? • Hands-on Labs • WSV01-HOL | Failover Clustering in Windows Server 2008 R2 • DAT01-HOL | Create a Two-Node Windows Server 2008 R2 Failover Cluster • DAT02-HOL | Create a Windows Server 2008 R2 MSDTC Cluster • DAT09-HOL | Installing a Microsoft SQL Server 2008 + SP1 Clustered Instance • DAT12-HOL | Maintaining a Microsoft SQL Server 2008 Failover Cluster • UNC02-HOL | Microsoft Exchange Server 2010 High Availability and Storage Scenarios • VIR06-HOL | Implementing High Availability and Live Migration with Windows Server 2008 R2 Hyper-V

  34. Failover Clustering Resources • 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

  35. Required Slide Resources Learning • Sessions On-Demand & Community • Microsoft Certification & Training Resources www.microsoft.com/teched www.microsoft.com/learning • Resources for IT Professionals • Resources for Developers • http://microsoft.com/technet • http://microsoft.com/msdn

  36. Required Slide Complete an evaluation on CommNet and enter to win!

  37. Sign up for Tech·Ed 2011 and save $500 starting June 8 – June 31st http://northamerica.msteched.com/registration You can also register at the North America 2011 kiosk located at registrationJoin us in Atlanta next year

  38. © 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.

  39. Required Slide

More Related