virtual techdays INDIA │ 9-11 February 2011 High Availability Clustering using Windows Server 2008 R2 Ninad Doshi │Associate Consultant-Global Delivery, Microsoft

Agenda Hyper-V Introduction Hyper-V Requirements Windows 2008 R2 Clustering Cluster Shared Volumes Live Migration Multi-Site Clustering

Non-Virtualized Architecture Default Windows Server 2008 Setup “Designed for Windows” Server Hardware Windows Server 2008 Windows Kernel Windows 2008 User Mode Processes User Mode Kernel Mode OS ISV / IHV / OEM Provided by: IHV Drivers Applications

Windows Server 2008 VS P Windows Kernel Applications Non- Hypervisor Aware OS Windows Server 2003, 2008 Window s Kernel VSC VMBus Emulation “Designed for Windows” Server Hardware Windows hypervisor Xen-Enabled Linux Kernel Linux VSC Hypercall Adapter Parent Partition Child Partitions VM Service WMI Provider VM Worker Processes OS ISV / IHV / OEM Windows Server Virtualization Microsoft / XenSource User Mode Kernel Mode Provided by: Ring -1 IHV Drivers VMBus Hyper-V Architecture

Hyper-V Requirements Description Hypervisor based virtualization platform Windows Server 2008 R1 or R2 x64 Edition technology Standard, Enterprise and Datacenter Editions Full or Server Core Hyper-V Server Hardware Requirements x64 server with hardware assisted virtualization AMD-V or Intel VT Hardware enabled Data Execution Prevention (DEP) required AMD (NX no execute bit) or Intel (XD execute disable)

Installing the Hyper-V or Failover Cluster Role Installation of Hyper-V or Failover Clustering using PowerShell in Full and Server CORE version of Windows 2008 R2 Open “Windows PowerShell Modules” on the Full Version of Windows 2008 R2 from Administrative Tools Add-WindowsFeature Hyper-V or Failover-Clustering On the Server Core Enable PowerShell and Allow Server Manager Remote Management using sconfig Open PowerShell and enter Import-Module ServerManager Add-WindowsFeature Hyper-V or Failover-Clustering

Hot Add/Remove Storage Overview -Add and remove VHD and pass-through disks to a running VM without requiring a reboot. -Hot-add/remove disk applies to VHDs and pass-through disks attached to the virtual SCSI controller Benefits -Enables storage growth in VMs without downtime -Enables additional datacenter backup scenarios

Processor Compatibility Mode Overview -Allows live migration across different CPU versions within the same processor family (i.e. Intel-to-Intel and AMD-to-AMD). -Does NOT enable cross platform from Intel to AMD or vice versa. -Configure compatibility on a per-VM basis. -Abstracts the VM down to the lowest common denominator in terms of instruction sets available to the VM. Benefits -Provides a great deal of migration flexibility within clusters. -Enables migration across a broader range of Hyper-V host hardware. -No specific hardware requirements needed.

Processor Compatibility Mode How it works? If a host A’s processor features are superset of host B’s processor features, migrating a running VM from host A to host B will fail; if the same VM is put in processor compatibility mode migration will succeed (see below image) Hypervisor exposes only those features to VM that are available between all Hyper-V supported processors VM NOT in Processor compatibility mode VM in Processor compatibility mode Physical Processor features: X,Y,Z VM sees processor features: X,Y,Z Physical Processor features: X,Y Physical Processor features: X,Y,Z Physical Processor features: X,Y Host A Host B Host A Migration fails Migration succeeds VM sees processor features: X,Y

What is the Validate tool? Test tool built right into the product Runs a focused set of tests on a collection of servers that are intended to be a cluster Catch hardware or configuration problems before the cluster goes in production -Ensures that the solution you are about to deploy is rock solid Run validate each and every time you install a new cluster -It’s the very first thing you do! Validate can also be run on configured clusters as a diagnostic tool -Disk Resources need to be in an Offline state to be validated Will replace the Cluster HCL in Win2008!

Requirements Software Hardware Network and Domain Account All multi-path software must be based on Microsoft Multipath I/O (MPIO) If using a custom Device Specific Module (DSM), it must have a logo All components in a cluster must have a Certified for Windows logo

