Microsoft Jump Start

M9: Implementing Failover Clustering with Hyper-V

Rick Claus | Technical Evangelist | Microsoft Ed Liberman | Technical Trainer | Train Signal

Jump Start Target Agenda | Day One

Day 1 Day 2

Module 1: Installing and Configuring Servers Based on Windows Server 2012

Module 2: Monitoring and Maintaining Windows Server 2012 Module 3: Managing Windows Server 2012 by Using PowerShell 3.0 - MEAL BREAK Module 4: Managing Storage for Windows Server 2012

Module 7: Implementing Failover Clustering

Module 8: Implementing Hyper-V Module 9: Implementing Failover Clustering with Hyper-V - MEAL BREAK Module 10: Implementing Dynamic Access Control

Module 5: Implementing Network Services

Module 11: Implementing Active Directory Domain Services

Module 6: Implementing Direct Access Module 12: Implementing Active Directory Federation Services

Module Overview
Overview of the Integration of Hyper-V with

Failover Clustering Implementing Hyper-V Virtual Machines on Failover Clusters Implementing Hyper-V Virtual Machine Movement Managing Hyper-V Virtual Environments by Using System Center Virtual Machine Manager

Options for Making Virtual Machines Highly Available

High Availability options Description
Virtual machines are highly available
Does not require virtual machine operating

Host clustering

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 Failover Clusters Work with Hyper-V Nodes?

Shared Bus or iSCSI Connection

Cluster Storage

Node 1

A dedicated network connects the failover cluster nodes

Node 2

Whats New in Failover Clustering for Hyper-V in Windows Server 2012?

Support for up to 4000 8000 virtual machines per

cluster Multi select virtual machines for Live Migration Virtual machine priority attribute CSV improvements Virtual machine application monitoring Storing virtual machines on highly available SMB file share

Best Practices for Implementing High Availability in a Virtual Environment

Use Windows Server 2012 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

Components of Hyper-V Clusters

Cluster nodes (must be physical computers) Cluster networks Virtual networks

Storage for virtual machines

Virtual machines

Requirements for Failover Clustering in Hyper-V

Hardware requirements: Cluster nodes & storage Server hardware & Storage Network adapters & storage adapters Software requirements: Cluster nodes Must run either Server Standard or Server Datacenter (or Hyper-V Server 2012) Should have same software updates & service packs Must be either full installation or Server Core installation Network infrastructure requirements Network settings and IP addresses DNS & Domain role Account for administering the cluster

Implementing Hyper-V VMs on Failover Cluster

1) Install and configure Windows Server 2012 2) Configure shared storage 3) Install the Hyper-V and failover clustering 4) 5)

6)
7)

features Validate the cluster configuration Create the cluster Create a virtual machine on one of the cluster nodes Make the virtual machine highly available

Configuring Clustered Shared Volumes

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: Create and format volumes on shared storage. Add the disks to failover cluster storage. Add the storage to the CSV.

Implementing Highly Available Virtual Machines on an SMB 3.0 File Share

In Windows Server 2012 you can store VM files on

SMB 3.0 file share File servers should be running Windows Server 2012 File server cluster should be running in scale-out mode Hyper-V Manager can be used to create or move virtual machine files to SMB file share

Considerations for Implementing Hyper-V Clusters

Identify applications that require high availability Identify application components that must be

highly available Identify the application characteristics Identify the total capacity requirements Create the Hyper-V design
1)
2) 3) 4) 5)

Verify basic requirements Configure a dedicated network adapter for the private virtual network Use similar host hardware Verify network configuration Manage Live Migrations

Virtual Machine Migration Options

Virtual machine and storage migration Quick Migration Live Migration

Hyper-V replica
Export/Import of a virtual machine

How Does Virtual Machine and Storage Migration Work? Storage Migration technology enables you to move a virtual machine and its storage to another location without downtime
During

migration the virtual machine hard drive is copied from one location to another Changes are written to both source and destination drive You can move virtual machine storage to same host, another host, or server message block share Storage and virtual machine configuration can be in different locations

How Does Live Migration Work?

Cluster Storage

Node 1

Node 2

How Does Hyper-V Replica Work?

Enables you to replicate a single virtual machine

over WAN or LAN network to another host Hyper-V replica components:

Replication

Engine Change Tracking Network Module Hyper-V Replica Broker role

Configuring Hyper-V Replica

1) Configure authentication options 2) Configure ports 3) Select replica servers

4) Select location for replica files

5) Enable replication on virtual machine