Module 11Implementing Failover Clustering with Hyper-V

Module Overview

Overview of Integrating Hyper-V with Failover ClusteringImplementing Hyper-V Virtual Machines on Failover ClustersImplementing Hyper-V Virtual Machine Movement•Managing Hyper-V Virtual Environments by Using VMM

Lesson 1: Overview of Integrating Hyper-V with Failover ClusteringOptions for Making Virtual Machines Highly AvailableHow Does a Failover Cluster Work with Hyper-V Nodes?What Is New in Failover Clustering for Hyper-V in Windows Server 2012?What Is New in Failover Clustering for Hyper-V in Windows Server 2012 R2?•Best Practices for Implementing High Availability in a Virtual Environment

Options for Making Virtual Machines Highly Available

High availability options

Description

Host clustering • Virtual machines are highly available

• Does not require virtual machine operating system or application to be cluster aware

Guest clustering • Virtual machines are failover cluster nodes

• Virtual machine applications must be cluster aware

• Requires iSCSI or virtual fiber channel interface for shared storage connections

NLB • Virtual machines are NLB cluster nodes

• Use for web-based applications

How Does a Failover Cluster Work with Hyper-V Nodes?

Node 2 Node 1

Shared bus or iSCSI connection

A dedicated network connects the

failover cluster nodes

Cluster Storage

What Is New in Failover Clustering for Hyper-V in Windows Server 2012?The Failover Clustering improvements for Hyper-V in Windows Server 2012 include:• Support for up to 8,000 virtual machines per cluster• Multi-select virtual machines for Live Migration• Virtual machine priority attribute• CSV improvements• Virtual machine application monitoring• Storage of virtual machines on highly available SMB file share

What Is New in Failover Clustering for Hyper-V in Windows Server 2012 R2?•Windows Server 2012 R2 provides new features for virtual machine clustering, that include:• Shared virtual hard disk•Virtual machine drain on shutdown•Network health detection

Best Practices for Implementing High Availability in a Virtual Environment•Use Windows Server 2012 R2 as the Hyper-V host

•Plan for failover scenarios •Plan the network design for failover clustering

•Plan the shared storage for failover clustering

•Use the recommended failover cluster quorum mode

•Deploy standardized Hyper-V hosts •Develop standard management practices

Lesson 2: Implementing Hyper-V Virtual Machines on Failover ClustersComponents of Hyper-V ClustersPrerequisites for Implementing Hyper-V ClustersImplementing Failover Clustering for Hyper-V Virtual MachinesConfiguring CSVConfiguring a Shared Virtual Hard DiskUsing Scale-Out File Servers Over SMB 3.0 for Virtual MachinesConsiderations for Implementing Hyper-V ClustersDemonstration: Implementing Virtual Machines on Clusters (optional)• Maintaining and Monitoring Virtual Machines in Clusters

Components of Hyper-V Clusters

Hyper-V cluster components:•Cluster nodes, must be physical computers•Cluster networks•Virtual networks• Storage for virtual machines•Virtual machines

Prerequisites for Implementing Hyper-V ClustersHardware requirements for cluster nodes and storage:• Server hardware • Network adapters • Storage adapters • Storage Software requirements for cluster nodes:• Must run either the x64-based version of Windows Server 2008 R2 or

Windows Server 2008, Enterprise or Datacenter Edition • Should have the same software updates and service packs • Must be either a full installation or a Server Core installation Network infrastructure requirements: • Network settings and IP addresses • DNS • Domain role • Account for administering the cluster

Implementing Failover Clustering for Hyper-V Virtual Machines1. Install and configure Windows Server 2012 2. Configure shared storage 3. Install the Hyper-V and failover clustering

features 4. Validate the cluster configuration 5. Create the cluster 6. Create a virtual machine on one of the

cluster nodes 7. Make the virtual machine highly available,

for existing virtual machine8. Test virtual machine failover

Configuring CSV

CSV benefits:• Fewer LUNs required• Better use of disk space• Virtual machine files are in a single logical

location• No special hardware required• Increased resiliency

To implement CSV: 1. Create and format volumes on shared

storage2. Add the disks to failover cluster storage3. Add the storage to the CSV

Configuring a Shared Virtual Hard Disk

• A failover cluster runs inside virtual machines• A shared virtual disk is used as shared storage if:• Virtual machines do not need access to iSCSI or failover

clustering SAN• Presented as a virtual serial attached SCSI disk• Used only for data

• Requirements for a shared virtual disk:• Virtual hard disk must be in VHDX format• Connected by using virtual SCSI adapter• Stored on a Scale-Out File Server or CSV

