Implementing Failover Clustering with Hyper-V Module 6 Implementing Failover Clustering with Hyper-V

20409A Module Overview 6: Implementing Failover Clustering with Hyper-V Implementing and Managing Failover Clustering with Hyper-V

Lesson 1: Configuring and Using Shared Storage 6: Implementing Failover Clustering with Hyper-V Using Virtual Hard Disk Sharing as Shared Storage

Storing A Virtual Machine on an SMB 3.0 Shared Folder 6: Implementing Failover Clustering with Hyper-V Hyper-V supports SMB 3.0 or newer Hyper-V uses file share is used as cluster shared storage Continuously available shares are recommended All virtual machine storage can be on an SMB share Configuration, virtual hard disks, checkpoints SMB Share – Applications profile should be used No access-based enumeration or share caching Full permissions on NTFS folder and SMB share Hyper-V administrators Computer account of Hyper-V host Hyper-V cluster computer account, if Hyper-V clustered

Using Scale-Out File Server 6: Implementing Failover Clustering with Hyper-V File server role cluster can work in two modes: Scale-out file server cluster File server cluster for general use Benefits of scale-out file server cluster: Active-Active file shares Increased bandwidth CHKDSK with zero downtime CSV cache Simple management Automatic scale-out rebalancing Clients redirected to the best node for access to a share Avoids unnecessary traffic redirection

What is iSCSI? Client-server SCSI transport protocol Compares with MPIO & VAMP 6: Implementing Failover Clustering with Hyper-V Client-server SCSI transport protocol Sends SCSI commands over IP networks Any SCSI device can be accessed Windows Server supports only block storage Block storage device is presented Used as locally attached disk iSCSI target is Windows Server role service Can be added as failover cluster role Multipath I/O for redundancy iSCSI initiator is part of Windows client and Windows Server operating systems iSCSI client runs iSCSI initiator TCP/IP protocol iSCSI target storage array

What is an iSCSI Target Server? 6: Implementing Failover Clustering with Hyper-V Virtual disks use the .vhdx format Presented to iSCSI initiators as SCSI logical units Limit initiators that can access logical units Fixed size, dynamically expanding, or differencing Clear the virtual disk on allocation Size can be up to 64 TB Can extend and shrink virtual disks online Enables application-consistent snapshots Includes Storage Management Initiative – Specification provider Standards-based management Enables discovery and storage-based management

Using Virtual Hard Disk Sharing as Shared Storage 6: Implementing Failover Clustering with Hyper-V A failover cluster runs inside virtual machines A shared virtual disk used as a shared storage Virtual machines do not need access to iSCSI or FC SAN Presented as virtual SAS disk Can be used only for data Requirements for shared virtual disk Virtual hard disk must be in .vhdx format Connected by using a virtual SCSI adapter Stored on a scale-out file server or CSV Supported operating systems in a virtual machine Windows Server 2012 or Windows Server 2012 R2

Lesson 2: Implementing & Managing Failover Clustering with Hyper-V 6: Implementing Failover Clustering with Hyper-V What Is CAU? What is Live Migration?

Overview of Failover Cluster Compares with VMware HA 6: Implementing Failover Clustering with Hyper-V Up to 64 physical servers and 6,000 VMs Built-n hardware and software validation Shared storage using SMB, iSCSI, Fibre Channel, Fibre Channel over Ethernet (FCoE) or Serial-Attached SCSI (SAS) Node 1 Node 2 Node 3… …Node 64 Cluster Shared Volumes (CSV) on Shared Storage

Configuring Highly Available Virtual Machines 6: Implementing Failover Clustering with Hyper-V High Availability Wizard Virtual machine storage is on shared storage CSV or SMB 3.0 continuously available share Virtual machine startup priority Higher priority is started before lower priority No auto start, must restart manually after failover Preferred owners Virtual machine will start on preferred Hyper-V host Start on possible owner only preferred owners are unavailable If preferred and possible owners are unavailable, virtual machine will move to other failover cluster node, but not start

