Module 12

Implementing failover clustering

with Windows Server 2016 Hyper-V
Module Overview

Overview of the integration of Hyper-V

Server 2016 with failover clustering
Implementing Hyper-V virtual machines on failover
clusters
Implementing Windows Server 2016 Hyper-V
virtual machine migration
• Implementing Hyper-V Replica
Lesson 1: Overview of the integration of Hyper-V
Server 2016 with failover clustering

Options for making applications and services highly

available
How does a failover cluster work with Hyper-V
nodes?
Failover clustering with Windows Server 2016
Hyper-V features
• Best practices for implementing high availability in
a virtual environment
Options for making applications and services
highly available
High-availability Description
options

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 Fibre 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?

Shared bus or
iSCSI connection

Cluster
storage

A dedicated network
Node connects the Node
1 failover cluster nodes 2
Failover clustering with Windows Server 2016
Hyper-V features

• Failover clustering with Windows Server 2016

Hyper-V features:
• Maximum nodes and virtual machine support
• File share storage:
• vhds (Windows Server 2016 only)
• .vhdx (Windows Server 2012 R2 and Windows Server 2016 only)
• Shared virtual disk
• Rolling Hyper-V cluster upgrades
• Virtual machine configuration version
Best practices for implementing high availability
in a virtual environment
• Plan for failover scenarios
• Plan the network design for failover clustering
• Plan the shared storage for failover clustering
• Use the default failover cluster quorum mode
• Deploy standardized Hyper-V hosts
• Develop standard management practices
Lesson 2: Implementing Hyper-V virtual machines
on failover clusters

Components of Hyper-V clusters

Prerequisites for implementing Hyper-V failover
clusters
Implementing Hyper-V virtual machines on a
failover cluster
Configuring CSVs
Configuring a shared virtual hard disk
Implementing Scale-Out File Server for virtual
machines
Considerations for implementing Hyper-V clusters
• Maintaining and monitoring virtual machines in
Components of Hyper-V clusters

Hyper-V cluster components include:

• Cluster nodes
• Cluster networks
• Virtual networks
• Storage for virtual machines
• Virtual machines
Prerequisites for implementing Hyper-V failover
clusters
• Hardware requirements for cluster nodes and storage:
• Server hardware
• Network adapters
• Storage adapters
• Storage
• Software recommendations for cluster nodes:
• Should run either Windows Server 2016 Standard, Datacenter, or
Microsoft Hyper-V Server 2016 editions
• Require 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
• Private networks
• DNS
• Domain role
• Account for administering the cluster
Implementing Hyper-V virtual machines on a
failover cluster

To implement a Hyper-V virtual machine on a

failover cluster:
1. Install and configure Windows Server 2016
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 in one of the cluster nodes
7. Make the virtual machine highly available (for an
existing virtual machine)
8. Test virtual machine failover
Configuring CSVs

• 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 storage
2. Add the disks to failover cluster storage
3. Add the storage to the CSV
Configuring a shared virtual hard disk

• Failover cluster runs inside virtual machines

• Shared virtual hard disk used as a shared storage:
• Virtual machines do not need access to iSCSI or failover
clustering SAN
• Presented as a virtual SAS disk
• Can be used only for data

• Requirements for a shared virtual hard disk:

• Must be in the .vhdx or .vhds format
• Connected by using a virtual SCSI adapter
• Stored on a Scale-Out File Server or CSV
• Supported operating system in a virtual machine:
• Windows Server 2012 R2 or later
Configuring a shared virtual hard disk
Shared virtual hard disk compared to other shared storage technologies:
Capability Shared .vhdx and Virtual Fibre Channel ISCSI in virtual
.vhds machine
Supported storage Storage spaces, SAS, Fibre Channel SAN iSCSI SAN
Fibre Channel, iSCSI,
SMB
Storage is presented to the Virtual SAS Virtual Fibre Channel iSCSI LUN
virtual machine through LUN
Data flows through the No No Yes
Hyper-V switch
Storage is configured at the Yes Yes No
Hyper-V host level
Provides low latency and low Yes (remote direct Yes (Fibre Channel) No
CPU use memory access [RDMA]
or Fibre Channel)
Requires specific hardware No Yes No
Requires switch to be No Yes No
reconfigured when virtual
machine is migrated
Implementing Scale-Out File Server for virtual
machines

• In Windows Server 2016, you can store virtual