• Supported operating system in a virtual machine:• Windows Server 2012 or Windows Server 2012 R2

Shared Virtual Disk vs. Other Shared Storage Technologies

Capability Shared VHDX Virtual Fibre Channel

iSCSI

Supported storage Storage Spaces, serial attached

SCSI, Fibre Channel, iSCSI, SMB

Fibre Channel SAN iSCSI SAN

How storage is exposed in the virtual machine

Virtual serial attached SCSI

Virtual Fibre Channel LUN iSCSI LUN

Flows through the Hyper-V virtual switch No No Yes

Storage configured at the Hyper-V host Yes Yes No

Provides low latency and low CPU use

Yes (RDMA or Fibre Channel) Yes (Fibre Channel) No

Requires specific hardware No Yes No

Exposes storage architecture No Yes Yes

Comparing guest clustering options

Using Scale-Out File Servers Over SMB 3.0 for Virtual Machines• In Windows Server 2012 or newer, you can store virtual machine files on an SMB 3.0 file share• File servers should run Windows Server 2012 R2• File server cluster should run in Scale-Out File Server mode•Hyper-V Manager can be used to create or move virtual machine files to an SMB file share

Considerations for Implementing Hyper-V Clusters1. Identify the applications that require high

availability2. Identify the application components that must

be highly available 3. Identify the application characteristics 4. Identify the total capacity requirements 5. To create the Windows Server 2012 Hyper-V

design: • Verify basic requirements• Configure a dedicated network adapter for the private virtual network• Use similar host hardware• Verify network configuration

Demonstration: Implementing Virtual Machines on Clusters (optional)In this demonstration, you will see how to implement highly available virtual machines with failover clustering

Maintaining and Monitoring Virtual Machines in ClustersIn Windows Server 2012 failover clustering, you can implement the following technologies for virtual machine maintenance and monitoring:• Service and virtual machine health monitoring•Network health detection, for Windows Server 2012 R2 only•Virtual machine drain on shutdown, for Windows Server 2012 R2 only

Lesson 3: Implementing Hyper-V Virtual Machine MovementVirtual Machine Migration OptionsHow Does Virtual Machine and Storage Migration Work?Using ODX Capable Storage for Virtual MachinesHow Does Live Migration Work?How Does Hyper-V Replica Work?New Features of Hyper-V Replica in Windows Server 2012 R2•Demonstration: Implementing Hyper-V Replica (optional)

Virtual Machine Migration Options

Available options for moving virtual machines are:• Virtual Machine and Storage Migration• Quick Migration• Live Migration• Hyper-V Replica• Export or import of a virtual machine

How Does Virtual Machine and Storage Migration Work?Virtual Machine and Storage Migration technology enables you to move a virtual machine and its storage to another location without downtime• During migration, the virtual machine hard disk is copied from one location to another• Changes are written to both the source and destination drive• You can move virtual machine storage to the same host, another host, or an SMB share• Storage and virtual machine configuration can be in different locations

Using ODX Capable Storage for Virtual Machines

When using ODX capable storage you achieve following benefits:• Increase data

transfer• Minimize latency• Minimize hosts

resource usage while copying and migrating data

Intelligent Storage Array

Actual Data Transfer

TokenOffl

oad

Read

Token Token

Offload

Write

How Live Migration Works

Cluster Storage

Node 2 Node 1

How Does Hyper-V Replica Work?Hyper-V Replica in Windows Server 2012 enables you to replicate a single virtual machine over a WAN or LAN network to another hostHyper-V Replica components include:Replication engineChange trackingNetwork moduleHyper-V Replica Broker role

WAN linkSAN\NAS

Primary site

IISSQL

CRMFile

SAN\NAS

Replica site

Recovery virtual machines

SAN\NAS

Extended Replica site

Recovery virtual machines

Replication traffic

WAN link

Replication traffic

How to Configure Hyper-V Replica?

To configure Hyper-V Replica, you should:1. Configure authentication options2. Configure ports3. Select replica servers4. Select location for replica files5. Enable replication on virtual machine

New Features of Hyper-V Replica in Windows Server 2012 R2Hyper-V Replica in Windows Server 2012 R2 is enhanced with the following features:• The ability to change the replication frequency:• The available intervals are 30 seconds, 5 minutes, and 15 minutes

• Extended replication:• You can extend Hyper-V Replica to include a third host

Demonstration: Implementing Hyper-V Replica (optional)In this demonstration, you will see how to implement Hyper-V Replica