Configuring Highly Available Virtual Machines 6: Implementing Failover Clustering with Hyper-V AntiAffinityClassNames Clustered roles in same AntiAffinityClassNames avoid same cluster node Prevents virtual machines from running on the same node Configured in Windows PowerShell or System Center 2012 Virtual Machine Manager Options to modify failover and failback settings Number of times to restart a clustered role Prevent failback of the clustered role to preferred node Virtual machine Policies settings Virtual machine Heartbeat monitoring Requires integration services in virtual machine

Virtual Machine Monitoring Compares with VMware App HA 6: Implementing Failover Clustering with Hyper-V Application health detection in virtual machine Monitor services through Service Control Manager Configure service recovery to take no action Monitor events in System, Application, or Security logs Windows Server 2012 or newer required Configurable recovery actions Restart service Restart virtual machine Fail over virtual machine Virtual machine network and storage protection Failure of virtual hard disk or lost network connectivity Virtual machine moved to different cluster node

What Is the Hyper-V Replica Broker Role? 6: Implementing Failover Clustering with Hyper-V ServerA Server1 ServerB Server2 ServerC Replica broker Server3 Failover cluster 1 Failover cluster 2

What is Live Migration? Utilizes available CPU resources on the host to perform compression Compressed memory sent across the network faster Operates on networks with less than 10 gigabit bandwidth available Enables a 2X improvement in Live Migration performance VM VM VM MEMORY MEMORY Memory content Configuration data Modified memory pages IP connection Target host iSCSI, FC or SMB Storage

Course Summary End of Day 1 20409A 13: Protecting and Monitoring Virtualization Infrastructure End of Day 1 Course Summary

What have we learned about Hyper-V? Summary What have we learned about Hyper-V? Host & Virtual Machine Configuration with inbox tools Resilient Hyper-V Infrastructure with Failover Clustering Virtual Machine Migration, Backup & Replication What will we learn about System Center? Hyper-V Host & Cluster Deployment & Configuration with VMM Managing Storage & Networking with VMM Templates & Service Templates Value-Add of Remaining System Center Components

Resources Hyper-V Overview - http://technet.microsoft.com/library/hh831531 Competitive Advantages of Hyper-V - http://download.microsoft.com/download/E/8/E/E8ECBD78-F07A-4A6F- 9401-AA1760ED6985/Competitive-Advantages-of-Windows-Server-Hyper-V-over-VMware-vSphere.pdf Technical Documentation | Virtual Machine Manager: http://www.microsoft.com/en- us/download/details.aspx?id=6346 Technical Documentation | App Controller: http://www.microsoft.com/en-us/download/details.aspx?id=29694 Technical Documentation | Operations Manager: http://www.microsoft.com/en- us/download/details.aspx?id=29256 Technical Documentation | Data Protection Manager: http://www.microsoft.com/en- us/download/details.aspx?id=29698 Technical Documentation | Service Manager: http://www.microsoft.com/en-us/download/details.aspx?id=27850 Technical Documentation | Orchestrator: http://www.microsoft.com/en-us/download/details.aspx?id=29258 Cloud Services Process Pack Download: http://www.microsoft.com/en-us/download/details.aspx?id=36497 Microsoft Virtual Machine Converter Download: http://www.microsoft.com/en- us/download/details.aspx?id=34591 System Center PowerShell Deployment Toolkit: http://gallery.technet.microsoft.com/PowerShell-Deployment- 797b3c6d

Download evaluation software Learn more Next Steps Come back tomorrow! Download evaluation software http://aka.ms/CampEval Learn more http://aka.ms/CampMVAWS http://aka.ms/CampMVASC http://www.microsoft.com/learning/en-us/course.aspx?ID=20409A&Locale=en-us Get certified http://www.microsoft.com/learning/en-us/exam.aspx?id=74-409

4/19/2017 © 2013 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. © 2010 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.