WSV 403: Failover Clustering & Hyper-V: Planning your Highly-Available Virtualization EnvironmentSymon PerrimanProgram Manager IIClustering & High-AvailabilityMicrosoft Corporation

Failover Clustering & Hyper-V

Foundation of the Dynamic Datacenter VisionIncrease VM Availability

Hardware health detectionHost OS health detectionVM health detectionApplication/service health detectionAutomatic recovery

VM mobilityDeployment flexibilityFocus is on Windows Server 2008 R2

Failover Clustering & Hyper-V

Guest vs. Host Cluster

Deployment & Validation

Optimizing for Hyper-V

Datacenter Management

CLUSTER

Host Clustering

Cluster service runs inside (physical) host and manages VMsVMs move between cluster nodes

Live Migration – No downtimeQuick Migration – Session state saved to disk

SAN

Why use Host Clustering?

Never rely on a single server for critical systems“Do not put all your eggs in 1 basket”

Survive Host CrashesVMs restarted on another node

Restart VM CrashesVM OS restarted on same node

Recover VM HangsVM OS restarted on same node

Zero Downtime Maintenance & PatchingLive migrate VMs to other hosts

Mobility & Load DistributionLive migrate VMs to different servers to load balance

CLUSTER

Guest Clustering

Cluster service runs inside a VMApps and services inside the VM are managed by the clusterApps move between clustered VMs

iSCSI

CLUSTERc

Why use Guest Clustering?

Application Health MonitoringApp or service within VM crashes or hangs and moves to another VM

Application MobilityApps or services moves to another VM for maintenance or patching of guest OS

iSCSI

Guest vs. Host: Health Detection

Fault Host Cluster Guest Cluster

Host Hardware Failure

Parent Partition Failure

VM Failure

Guest OS Failure

Application Failure

Guest vs. Host: Storage Options

Storage Host Cluster Guest Cluster

Fibre Chanel (FC)

Serial Attached SCSI (SAS)

iSCSI

Host + Guest Clustering

Optimal solution offer the most flexibility and protection

VM high-availability & mobility between physical nodesApplication & service high-availability & mobility between VMs

Increases complexity

CLUSTER

GUEST CLUSTER

SAN

CLUSTER

SAN

iSCSI

CLUSTER

Mixing Physical and Virtual

Mixing physical & virtual nodes is supportedMust still pass “Validate”

Requires iSCSI storageScenarios:

Backup node is a VM in a farmTest cluster

iSCSI

Common Workloads in a Guest Cluster

ExchangeExchange 2007 SP1 (and later) supported for guest and host clusteringExchange 2007 SP1 HA solutions are supported for guest clustering Does not support mixing Guest and Host ClusteringSupport Policy: http://technet.microsoft.com/en-us/library/cc794548.aspx

File ServerFully SupportedLive migration is a great solution for moving the file server to a different physical system without breaking client TCP/IP connections

SQLHost and guest clustering supported for SQL 2005 and 2008Supports guest live and quick migrationSupport policy: http://support.microsoft.com/?id=956893

Other Server Products: http://support.microsoft.com/kb/957006

Failover Clustering & Hyper-V

Guest vs. Host Cluster

Deployment & Validation

Optimizing for Hyper-V

Datacenter Management

SKUs & Hyper-V Server

Microsoft Hyper-V Server 2008 R2FREE Host OS – Download it today!Built on Server Core for even higher availabilityFailover Clustering, Hyper-V, CSV, Live Migration16-node SupportMore 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”

Specification Hyper-V Server Enterprise Datacenter

Failover Cluster Nodes 16 16 16

VM Guest Licenses 0 4 Unlimited

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

Cluster Validation & SupportJoachim NasslanderSenior Solution ArchitectMicrosoft InfrastructureDell Inc. & Cluster MVP

demo

PowerShell Support

Improved ManageabilityRun ValidateEasily Create Clusters & HA RolesGenerate Dependency ReportsBuilt-in Help (Get-Help Cluster)

Hyper-V IntegrationCreate VMs: Add-ClusterVirtualMachineRoleQuick migration: Move-ClusterGroupLive migration: Move-ClusterVirtualMachineRoleAdd a disk to CSV: Add-ClusterSharedVolumeMove CSV disk: Move-ClusterSharedVolumeUpdate VM Configuration: Update-ClusterVirtualMachineConfiguration

Server Core, Hyper-V Server 2008 R2 & RSAT Client

Replaces cluster.exe as the CLI tool

Scripting Cluster DeploymentJoachim NasslanderSenior Solution ArchitectMicrosoft InfrastructureDell Inc. & Cluster MVP

demo

Failover Clustering & Hyper-V

Guest vs. Host Cluster

Deployment & Validation

Optimizing for Hyper-V

Datacenter Management

Cluster Shared VolumesData over any network

VHD VHD VHD

Coordinator Node

1 LUN : Many VMs

Hyper-V

Only

Every node can access storage

SAN

Live Migration

Memory content is copied to new server

Entire VM memory copied

Live Migrate

May be additional incremental data copies until data on both nodes is essentially identical

VHD

SAN

Live Migration

Session state is maintainedNo reconnections necessaryClients stay connected to a “live” VM

VHD

SANARP redirects clients to new nodeOld VM deleted after success

Client directed to new host

CLUSTER

Configuring VM Health Monitoring

Enable VM heartbeat settingRequires Integration Components (ICs) installed

Health check for VM OS from hostUser-Mode HangsSystem Crashes