machine files on a SMB 3.0 file share
• File servers should be running Windows
Server 2012 or later
• File server cluster should be configured as a
Scale-Out File Server for application data
• Use Hyper-V Manager to create or move virtual
machine files to a SMB file share
Considerations for implementing Hyper-V clusters

• Use the following recommended failover clustering

requirements:
• Identify the applications that require high availability
• Identify the application components that must be highly
available
• Identify the application characteristics
• Identify the total capacity requirements
• Windows Server 2016 Hyper-V Live Migration
considerations:
• Verify basic requirements
• Configure a dedicated network adapter or virtual network
adapter
• Use similar host hardware
• Verify network configuration
Maintaining and monitoring virtual machines in
clusters

In Windows Server 2016 failover clustering, you

can implement the following technologies for
virtual machine maintenance and monitoring:
• Service and virtual machine health monitoring
• Network health detection (Windows Server 2012 R2 and
later only)
• Virtual machine drain on shutdown (Windows
Server 2012 R2 and later only)
Lesson 3: Implementing Windows Server 2016
Hyper-V virtual machine migration

Virtual machine migration options

How Storage Migration works
• How Live Migration works
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 Storage Migration works

• Storage migration technology allows 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
drives
• 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
How Live Migration works

Cluster
storage

Node Node
1 2
Lesson 4: Implementing Hyper-V Replica

What is Hyper-V Replica?

Hyper-V Replica in Windows Server 2016
Configuring Hyper-V Replica
• Failover with Hyper-V Replica
What is Hyper-V Replica?
Hyper-V Replica in Windows Server 2016 enables you to replicate a
single virtual machine over a WAN or LAN network to another host
Hyper-V Replica components include:
• Replication Engine
• Change Tracking
• Network Module
• Hyper-V Replica Broker role

Recovery
SQL CRM virtual machines
Server File Replication traffic
IIS

WAN link SAN\NAS

SAN\NAS

Replica site
Primary site
Hyper-V Replica in Windows Server 2016

Hyper-V Replica in Windows Server 2016 and

Windows Server 2012 R2 is enhanced with the
following features:
• Ability to change the replication frequency:
• Available intervals are 30 seconds, 5 minutes, and 15
minutes
• Extended replication:
• You can extend Hyper-V Replica to include a third host
Configuring Hyper-V Replica

To configure Hyper-V Replica, you should:

1. Configure authentication options
2. Configure ports
3. Select replica servers
4. Select a location for replica files
5. Enable replication on a virtual machine
Failover with Hyper-V Replica

• Test failover:
• Is nondisruptive testing with zero downtime
• Creates a new virtual machine in the recovery site from the
replica checkpoint and is turned off and not connected
• Allows you to stop a test failover

• Planned failover:
• Failover moves a turned-off primary virtual machine to a replica
site
• Primary virtual machine sends data that has not been replicated
• Planned failover fails over the virtual machine to the replica
server and starts the replica virtual machine
• Replication should be reversed after the primary site is restored
• Failover:
• Is performed in the event that an occurrence disrupts the
primary site
Lab: Implementing failover clustering with
Windows Server 2016 Hyper-V
Exercise 1: The Hyper-V Failover clustering testing
environment
Exercise 2: Configuring Hyper-V Replica
Exercise 3: Configuring a failover cluster for Hyper-V
• Exercise 4: Configuring a highly available virtual
machine
Logon Information
Virtual machines: 20743B-LON-HOST2
20743B-LON-DC1-C
User name: Adatum\Administrator
Password: Pa55w.rd

Estimated Time: 75 minutes

Lab Scenario

The initial deployment of virtual machines on Hyper-V has been

successful for A. Datum Corporation. As a next step in virtual machine
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 is also 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. You have limited hardware; so to
facilitate testing before implementation in your production
environment, you will enable nested virtualization to test clustering
two Hyper-V Hosts and Hyper-V Replica without using physical
Lab Review

How can you extend Hyper-V Replica in Windows

Server 2016?
• What is the difference between Live Migration and
Storage Migration?
Module Review and Takeaways

Review Questions
Tools
Best Practices
• Common Issues and Troubleshooting Tips
Course Evaluation

• Your evaluation of this course will help Microsoft

understand the quality of your learning
experience.
• Please work with your training provider to access
the course evaluation form.
• Microsoft will keep your answers to this survey
private and confidential and will use your
responses to improve your future learning
experience. Your open and honest feedback is
valuable and appreciated.