Lesson 4: Managing Hyper-V Virtual Environments by Using VMMWhat Is VMM?What Is New in VMM 2012 R2?Prerequisites for Installing VMMPrivate Cloud Infrastructure Components in VMMManaging Hosts and Host Groups with VMMDeploying Virtual Machines with VMMWhat Are Services and Service Templates?•Considerations for Deploying a Highly Available VMM Server

What Is VMM?

VMM provides centralized administration and management of your virtual environment and private cloudsVMM components are:• VMM server• Database• Management console• Library• Command shell• Self-Service Portal

What Is New in VMM 2012 R2?

The significant enhancements in VMM 2012 R2 are:• Enterprise-class performance:• Support for up to 1,000 hosts and 25,000 virtual machines

• Dynamic VHDX resize• Automatic upgrade of Hyper-V clusters with Live Migration

• Enhanced support for XenServer and VMware hosts• Simplified provisioning and migration:• Storage improvements• Bare metal provisioning• Multitenant cloud infrastructure• Provisioning a Windows Azure infrastructure

Prerequisites for Installing VMM

Software requirements for the VMM Server:• Windows Server 2008 R2 or newer• SQL Server 2008 SP2 or SQL Server 2008 R2 • Microsoft .NET Framework 3.5 SP1 or newer• Windows Assessment and Deployment Kit • Windows PowerShell 2.0, if the VMM Management Console will run

on the same server• WinRM 2.0

Hardware requirements:• CPU: Single core CPU 2 GHz • RAM: 4 – 8 GB• Disk space: 40 GB – 150 GB

The number of hosts determines the hardware requirements

Private Cloud Infrastructure Components in VMM

On the Fabric workspace of VMM management console, you can manage:•Servers:

• Hosts• Host Groups• PXE Servers• Update Servers

•Networking:• Logical Networks• IP Pools• MAC Pools• Load Balancers

•Storage:• Classifications• Pools• Providers• Arrays

Managing Hosts and Host Groups with VMM

• Host group scenarios:• Provide basic organization when managing large numbers of

hosts• Reserve resources for use by hosts• Designate hosts on which a user can create and operate

their own virtual machines• Create private clouds

• Host groups simplify management tasks by using a single action to apply settings to multiple hosts

• VMM can deploy and manage Hyper-V hosts, Hyper-V clusters, and host groups

Deploying Virtual Machines with VMM

In VMM, there are several ways that you can create and deploy a new virtual machine:• Create a new virtual machine from an empty hard disk• Create a new virtual machine based on a pre-defined template• Deploy a new virtual machine from the VMM library

What Are Services and Service Templates?• In terms of VMM clouds, a service is a set of one or more virtual machines that are deployed together and managed as a single entity

• A service template encapsulates all neccessary components required to deploy and run a new instance of an application• A service is deployed by an administrator or end-user

• A service can contain several different components• A service can be deployed to a private cloud or to host group

• An administrator creates a service template in VMM • An application owner deploys a service based on the service template

• App Controller or VMM Manager console can be used to deploy service based on template

Considerations for Deploying a Highly Available VMM ServerThe considerations for deploying a highly available VMM are:• VMM is cluster-aware and can be highly

available•When deploying VMM in a cluster, the service account must be the domain account •Use Distributed Key Management for encryption keys•Make database and library servers highly available •Do not install a Self-Service Portal on a clustered VMM server•Use the Failover Cluster Manager to perform a planned failover

Lab: Implementing Failover Clustering with Hyper-VExercise 1: Configuring Hyper-V ReplicasExercise 2: Configuring a Failover Cluster for Hyper-V•Exercise 3: Configuring a Highly Available Virtual Machine

Logon InformationVirtual machines: 20412C-LON-DC1-B

20412C-LON-SVR1-BUser name: Adatum\administratorPassword: Pa$$w0rd

Estimated Time: 75 minutes

Lab Scenario

The initial deployment of virtual machines on Hyper-V has been successful for A. Datum. As a next step in the deployment, A. Datum is considering ways to ensure that the services and applications deployed on the virtual machines are highly available. As part of the implementation of high availability for most network services and applications, A. Datum also is considering options for making the virtual machines that run on Hyper-V highly available.As one of the senior network administrators at A. Datum, you are responsible for integrating Hyper-V with failover clustering to ensure that the virtual machines deployed on Hyper-V are highly available. You are responsible for planning the virtual machine and storage configuration, and for implementing the virtual machines as highly available services on the failover cluster. You also are considering other techniques, such as Hyper-V Replica, for ensuring high availability for virtual machines.

Lab Review

How can you extend Hyper-V Replica in Windows Server 2012 R2?•What is the difference between Live Migration and Storage Migration?