20417a_09.pdf
TRANSCRIPT
-
7/27/2019 20417A_09.pdf
1/19
MicrosoftJump Start
M9: Implementing FailoverClustering with Hyper-V
Rick Claus | Technical Evangelist | MicrosoftEd Liberman | Technical Trainer | Train Signal
-
7/27/2019 20417A_09.pdf
2/19
Jump Start Target Agenda | Day One
Day 1 Day 2
Module 1: Installing and ConfiguringServers Based on Windows Server2012
Module 7: Implementing FailoverClustering
Module 2: Monitoring andMaintaining Windows Server 2012
Module 8: Implementing Hyper-V
Module 3: Managing Windows Server2012 by Using PowerShell 3.0
Module 9: Implementing FailoverClustering with Hyper-V
- MEAL BREAK - - MEAL BREAK -
Module 4: Managing Storage forWindows Server 2012
Module 10: Implementing DynamicAccess Control
Module 5: Implementing NetworkServices
Module 11: Implementing ActiveDirectory Domain Services
Module 6: Implementing Direct Access Module 12: Implementing ActiveDirectory Federation Services
-
7/27/2019 20417A_09.pdf
3/19
Module Overview
Overview of the Integration of Hyper-V withFailover Clustering
Implementing Hyper-V Virtual Machines onFailover Clusters
Implementing Hyper-V Virtual Machine Movement
Managing Hyper-V Virtual Environments by UsingSystem Center Virtual Machine Manager
-
7/27/2019 20417A_09.pdf
4/19
Options for Making Virtual Machines HighlyAvailable
High Availability
options
Description
Host clustering Virtual machines are highly available
Does not require virtual machine operatingsystem or application to be cluster aware
Guest clustering Virtual machines are failover cluster nodes
Virtual machine applications must be clusteraware
Requires iSCSI or virtual fiber channelinterface for shared storage connections
NLB Virtual machines are NLB cluster nodes
Use for web-based applications
-
7/27/2019 20417A_09.pdf
5/19
Node 2Node 1
How Failover Clusters Work with Hyper-V Nodes?
Shared Bus oriSCSI Connection
A dedicated networkconnects the
failover cluster nodes
Cluster
Storage
-
7/27/2019 20417A_09.pdf
6/19
Whats New in Failover Clustering for Hyper-V inWindows Server 2012?
Support for up to 4000 8000 virtual machines percluster
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
-
7/27/2019 20417A_09.pdf
7/19
Best Practices for Implementing High Availability in aVirtual 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 quorummode
Deploy standardized Hyper-V hosts
Develop standard management practices
-
7/27/2019 20417A_09.pdf
8/19
Components of Hyper-V Clusters
Cluster nodes (must be physical computers)
Cluster networks
Virtual networks
Storage for virtual machines
Virtual machines
-
7/27/2019 20417A_09.pdf
9/19
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 (orHyper-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
-
7/27/2019 20417A_09.pdf
10/19
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 clusteringfeatures
4) Validate the cluster configuration
5) Create the cluster
6) Create a virtual machine on one of the cluster
nodes7) Make the virtual machine highly available
-
7/27/2019 20417A_09.pdf
11/19
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.
-
7/27/2019 20417A_09.pdf
12/19
Implementing Highly Available Virtual Machines onan SMB 3.0 File Share
In Windows Server 2012 you can store VM files onSMB 3.0 file share
File servers should be running Windows Server2012
File server cluster should be running in scale-outmode
Hyper-V Manager can be used to create or move
virtual machine files to SMB file share
-
7/27/2019 20417A_09.pdf
13/19
Considerations for Implementing Hyper-V Clusters
Identify applications that require high availability
Identify application components that must behighly available
Identify the application characteristics
Identify the total capacity requirements
Create the Hyper-V design1) Verify basic requirements
2) Configure a dedicated network adapter for the privatevirtual network
3) Use similar host hardware
4) Verify network configuration
5) Manage Live Migrations
-
7/27/2019 20417A_09.pdf
14/19
Virtual Machine Migration Options
Virtual machine and storage migration
Quick Migration
Live Migration
Hyper-V replica
Export/Import of a virtual machine
-
7/27/2019 20417A_09.pdf
15/19
How Does Virtual Machine and Storage MigrationWork?
Storage Migration technology enables you to movea virtual machine and its storage to anotherlocation without downtime
During migration the virtual machine hard drive iscopied from one location to another
Changes are written to both source and destinationdrive
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
-
7/27/2019 20417A_09.pdf
16/19
How Does Live Migration Work?
Node 2Node 1
Cluster
Storage
-
7/27/2019 20417A_09.pdf
17/19
How Does Hyper-V Replica Work?
Enables you to replicate a single virtual machineover WAN or LAN network to another host
Hyper-V replica components: Replication Engine
Change Tracking Network Module
Hyper-V Replica Broker role
-
7/27/2019 20417A_09.pdf
18/19
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
-
7/27/2019 20417A_09.pdf
19/19