Windows 2008 Cluster Storage Requirements Only storage that supports Persistent Reservations will be supported in 2008 Failover Clustering Deprecating parallel-SCSI support Serial Attached SCSI (SAS) based clusters will replace parallel-SCSI Fibre Channel Fibre ChanneliSCSI SAS Supported Shared Bus Types:

Demo Creating a HyperV cluster

Cluster Shared Volumes Better Storage Utilization with CSV Distributed file access solution for Hyper-V Concurrent access to disk from any node VMs do not know their host VMs no longer bound to storage VMs remain online during live migration

Single Name Space CSV provides a single consistent file name space Files have the same name and path when viewed from any node in the cluster CSV volumes are exposed as directories and subdirectories under the “ClusterStorage” root directory -C:\ClusterStorage\Volume1\ -C:\ClusterStorage\Volume2\ -C:\ClusterStorage\Volume3\

CSV Compatibility No special hardware requirements Same requirements as standard cluster disk iSCSI, Fibre Channel, SAS No directory structure or depth limitations No proprietary file system Standard NTFS Support Hyper-V Workload It Just Works!

Cluster Shared Volumes Overview Better Storage Utilization with CSV Data over any network VHD Coordinator Node 1 LUN, Many VMs Distributed File Access for Hyper-V

CSV Benefits Simplify Storage Management -Consolidate VMs on a CSV disk -Individual VMs can failover on a shared LUN -Remove drive letter dependency Live migration Increases Reliability Dynamic I/O Redirection -Node Fault Tolerance -Network Fault Tolerance -Storage Access Redirection 99% 99.9% 99.99% % Availability

Live Migration Live Migration via Cluster Manager -In box UI Live Migration via Virtual Machine Manager -Orchestrate migrations via policy Moving from Quick to Live Migration: -Guest OS limitations?:No -Changes to VMs needed?:No -Changes to Storage infrastructure: No -Changes to Network Infrastructure:No -Update to WS 2008 R2 Hyper-V:Yes

Hyper-V Live Migration Move a running VM between hosts with no user-perceived downtime Client is not aware of the migration Maintain open TCP connections to the guest OS Clients stay connected Planned failover Failover Clustering still recovers VM from an unplanned failover

Demo 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 Virtual Machine Live Migration

Live Migration Session state is maintained No reconnections necessary Clients stay connected to “live” VM VHD Client directed to new host ARP issued to point routing devices to new node Old VM deleted after success Virtual Machine Live Migration

Migration – Our Upgrade Path Built-in Migration Wizard Windows Server 2008 is a new architecture rolling upgrades are not available Migration tool does not migrate data, it only migrates resources Reuse storage or copy data and use new storage Migrate resource groups between clusters Enhanced Pre- and Post- migration reports Guide: R R2

Multi-Site Clustering Introduction

Benefits of a Multi-Site Cluster Protects against loss of an entire datacenter Automates failover -Reduced downtime -Lower complexity of disaster recovery plan Reduces administrative overhead -Automatically synchronize application and cluster changes -Easier to keep consistent than standalone servers The primary reason DR solutions fail is dependence on people The primary reason DR solutions fail is dependence on people

Evaluate Business Need Multi-Site cluster isn’t for every company/application -Increased cost -Potentially increased complexity (compared to local clusters) Evaluate business requirements -Application importance -Type of application (database, , line of business) -Availability options (tape backup, log shipping, clusters) -Plan: architecture, site location, failover, failback, testing -Test, test, and test again (and test routinely)

Multi-Site Clustering Diagram

Multi-Site Clustering Guide Design guide: - Deployment guide/checklist: -

Session Summary Windows Server 2008 R2 is delivering substantial value -Hyper-V deployments will want to upgrade immediately No special requirements – it just works Lower costs Higher Availability Cluster Shared Volumes Live Migration PowerShell Migration Improved Integration Datacenter Tools Improved Logging Enhanced Validation Performance Counters Eventing

Online Resources Single Source for Failover Clustering Windows Server Virtualization Blog Site: Windows Server Virtualization TechNet Site: ion.mspx Infrastructure Planning and Design guides for Virtualization Virtualization Case Studies Windows Server 2008 Virtualization & Consolidation: consolidation.aspx Optimized Desktop Infrastructure: spx

virtual techdays THANKS │ 9-11 February 2011