SAN

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

NICs & Networks in a Cluster

Best SolutionInternal / Cluster / CSV / ‘Heartbeat’Public network for clustered Apps, Services & VMsStorage: iSCSIHyper-V: VM Guest ManagementHyper-V: Live Migration

Minimum is 2 networks:Internal & Live MigrationPublic & VM Guest Management

Use ‘Network Prioritization’ to configure your networks

NIC Teaming & Network PrioritizationJoachim NasslanderSenior Solution ArchitectMicrosoft InfrastructureDell Inc. & Cluster MVP

demo

Settings: Heartbeat for Guest Clusters

Configured in Guest Cluster

Tolerance for network responsiveness during live migration

SameSubnetThreshold & SameSubnetDelaySameSubnetDelay (default = 1 second)

Frequency heartbeats are sent

SameSubnetThreshold (default = 5 heartbeats)Missed heartbeats before an interface is considered down

Settings: AntiAffinityClassNames

AntiAffinityClassNames Groups with same AACN try to avoid moving to same nodehttp://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

Settings: Auto-StartMark 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

Settings: Persistent ModeHA 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

Settings: Root Memory Reserve(d)Different behavior in 2008 R2 RTM and 2008 R2 SP1

2008 R2 RTMThe cluster property, RootMemoryReserved, watches host memory reserve level during VM startupPrevent crashes and failovers if too much memory is being committed during VM startupSets the Hyper-V registry setting, RootMemoryReserve (no ‘d’) across all nodesCluster default: 512 MB, max: 4 GBPS > (get-cluster <cluster name>).RootMemoryReserved=1024

2008 R2 SP1Hyper-V will use a new memory reservation setting for the parent partition memory reserve

Based on “memory pressure” algorithmAdmin can also configure a static reserve value

The cluster nodes will use this new value for the parent partitionConfiguring RootMemoryReserved in the cluster does nothing

Settings: Dynamic MemoryWS2008 R2 SP1 & Hyper-V Server 2008 R2 SP1

Upgrade the Guest Integration Components

Higher VM density across all nodesMemory allocated to VMs is dynamically adjusted in real time

“Ballooning” makes memory pages non-accessible to the VM, until they are neededDoes not impact Task Scheduler or other memory-monitoring utilities

Memory Priority Value is configurable per VMHigher priority for those with higher performance requirements

Ensure you have enough free memory on other nodes for failure recovery

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 configurationPS > Update- ClusterVirtualMachineConfiguration

StorageMoves disks into correct group with new VMsEnsures VM on correct CSV disk with updated paths

NetworkApplies changes to cluster network propertiesChecks live migration compatibility

Several other checks performed

Failover Clustering & Hyper-V

Guest vs. Host Cluster

Deployment & Validation

Optimizing for Hyper-V

Datacenter Management

Virtual Machine Density1000 VMs per ClusterDeploy them all across any number of nodes384 VM/node limitPlanning Considerations:

Hardware LimitsHyper-V LimitsReserve CapacityStorage I/O & Latency

SCVMM: Live MigrationDetects if Live migration can be doneNode placed into ‘Maintenance Mode’

Live-migrate (default) all running HA VMs Serialized multiple live migrationsSave-State (optional)Ideal for host maintenance and patching

Automatically retries live migrations if a node is busy

SCVMM: Quick Storage Migration

Ability to migrate VM storage to new locationMinimizes downtime during transferHandled in a single seamless action

SCVMM: Intelligent Placement

Capacity planning improves resource utilizationSpreads VMs across nodes“Star-Rated” results for easy decision makingCustomizable algorithm

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

Putting it Together

SCVMM Templates

Joachim NasslanderSenior Solution ArchitectMicrosoft InfrastructureDell Inc. & Cluster MVP

demo

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

Integrated Hyper-V

Improved Manage-ability

ScriptedDeployme

nt

Advanced Validation

DatacenterSupport

Passion for High Availability?

Are You Up For a Challenge?

Become a Cluster MVP!

Contact: ClusMVP@microsoft.com

Related ContentBreakout Sessions

VIR309 - Disaster Recovery by Stretching Hyper-V Clusters Across SitesWSV313 - Failover Clustering in 2008 R2: What’s New in the #1 High-Availability SolutionWSV403 - 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 AvailabilityUNC401 - Microsoft Exchange Server 2010: High Availability Deep DiveVIR321 - Advanced Storage Infrastructure Best Practices to Enable Ultimate Hyper-V ScalabilityInteractive SessionsWSV203-IS (R) - Failover Clustering 101: Everything you Wanted to Know but were Afraid to AskWSV306-IS - Failover Clustering with Hyper-V Unleashed in Windows Server 2008 R2DAT303-IS - Performance Scalability and Reliability with SQL Server 2008 R2 & WS 2008 R2UNC321-IS - Microsoft Exchange 2010 SP1 High Availability: Ask The ExpertsVIR302-IS - Understanding How Microsoft Virtualization Compares to VMwareHands-on Labs & Other Session TypesWSV01-HOL - Implementing High AvailabilityMGT201-LNC - Managing Your Virtual EnvironmentsPRC05 - Microsoft Exchange Server 2010 High Availability and Disaster Recovery - Be Prepared

Visit the Cluster Team in the TLC!

We will be there every

hour it is open!

Failover Clustering ResourcesCluster 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

Visit the Cluster Team in the TLC!

We will be there every

hour it is open!

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. 

 

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

Demo Title

NameTitleGroup

demo