Virtualization And High Availability. Howard Chow Microsoft MVP

Transcription

1 Virtualization And High Availability Howard Chow Microsoft MVP

2 Session Objectives And Agenda Virtualization and High Availability Types of high availability enabled by virtualization Enabling a highly available cluster with virtual machines Demo: Windows Server 2008 Cluster Creation Demo: Making a Virtual Machine highly available High Availability Best Practices

3 Session Prerequisites Knowledge of Windows Server 2008 Knowledge of Microsoft Hyper-V Cluster Experience NOT REQUIRED!

4 Windows Server 2008 With Hyper-V Technology A role of Windows Server 2008 (Std, EE, DC) Can be installed on both Windows Server 2008 Full and Core Production servers can be configured as a minimal footprint Server Core role Hypervisor based architecture Flexible and dynamic virtualization solution Managed by the Microsoft System Center family of products

5 VIRTUALIZATION AND HIGH AVAILABILITY

6 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

7 Microsoft Hyper-V Quick Migration Provides solutions for both planned and unplanned downtime Planned downtime Quickly move virtualized workloads to service underlying hardware More common than unplanned Unplanned downtime Automatic failover to other nodes (hardware or power failure) Not as common and more difficult

8 Quick Migration Fundamentals Planned Downtime 1. Save state a) Save entire virtual machine state 2. Move virtual machine VHDs Shared Storage a) Move storage connectivity from origin to destination host 3. Restore state and Run a) Restore virtual machine and run Network Connectivity

9 Ethernet Quick Migration: Planned Downtime Domain Controller Virtualization Servers (3 + 1 Servers) Active server requires servicing Move virtualized workloads to a standby server System Center Virtual Machine Manager 2008 Windows Server 2008 Failover Cluster Manager Storage Connectivity VHDs on SAN

10 Ethernet Quick Migration: Unplanned Downtime System Center Virtual Machine Manager 2008 Domain Controller Virtualization Servers (3 + 1 Servers) 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 Windows Server 2008 Failover Cluster Manager Storage Connectivity VHDs on SAN

11 Quick Migration Storage Considerations (1/2) Pass-through Disks in a cluster Provides enhanced I/O performance Requires VM configuration file to be stored separate from the virtual machine file Create file share on the cluster and store VM configuration files for virtual machines that use pass-thru VHD Based One LUN per VM best practice Ability to provision more then one VM per LUN but all failover as a unit

12 Quick Migration Storage Considerations (2/2) SAN/iSCSI Leverage MPIO solutions for path availability and I/O throughput Leverage VM provisioning via GUID ID instead of drive letter \\?\<GUID>\ Use Mountvol.exe to find GUID of provisioned LUN

13 Windows Server 2008 Hyper-V High Availability: A Competitive Look Volume Shadow Service Support for Host Backup? Windows Server 2008 Hyper-V VMware VI3 Starter VMware VI3 Standard VMware VI3 Enterprise Yes No No Proprietary Backup Solution Quick Migration? Yes, RTM No No N/A Unplanned downtime failover? Cost: Additional Comments: Yes, RTM; Parity with VMware VI3 EE Included with Windows Server 2008 EE and DTC Editions High Availability Built-In No No Yes; Parity with Windows Virtualization $1,000 for two sockets; $2,000 for four sockets No SAN support; Limited to 8 GB of physical memory support $3,750 for two sockets; $7,500 for four sockets No migration or server side backup capabilities $5,750 for two sockets; $11,500 for four sockets

14 Other Types Of High Availability Virtual Machine Clustering Suited for stateful applications Application clusters SQL Exchange Network Load Balancing Stateless HA approach Enabled with Hyper-V s enhanced networking support

15 Comparing High Availability To Fault Tolerance Continuous replication of VM memory contents Fail through concept vs. failover Hardware or component failure undetected by applications Requires redundant hardware configurations deployed in lock step Special interconnects Vendors with FT Hyper V solutions Marathon Stratus Technologies

16 Configuring A VM To Be Highly Available 3. Move the disk to resource group 4. Create VM Configuration resource 2. Find available disk resource 5. Create VM resource 1. Create resource group 6. Set resource dependencies VM Resource VM Config Resource Disk Resource

17 Placement And Cluster Reserve Cluster reserve = 1 node Can the cluster sustain 1 node failure? YES Clustered Host 1 Clustered Host 2 Clustered Host 3

18 STRETCH CLUSTER

19 Geographically Diverse Clusters Stretching Nodes across the river used to be good enough But businesses are now demanding more!

20 Stretch Clusters (Long Distance) No More Single-Subnet Limitation Allow cluster nodes to communicate across network routers No more having to connect nodes with VLANs! Configurable Heartbeat Timeouts Increase to Extend Geographically Dispersed Clusters over greater distances Decrease to detect failures faster and take recovery actions for quicker failover Storage Vendor Based Solution Mirrored storage between stretched locations Hardware or Software based replication

21 GUEST CLUSTERING

22 Guest Clustering Is the workload being run in the virtual machine cluster aware? File, Print, DNS, DHCP, SQL, etc Virtual machines are clustered using iscsi Guest clustering can be used with quick migration!

23 Guest Clustering Example Windows Server 2008 with Hyper-V Node 1 Private Virtual Network iscsi Target Node 2

24 Guest Clustering Best Practices Multiple NICs in system Private virtual network for cluster communication Virtual network dedicated for iscsi traffic Workload running in VM must be cluster aware

25 HYPER-V & NLB

26 Why Network Load Balancing? Scalability Network Load Balancing can load balance requests for individual TCP/IP request across the cluster Can load balance multiple server requests, from the same client or from several clients across multiple hosts in the cluster High Availability Can automatically detect and recover from a failed or offline computer Can automatically rebalance the network load when servers are added or removed

27 Ethernet Windows Server Virtualization And Network Load Domain Controller Balancing Virtualization Servers Running Virtual Web Servers with NLB June : Web Store working well Nov: Operations Manager notices seasonal demand and signals Virtual Machine Manager to deploy an additional Web Server Dec: Even more customer demand means that another Web Server will be rapidly deployed Public Web Store Storage Connectivity VHDs on SAN Operations Manager Monitoring system health and performance Enforces business policy Integrates with Virtual Machine Manager Virtual Machine Manager Virtual Machine Management Rapid deployment Centralized Virtual Machine Library

28 Microsoft Virtualization HA Partners Clustered File Systems SanBolic PolyServe Replication Storage OEM synchronous and asynchronous solutions Doubletake

29 Resources Microsoft Virtualization Home Windows Server 2008 Home Hyper-V WMI Provider APIs Hyper-V Hypercall Interface 1E2E518-C62C-4FF2-8E50-3A37EA4100F5&displaylang=en

30 Q&A

31 2008 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.