Module 6

Module 6Implementing Failover Clustering with Hyper-V

Microsoft Official CoursePresentation: 90 minutesLab: 60 minutesAfter completing this module, students will be able to:Describe failover clustering.Configure and use shared storage.Implement and manage failover clustering with Hyper-V.Required MaterialsTo teach this module, you need the Microsoft Office PowerPoint file 20409A_06.pptx.Important: We recommend that you use Office PowerPoint 2007 or newer to display the slides for this course. If you use PowerPoint Viewer or an older version of PowerPoint, all the features of the slides might not display correctly.Preparation TasksTo prepare for this module:Read all of the materials for this module.Practice performing the lab exercises.Work through the Module Review and Takeaways section, and determine how you will use this section to reinforce student learning and promote knowledge transfer to on-the-job performance.120409A6: Implementing Failover Clustering with Hyper-VModule OverviewOverview of Failover ClusteringConfiguring and Using Shared StorageImplementing and Managing Failover Clustering with Hyper-VList lessons in this module and briefly explain the content that each lesson covers. Briefly mention that Hyper-V does not include high availability, but it uses failover clustering as a mechanism for providing highly available virtual machines.220409A6: Implementing Failover Clustering with Hyper-VLesson 1: Overview of Failover ClusteringWhat Is A Failover Cluster?What are Failover and Failback?Failover Cluster NetworksFailover Cluster StorageWhat Is CSV?What Is a Quorum?What Is Encrypted Cluster Volume?List the topics in this lesson and provide a brief overview of the content each topic covers. If students are familiar with failover clustering, ask them if they are aware of the new features that Windows Server 2012 R2 introduces. If they do not have experience with failover clustering, spend some more time covering its basics such as failover clustering components and different quorum models.320409A6: Implementing Failover Clustering with Hyper-VWhat Is A Failover Cluster?

Node 1Node 2Cluster storageClientsA dedicated network connects the nodesA network connects the failover cluster and clientsShared bus or iSCSI connection

Clustered role highlyavailable serviceExplain to students the basic principles of failover clustering, and how it provides high availability. Describe each component and emphasize the importance of redundancy, for example, power supplies and multiple network paths between nodes and the storage. Point out that the cluster role is running on a single node and if that node fails, the cluster role moves to a different node. Ask students if they have failover clusters implemented in their environment. Based on the failover cluster description, ask them why it is important to use Hyper-V with failover clustering.QuestionWill clients still be able to connect to a cluster role if the failover cluster has only two nodes and the internode network fails?AnswerYou should plan your failover cluster in such a way that it provides redundancy, and that the internode network never fails. If the internode network were to fail, the nodes will not be able to communicate or participate in the voting process, although they will still have access to the shared storage and to the clients. Depending on the quorum model, it is possible that a single node will continue to run the cluster role and clients will still be able to connect to it.420409A6: Implementing Failover Clustering with Hyper-VWhat are Failover and Failback?When a node fails, application is moved to a different nodeOperation is called failoverDuring failover, all associated resources are movedFailover occurs when:Node that hosts the application cannot be accessedOne of the application resources failsAdministrator forces a failover Failback is moving an application backAfter the failed node becomes active againCan be automatic or manual

Explain to students that failover and failback are related operations. Failover moves cluster role from the failed node to a different node, and failback returns the cluster role back to the original node, when it is back online. Describe the steps that are performed during failover. Briefly explain the configuration options that you can set to control failover. Provide examples such as setting how often failover can happen, and whether you want failback to happen immediately when the failed node is back online. Mention also the preferred owner list as a way to control which nodes the cluster role can run on.QuestionDoes failback always follow failover when the failed node is back online?AnswerNo, not necessarily. After the failover process moves the cluster role to a different cluster node, the cluster role may stay on that node and not fail back, even when the failed node is back online. This depends on the configuration settings. Furthermore, the administrator may decide to trigger failback manually or not at all.520409A6: Implementing Failover Clustering with Hyper-VFailover Cluster NetworksHave at least two network paths between nodesMultiple (fast) network cards are recommendedCan use NIC Teaming and virtual network adaptersCluster Network Types:Allow cluster network communication on this networkAllow clients to connect through this networkDo not allow cluster network communicationSingle network can support intranode and clientsNot recommendedMicrosoft Failover Cluster Virtual AdapterFault-tolerant connections across all available interfacesSimilar to an internal NIC Teaming for clusteringAsk students why a failover cluster should have multiple network paths between the nodes. Ask them also if you can create additional network paths by adding only additional network adapters, or if there is some other way to create additional network paths. (Remind them about virtual network adapters.) Emphasize that as a best practice, each node should have at least two physical adapters, although this is not a technical requirement. Describe the Microsoft Failover Cluster Virtual Adapter and its benefits. If students have more in-depth questions, you can suggest that they consult the additional reading materials.QuestionDo you need to manually put network adapters in a failover clustering node in a NIC team?AnswerNo, you do not need to manually put network adapters in a NIC team. When you install the failover clustering feature, the Microsoft Failover Cluster Virtual Adapter is created, which is hidden, but it can utilize all paths between the nodes as long as they are physically available.620409A6: Implementing Failover Clustering with Hyper-VFailover Cluster StorageShared storage provides consistent dataWhen node fails, application data is still availableMultiple nodes can access shared storageShared storage options include:SASiSCSIFibre Channel Fiber Channel over EthernetSMB 3.0 file sharesOnly for Hyper-V, not failover clusterConsider using CSV for shared storage

Explain the use of shared storage in failover clusters, and how it enables the node to which the cluster role is moved, to continue from the point where the failed node stops. List different shared storage options, their benefits, and when you would use them. Mention that Fibre Channel and Internet small computer system interface (iSCSI) are most popular, but iSCSI typically has lower costs. Point out that Hyper-V can also use server message block (SMB) 3.0 file shares as a shared storage for virtual machines. Mention that you would use Cluster Shared Volume (CSV) for shared storage, but do not go into details, because there is a separate topic on CSV.QuestionCan you use a network-attached storage (NAS) device as a shared storage for a failover cluster?AnswerIt depends. Some NAS devices provide only filelevel access, whereas others provide blocklevel access (or both). If a network-attached storage (NAS) device provides blocklevel access, you can use it as a shared storage.720409A6: Implementing Failover Clustering with Hyper-VWhat Is CSV?LUN is owned by single node at any timeMultiple nodes can access a CSV simultaneouslyApplication failover without drive ownership changeConcurrent access to a single file systemSingle consistent file namespace across cluster nodesBetter use of disk space Virtual machine resources in a single logical locationNo special hardware is requiredSimple CSV setupHyper-V, SQL Server and file server can use CSVUse Storage Spaces to deploy CSVDeduplication and tiered storage spaces are supportedExplain the benefits of CSV as compared to logical unit numbers (LUNs). Point out that CSV was first supported in Windows Server 2008 R2. Windows Server 2012 and Windows Server 2012 R2 include important improvements to CSV, such as support for additional cluster roles aside from Hyper-V, and CSV caching. Mention that CSV enables multiple nodes to access the same file system simultaneously, and it is used by the scale-out file server cluster role.QuestionCan you format a CSV by using CSV file system?AnswerAlthough CSVs on Windows Server 2012 and Windows Server 2012 R2 appear as though they are formatted with the CSV file system, they are actually formatted with NTFS file server. CSV file system is used to make the application aware that it is running in a failover cluster and stored on a CSV, but CSV file system is not the actual file system.820409A6: Implementing Failover Clustering with Hyper-VWhat Is a Quorum?Consensus that enough nodes are availableMore than half of all votesBased on votesNodes, file share, and disk can have a voteCluster online, when a quorum has more than 50 percent of the votes Quorum modes:Node MajorityNode and Disk MajorityNode and File Share MajorityNo Majority: Disk OnlyExplain the concept of a quorum, and its importance for failover clusters. Point out the elements that can participate with their vote, and the quorum modes that failover clustering supports. Point out that the quorum mode No Majority: Disk Only is a legacy quorum mode, and it should be avoided because it presents a single point of failure. Discuss the quorum mode enhancements in Windows Server 2012 and Windows Server 2012 R2. Explain node weight, dynamic quorum model, and dynamic witness, and provide examples of each.QuestionCan a failover cluster that originally had six nodes still run cluster roles if three nodes fail and only three nodes are left online?AnswerIt depends. Based on the quorum model used, and whether all three nodes failed at once or there was some time between each failure, the remaining three nodes might still run cluster roles. The nodes must also have enough resources and use the dynamic quorum model, which is the default.920409A6: Implementing Failover Clustering with Hyper-VWhat Is a Quorum?Node weightCan configure so not all nodes have a voteUseful in multisite cluster scenariosWorks with all quorum modes except Disk OnlyDynamic QuorumNumber of votes is adjusted dynamically Cluster can be available with less than 50% votesEnabled by defaultWorks with all quorum modes, except Disk OnlyTie breaker for 50 percent node splitDynamic witness1020409A6: Implementing Failover Clustering with Hyper-VWhat Is Encrypted Cluster Volume?BitLocker-encrypted cluster disksSupport for traditional failover disks and CSVCan be enabled before or after a disk is added Add the failover cluster AD DS identity as a BitLocker protector to the target disk volumesMinimal performance impact RequirementsWindows Server 2012 or newer failover clusteringWindows Server 2012 domain controller is accessible from all nodesBitLocker is installedBitlocker PowerShell module or Manage-BDEIntroduce encrypted cluster volumes. Explain that you use BitLocker drive encryption for encrypting the volume, and that Active Directory Domain Services (AD DS) stores the decryption key with the failover cluster computer object. Point out that this is a new feature in Windows Server 2012 and newer operating systems. List the requirements to be able to use this feature. Mention also that encrypted cluster volumes introduces minimal performance overhead of less than one percent.QuestionCan you protect data on shared storage by using an encrypted cluster volume if the failover cluster is a member of an ADDS domain with Windows Server 2008 R2 domain-functional level?AnswerIf the domain has at least one domain controller running Windows Server 2012 or a newer operating system, you can create and use an encrypted cluster volume. If the domain functional level is Windows Server 2008 R2, this means that domain controllers are running Windows Server 2008 R2 and newer operating systems.1120409A6: Implementing Failover Clustering with Hyper-VLesson 2: Configuring and Using Shared StorageStoring A Virtual Machine on an SMB 3.0 Shared FolderUsing Scale-Out File ServerWhat Is iSCSI?What Is iSCSI Target Server?Demonstration: Using an iSCSI Target ServerConsiderations for Implementing iSCSI StorageUsing Virtual Hard Disk Sharing as Shared StorageList each topic and briefly introduce what it will cover. Ask students how familiar they are with iSCSI SAN and based on their answers, adjust the content of this lesson.1220409A6: Implementing Failover Clustering with Hyper-VStoring A Virtual Machine on an SMB 3.0 Shared FolderHyper-V supports SMB 3.0 or newerHyper-V uses file share is used as cluster shared storageContinuously available shares are recommendedAll virtual machine storage can be on an SMB shareConfiguration, virtual hard disks, checkpointsSMB Share Applications profile should be usedNo access-based enumeration or share cachingFull permissions on NTFS folder and SMB shareHyper-V administratorsComputer account of Hyper-V hostHyper-V cluster computer account, if Hyper-V clusteredRemind students that you can store running virtual machines on SMB 3.0 file shares. You can either create it on the shared network folder, or move it there. You already covered the benefits of SMB 3.0, and in one of the previous labs, students moved a virtual machine to a shared network folder. In this topic, you should focus on how to configure a shared network folder and whom to grant permissions to the share.QuestionCan you store a virtual machine on a shared folder on a Windows Server 2008 R2 file server?AnswerIf the virtual machine is not running and you will not run it from the shared network folder, you can store it on any shared network folder. However, if you plan to run it from the shared network folder, you should store it on a shared folder on Windows Server 2012 or newer. Hyper-V will not warn you, but you should remember that running virtual machine from non-SMB 3.0 file shares is not supported.1320409A6: Implementing Failover Clustering with Hyper-VUsing Scale-Out File ServerFile server role cluster can work in two modes:Scale-out file server clusterFile server cluster for general useBenefits of scale-out file server cluster:Active-Active file shares Increased bandwidth CHKDSK with zero downtime CSV cache Simple managementAutomatic scale-out rebalancingClients redirected to the best node for access to a shareAvoids unnecessary traffic redirection Explain the difference between file server cluster for general use and scale-out file server cluster. Point out that file server cluster for general use runs only on a single failover cluster node, while scale-out file server runs on multiple nodes simultaneously. Scale-out file server also provides a scalability solution in addition to high availability.List the benefits of scale-out file server, and mention that Windows Server 2012 R2 introduces some new features such as automatic scale-out rebalancing.QuestionDoes file server cluster for general use support more clients than standalone file server?AnswerFile server cluster for general use provides high availability because this cluster role can be moved between nodes in the failover cluster. However, at any time, it runs only on a single node, and can support only the number of clients that this node can handle. If the node was a standalone server and not a node in the failover cluster, it would support the same number of clients, but without high availability.1420409A6: Implementing Failover Clustering with Hyper-VWhat Is iSCSI?Client-server SCSI transport protocolSends SCSI commands over IP networksAny SCSI device can be accessedWindows Server supports only block storageBlock storage device is presentedUsed as locally attached diskiSCSI target is Windows Server role serviceCan be added as failover cluster roleMultipath I/O for redundancyiSCSI initiator is part of Windows client and Windows Server operating systems

iSCSI client runs iSCSI initiator

TCP/IP protocoliSCSI targetstorage arrayIntroduce iSCSI as a client-server protocol, which sends small computer system interface (SCSI) commands over IP networks. Remind students that Windows Server supports only block storage devices with the iSCSI protocol. Explain to students that remote iSCSI storage is presented as a locally attached disk, even though all communication with it occurs over the network. Point out that the iSCSI initiator is a client and it is included in any Windows Server or Windows client operating system, whereas iSCSI target is a server and it is a role service in the Windows Server operating system. Be sure to mention the importance of iSCSI target server cluster role and Multipath I/O (MPIO) feature for providing redundancy and high availability for the iSCSI storage.QuestionWhat must you enable and configure in Windows Server 2012 R2 to be able to use storage on an iSCSI SAN?AnswerTo be able to use storage on an iSCSI SAN, you need an iSCSI initiator. iSCSI initiator is part of every Windows Server and Windows client operating system and it is installed by default, so you do not need to install anything in Windows Server 2012 R2. However, you must first enable and configure the initiator properly.1520409A6: Implementing Failover Clustering with Hyper-VWhat Is iSCSI Target Server?Virtual disks use the .vhdx formatPresented to iSCSI initiators as SCSI logical units Limit initiators that can access logical units Fixed size, dynamically expanding, or differencingClear the virtual disk on allocationSize can be up to 64 TBCan extend and shrink virtual disks onlineEnables application-consistent snapshotsIncludes Storage Management Initiative Specification providerStandards-based managementEnables discovery and storage-based managementIntroduce iSCSI target server, and remind students that it shares several similarities with the virtual hard disks that Hyper-V uses. Explain to students that virtual hard disks and virtual disks use the .vhdx format. However, iSCSI virtual disks use only the .vhdx format, whereas Hyper-V virtual hard disks can be either .vhd or .vhdx format). Mention that similar to virtual hard disks, iSCSI virtual disks can be dynamically expanding, fixed size, or dynamic, and both have a maximum size of 64 terabytes (TB). Point out that you can also expand virtual disks and virtual hard disks while they are in use. Emphasize the importance of the Storage Management Initiative Specification provider. This module does not cover Storage Management Initiative Specification, but it will be important when the iSCSI target server is used from VMM.QuestionCan you use an iSCSI target server on Windows Server 2012 R2 to provide storage to a server that is running a non-Microsoft operating system?AnswerYes, because iSCSI is a platformindependent protocol. You can use it to provide storage to any platform, provided it has implemented an iSCSI initiator. If a non-Microsoft server has an iSCSI initiator, you can use it to access and use storage offered by an iSCSI target on Windows Server 2012 R2.1620409A6: Implementing Failover Clustering with Hyper-VDemonstration: Using an iSCSI Target ServerIn this demonstration, you will see how to use an iSCSI target serverPreparation StepsFor this demonstration you need 20409A-LON-HOST1, 20409A-LON-DC1, and 20409-LON-SS1 running. Sign in as Adatum\Administrator with the password Pa$$w0rd. Also before you perform this demonstration, on LON-HOST1, add LON-SS1 to All Servers.Demonstration StepsOn LON-HOST1, in the Server Manager navigation pane, click File and Storage Services. Confirm that in the SERVERS section, LON-SS1 is selected, and then click iSCSI.In the iSCSI VIRTUAL DISKS section, click TASKS, and then click New iSCSI Virtual Disk.In the New iSCSI Virtual Disk Wizard, on the Select iSCSI virtual disk location page, select E:\, and then click Next.On the Specify iSCSI virtual disk name page, in the Name field, type Disk11, and then click Next.On the Specify iSCSI virtual disk size page, in the Size field, type 15, click Dynamically expanding, and then click Next.On the Assign iSCSI target page, click New iSCSI target, and then click Next.On the Specify target name page, in the Name field, type Lab6-Host1, and then click Next.On the Specify access servers page, click Add. On Select a method to identify the initiator, click Browse, in the Browse field, type LON-HOST1, and then click OK twice.On the Specify access servers page, click Add. On Select a method to identify the initiator, click Browse, in the Browse field, type LON-HOST2, click OK twice, and then click Next.On the Enable Authentication page, click Next.On the Confirm selections page, click Create.On the View Results page, click Close.On LON-HOST1, open Windows PowerShell.

1720409A6: Implementing Failover Clustering with Hyper-V(More notes on the next slide)In Windows PowerShell, create additional virtual disks and add them to the Lab6-Host1 target by running the following cmdlets:New-IscsiVirtualDisk Path C:\iSCSIVirtualDisks\Disk12.vhdx Size 15GB ComputerName LON-SS1Add-IscsiVirtualDiskTargetMapping TargetName Lab6-Host1 Path C:\iSCSIVirtualDisks\Disk12.vhdx -ComputerName LON-SS1In Server Manager, on the toolbar, click the Refresh icon, and confirm that virtual disk Disk12.vhdx displays and it is mapped to the Lab6-Host1 target.On LON-HOST1, in Server Manager, click Tools and then click iSCSI Initiator. In the iSCSI Initiator Properties dialog box, in the Target field, type LON-SS1, and then click Quick Connect. Disconnect any pre-configured targetsIn Quick Connect, click the Discovered target with Lab6-Host1 in the name, click Connect, click Done, and then click OK.On LON-HOST1, in Server Manager, on the Tools menu, click Computer Management.In Computer Management, in the navigation pane, click Disk Management. In the details pane, confirm that two disks are added, that they have the size of 15 GB, and that they are Offline. Point out to students that these are the virtual disks that you just added on the iSCSI target.1820409A6: Implementing Failover Clustering with Hyper-VConsiderations for Implementing iSCSI StorageUse a fast network for accessing iSCSI storageNetwork should be dedicated for accessing storageDeploy the iSCSI target as a highly available roleIncluding redundant network pathsImplement iSNS for discovering iSCSI devicesImplement security for iSCSI storageLimit initiators that can access iSCSI targetAuthenticate initiator connectionEncrypt network trafficDiscuss best practices and considerations for designing iSCSI storage solutions. Point out the importance of fast dedicated networks for iSCSI traffic, and providing high availability for the iSCSI storage. Ask students if they are using Microsoft Internet Storage Name Service (iSNS) servers in their environment, and explain its benefits. Discuss iSCSI security and its role when using a dedicated network for iSCSI.QuestionHow can you control which iSCSI initiators can connect and use an iSCSI target?AnswerAccess Servers is an iSCSI property that you can use to configure which iSCSI initiators can connect to an iSCSI target. You can also configure authentication to allow only connections from the properly configured initiators.1920409A6: Implementing Failover Clustering with Hyper-VUsing Virtual Hard Disk Sharing as Shared StorageA failover cluster runs inside virtual machinesA shared virtual disk used as a shared storageVirtual machines do not need access to iSCSI or FC SANPresented as virtual SAS diskCan be used only for dataRequirements for shared virtual diskVirtual hard disk must be in .vhdx formatConnected by using a virtual SCSI adapterStored on a scale-out file server or CSVSupported operating systems in a virtual machineWindows Server 2012 or Windows Server 2012 R2One of the earlier modules in this course covered virtual hard disk sharing, so you can ask students questions and emphasize important points, such as when you would use virtual hard disk sharing, what are the requirements, and why you would use virtual hard disk sharing instead of using iSCSI or Fibre Channel SAN. Use the second slide in this topic to compare virtual hard disk sharing with the iSCSI and Fibre Channel SAN.QuestionDo you need to install anything into the virtual machine to enable virtual hard disk sharing?AnswerThe virtual machine must be running a supported operating system, which in this case is Windows Server 2012 or a newer Windows Server operating system. You should also ensure that the latest version of integration services in installed on the virtual machine, in order to use shared virtual hard disk.2020409A6: Implementing Failover Clustering with Hyper-VUsing Virtual Hard Disk Sharing as Shared StorageCapabilityShared VHDXVirtual Fibre ChanneliSCSI Supported storageStorage Spaces, Serial attached SCSI, Fiber Channel, iSCSI, SMBFiber Channel SANiSCSI SANHow is storage presented in virtual machineVirtual Serial attached SCSIVirtual Fiber Channel LUNiSCSI LUNData flows through the Hyper-V switchNoNoYesStorage is configured at the Hyper-V host levelYesYesNoProvides low latency and low CPU useYes (RDMA or Fiber Channel)Yes (Fibre Channel)NoRequires specific hardwareNoYesNoSwitch must be reconfigured when virtual machine is migratedNoYesNoComparing guest clustering options2120409A6: Implementing Failover Clustering with Hyper-VLesson 3: Implementing and Managing Failover Clustering with Hyper-VImplementing a Failover ClusterHyper-V Validation TestsDemonstration: Creating a Failover ClusterConfiguring Highly Available Virtual MachinesVirtual Machine MonitoringDemonstration: Creating and Managing the Virtual Machine Clustered RoleWhat Is the Hyper-V Replica Broker Role?What Is CAU?List each topic and briefly introduce what it will cover. This lesson focuses on failover cluster settings that are specific to the virtual machine cluster role, although many settings are the same also for other cluster roles.2220409A6: Implementing Failover Clustering with Hyper-VImplementing a Failover ClusterInstall Windows Server 2012 R2 serversSame hardware and same operating system on all nodesConfigure shared storageAll nodes should have access to shared storageInstall the failover clustering featureInstall the server role on the serversOnly on servers that will host that highly available roleValidate and create a failover clusterConfigure a highly available clustered role Test clustered role failoverExplain the main steps in implementing failover cluster. Use Hyper-V as an example, but explain that you can implement any other cluster role in a similar way. Keep the explanation fairly highlevel, because explaining details can take a lot of time. Remember that students will perform all of these steps in the lab, except for installing the operating system.QuestionCan you implement a failover cluster by using the Windows Server 2012 R2 Standard operating system?AnswerYes. In operating systems prior to Windows Server 2012, the Standard edition did not include the failover clustering feature; the Enterprise or Datacenter edition was required, because they included failover clustering. However, the Windows Server 2012 Standard and Windows Server 2012 R2 Standard editions include failover clustering, so you can use these operating systems for setting up a failover cluster. 2320409A6: Implementing Failover Clustering with Hyper-VHyper-V Validation TestsValidate a Configuration WizardValidates nodes before adding them to a failover clusterRequired to have supported cluster configurationRun before creating a cluster and after any changesCan limit validation to specific cluster storageHyper-V validation tests includeCompatibility of Virtual Fibre Channel SANsIntegration Services VersionMemory Resource Pool CompatibilityStorage Resource Pool CompatibilityVirtual Machine Network ConfigurationVirtual Machine Storage ConfigurationMatching Processor Manufacturers

Explain the cluster validation process. Explain that you should perform it before creating a failover cluster, and each time a cluster configuration changes. Emphasize that validation is not mandatory, but is strongly recommended, and required if you want Microsoft to support the cluster. Mention some of the Hyper-V validation tests and their importance for the failover cluster. You can use screenshots with the Hyper-V Validation tests as guidance, but be aware that students will also perform validation in the lab.QuestionWhy is it important that all failover cluster nodes have processors from the same manufacturer?AnswerYou can move virtual machines between failover cluster nodes. If source and target node are using processors from different vendors, you would not be able to move running virtual machine between them. For example, if the source node has Intel processors and the destination node has AMD processors, you would have to restart the virtual machine on the target node.2420409A6: Implementing Failover Clustering with Hyper-VHyper-V Validation Tests

2520409A6: Implementing Failover Clustering with Hyper-VHyper-V Validation Tests

2620409A6: Implementing Failover Clustering with Hyper-VDemonstration: Creating a Failover ClusterIn this demonstration, you will see how to create a failover clusterPreparation StepsFor this demonstration you need 20409A-LON-HOST1, 20409A-LON-HOST2, 20409A-LON-DC1, and 20409-LON-SS1 running. Sign in as Adatum\Administrator with the password Pa$$w0rd. Also before you perform this demonstration, you need to perform following preparation steps:On LON-HOST1, add LON-SS1 to All Servers in Server Manager.On LON-HOST1, run Install-WindowsFeature RSAT-AD-AdminCenter cmdlet.On LON-HOST1 and LON-HOST2 Install the Failover Clustering feature.On LON-HOST2, create private virtual switch named Private Switch.On LON-HOST1, in Computer Management, rightclick Disk (Created in previous demo), click Online and then click Initialize Disk. Right-click unallocated space on Disk, click New Simple Volume, click Next four times, and then click Finish.Demonstration StepsOn LON-HOST1, in Server Manager, on the Tools menu, click Failover Cluster Manager.In Failover Cluster Manager, in the Actions pane, click Create Cluster. In the Create Cluster Wizard, on the Before You Begin page, click Next.On the Select Servers page, in the Enter server name field, type LON-HOST1, and then click Add. After server is added, in the Enter server name field, type LON-HOST2, click Add, and then click Next.On the Validation Warning page, click Next.In the Validate a Configuration Wizard, on the Before You Begin page, click Next.On the Testing Options page, click Next.On the Confirmation page, click Next. While you wait until all validation tests are performed, notice the many notifications that display about the problems with the drives.

2720409A6: Implementing Failover Clustering with Hyper-V(More notes on the next slide)View the validation report, and then click Finish.On the Access Point for Administering the Cluster page, in the Cluster Name field, type LON-CLUST, and then click Next.On the Confirmation page, click Next.On the Summary page, view the report, and then click Finish.In Server Manager, on the Tools menu, click Active Directory Users and Computers.In Active Directory Users and Computers, expand Adatum.com, in the navigation pane, click the Computers container, and confirm that it contains computer accounts for LON-HOST1, LON-HOST2, and LON-CLUST, which was added when you created the failover cluster. Close Active Directory Users and Computers.On LON-HOST1, open File Explorer, click drive C, and in the details pane, confirm that a folder named ClusterStorage displays. Double-click the ClusterStorage folder, and confirm that the folder is empty.In the Failover Cluster Manager, in the navigation pane, expand LON-CLUST.Adatum.com, expand Storage, and then click Disks. In the details pane, right-click Cluster Disk 2, and then click Add to Cluster Shared Volumes.In File Explorer, confirm that the ClusterStorage folder contains a mounted volume for Volume1, which was added when you added the disk to the cluster shared volume.2820409A6: Implementing Failover Clustering with Hyper-VConfiguring Highly Available Virtual MachinesHigh Availability WizardVirtual machine storage is on shared storageCSV or SMB 3.0 continuously available shareVirtual machine startup priorityHigher priority is started before lower priorityNo auto start, must restart manually after failoverPreferred ownersVirtual machine will start on preferred Hyper-V hostStart on possible owner only preferred owners are unavailableIf preferred and possible owners are unavailable, virtual machine will move to other failover cluster node, but not start

Use the screenshots on the slides in this topic as guidance on configuration options for the virtual machine cluster role. Mention that many settings are the same for all cluster roles, whereas some are specific for virtual machines. Explain that highly available virtual machines must have data files stored on the shared storage, and you can create it by using the High Availability Wizard. Mention virtual machine priority and how it affects virtual machines when they are moved to a different node. Discuss the preferred owners and possible owners lists, and their usage. Mention also failover, failback, and anti-affinity settings. Explain anti-affinity, and emphasize that you cannot configure it in a GUI (except in VMM), but only by using Windows PowerShell. Use the screenshots on the slides to show where you can configure all of these settings. (You can also show them in a live demonstration.QuestionWill a virtual machine ever fail over to a node that is not on either its preferred owners list or possible owners list?AnswerIf any of the preferred owners is online and has available resources, the virtual machine will fail over to one of those nodes. If no node from the preferred owners list is available, then the virtual machine will fail over to one of the nodes on the possible owners list. If no node from either owners list is available, then the virtual machine will fail over to any other node, but it will not start on that node.2920409A6: Implementing Failover Clustering with Hyper-VConfiguring Highly Available Virtual Machines

AntiAffinityClassNames Clustered roles in same AntiAffinityClassNames avoid same cluster nodePrevents virtual machines from running on the same nodeConfigured in Windows PowerShell or System Center 2012 Virtual Machine ManagerOptions to modify failover and failback settingsNumber of times to restart a clustered rolePrevent failback of the clustered role to preferred nodeVirtual machine Policies settingsVirtual machine Heartbeat monitoringRequires integration services in virtual machine3020409A6: Implementing Failover Clustering with Hyper-VConfiguring Highly Available Virtual Machines

3120409A6: Implementing Failover Clustering with Hyper-VConfiguring Highly Available Virtual Machines

3220409A6: Implementing Failover Clustering with Hyper-VConfiguring Highly Available Virtual Machines

3320409A6: Implementing Failover Clustering with Hyper-VConfiguring Highly Available Virtual Machines

3420409A6: Implementing Failover Clustering with Hyper-VConfiguring Highly Available Virtual Machines

3520409A6: Implementing Failover Clustering with Hyper-VVirtual Machine MonitoringApplication health detection in virtual machineMonitor services through Service Control ManagerConfigure service recovery to take no actionMonitor events in System, Application, or Security logsWindows Server 2012 or newer requiredConfigurable recovery actionsRestart serviceRestart virtual machineFail over virtual machineVirtual machine network and storage protectionFailure of virtual hard disk or lost network connectivityVirtual machine moved to different cluster node

Explain that prior to Windows Server 2012, Hyper-V could monitor only the virtual machine heartbeat. In Windows Server 2012, Hyper-V can also monitor services and applications that are running in virtual machines. In Windows Server 2012 R2, Hyper-V can also monitor failure of the virtual machine storage and network connectivity. Provide an example of how monitoring services in virtual machines can be useful, and emphasize the requirements: Windows Server 2012 or newer server operating system in the virtual machine, and integration services (which is installed by default). You can use the second slide in this topic to explain how to configure virtual machine monitoring.QuestionHow can you monitor an application that is installed in a Windows Server 2012 R2 virtual machine, but is not running as a service?AnswerYou can configure virtual machine monitoring to act upon events in the System, Application, or Security logs. If an application is writing events in one of those logs, you can monitor such applications in the virtual machine.QuestionHow should you configure a service in a highly available virtual machine by using Service Control Manager, if you plan to monitor it by failover cluster?AnswerIf you plan to monitor a service in a virtual machine, you should configure in Service Control Manager one of the recovery options for this service as Take no action.3620409A6: Implementing Failover Clustering with Hyper-VVirtual Machine Monitoring

3720409A6: Implementing Failover Clustering with Hyper-VVirtual Machine Monitoring

3820409A6: Implementing Failover Clustering with Hyper-VVirtual Machine Monitoring

3920409A6: Implementing Failover Clustering with Hyper-VVirtual Machine Monitoring

4020409A6: Implementing Failover Clustering with Hyper-VDemonstration: Creating and Managing the Virtual Machine Clustered RoleIn this demonstration, you will see how to create and manage a virtual machine clustered role.After you finish with the demonstration, perform Lab A, Exercise 2, Task 6, Destroy a failover cluster, to prepare the environment for next module.Preparation StepsContinue from the previous demonstration.After you finish with the demonstration, perform Lab A, Exercise 2, Task 6, Destroy a failover cluster, to prepare the environment for the next module.Demonstration StepsOn LON-HOST1, in the Failover Cluster Manager, in the navigation pane, right-click Roles, click Virtual Machines and then click New Virtual Machine.In the New Virtual Machine window, click LON-HOST1, and then click OK. In the New Virtual Machine Wizard, on the Before You Begin page, click Next.On the Specify Name and Location page, specify the following values:Name: LON-HA1Location: C:\ClusterStorage\Volume1\Select the Store the virtual machine in a different location check box, and click Next.On the Specify Generation page, confirm that Generation 1 is selected, and then click Next.On the Assign Memory page, select the Use Dynamic Memory for this virtual machine check box, and then click Next four times.On the Competing the Virtual Machine Wizard page, click Finish. Virtual machine named LON-HA1 is created.In the High Availability Wizard, on the Summary page, click Finish. On LON-HOST1, in the Failover Cluster Manager, right-click the LON-HA1 role, click Change Setup Priority, and then click Low. Right-click the LON-HA1 role and then click Properties.

4120409A6: Implementing Failover Clustering with Hyper-V(More notes on the next slide)In the LON-HA1 Properties dialog box, on the General tab, confirm that the virtual machine is configured with the Priority value set to Low. In the Preferred Owners section, click LON-HOST1. Point out to students how you can order preferred owners for the cluster service. In the LON-HA1 Properties dialog box, click the Failover tab. On the Failover tab, specify the following values, and then click OK:Maximum failures in the specified period: 2Period: 3In the Failover Cluster Manager, on LON-HA1, click the Resources tab. Right-click Virtual Machine LON-HA1, and then click Properties.In the Virtual Machine LON-HA1 Properties dialog box, click the Policies tab. In the Period for restart (mm:ss) field, type 10:00.Click the Advanced Policies tab, confirm that both LON-HOST1 and LON-HOST2 are selected as Possible Owners, and then click OK.On LON-HOST1, open Windows PowerShell. In Windows PowerShell, add the virtual machine cluster role by running the following cmdlet:Add-ClusterVirtualMachineRole VMName 20409A-LON-BLUE1On LON-HOST1, in the Failover Cluster Manager, select 20409A-LON-BLUE1 as the cluster Role. In the LON-BLUE1 pane, click the Summary tab, and confirm that no Monitored Services are listed.In the details pane, right-click 20409A-LON-BLUE1, click More Actions, and then click Configure Monitoring.In Select Services, click Print Spooler, and then click OK.In the LON-BLUE1 pane, confirm that Print Spooler is listed under Monitored Services.4220409A6: Implementing Failover Clustering with Hyper-VWhat Is the Hyper-V Replica Broker Role?

ServerAServerBServer3Server1Server2ServerC

Failover cluster 1Failover cluster 2Replica broker

Explain what the Hyper-V Broker Replica role is, and its importance when a replica virtual machine is on a failover cluster node. Use the animation slide to explain how replica broker redirects replication traffic to the new replica server when a replica virtual machine is moved between failover cluster nodes.QuestionWhen do you need Hyper-V Replica Broker?AnswerYou need Hyper-V Replica Broker when the replica Hyper-V host is a failover cluster node. If the replica server is not part of the failover cluster, you do not need Hyper-V Replica Broker.4320409A6: Implementing Failover Clustering with Hyper-VWhat Is CAU?Automatically update cluster nodesScans, downloads, and installs updates on all nodesFails over clustered roles before installing the updateMinimal or no downtimeRestarts nodes after the updates are installed if neededFails back clustered rolesCustomizable pre- and post-update actionsCAU can work in two modesRemote Updating modeSelf Updating modeExplain Cluster-Aware Updating (CAU), and how it simplifies installing updates in a failover cluster. Ask students how they update failover cluster nodes, and point out that CAU performs the same steps in an automated manner without user interaction. Mention that you can customize pre-update and post-update actions, and explain the differences between the Remote Updating mode and Self-Updating mode. QuestionIs there any downtime when you update nodes in a failover cluster by using CAU?AnswerIt depends on the cluster roles. If you can move a cluster role (such as a highly available virtual machine or a scale-out file server), between nodes without downtime, then there is no downtime when CAU is performing the update. If moving a role causes some interruption in client connectivity, then there will be minimal downtime when CAU performs the update.4420409A6: Implementing Failover Clustering with Hyper-VLab: Implementing Failover Clustering with Hyper-VExercise 1: Creating a Hyper-V Failover ClusterExercise 2: Managing a Hyper-V Failover ClusterLogon InformationVirtual machines: 20409A-LON-HOSTx, 20409A-LON-CLx, 20409A-LON-DC1, and 20409A-LON-SS1User name: Adatum\AdministratorPassword: Pa$$w0rdEstimated Time: 60 minutesStudents work in pairs, with the first student using LON-HOST1 and the second student using LON-HOST2. Both physical hosts are connected by a crossover cable.A task that explicitly uses computer name (1 or 2) should be performed only by one student, on his or her physical or virtual machine.A task that is using x for computer name (for example LON-HOSTx) should be performed on both computers, and each student should perform it by replacing x with his or her number, for example LON-RED1, and perform it on that computer. Some tasks also reference y this is the partner number. For example, if a students number x is 1 and that student is working on the LON-HOST1 physical host, y refers to number 2 (number of the partner). If a student is working on LON-HOST2, y refers to 1, because in this case, 1 is the the students partners number.Exercise 1: Creating a Hyper-V Failover ClusterA. Datum has decided that they will use iSCSI shared storage for failover clusters. For this purpose, you need to create a proof-of-concept deployment, where you can also demonstrate how to extend iSCSI logical units online. To perform this task, you decide to use one of the existing file servers and configure the iSCSI target server on it. You also need to add the shared storage to the servers, verify that it is configured properly, and create a failover cluster.Exercise 2: Managing a Hyper-V Failover ClusterAs part of the proof-on concept deployment, you need to configure virtual hard disk sharing, which you will use later as shared storage for virtual machine clustering. You also need to create highly available virtual machines and configure their settings. Because several virtual machines will be used as print servers, you need to configure monitoring that will notify you when the print spooler service in those virtual machines stops.4520409A6: Implementing Failover Clustering with Hyper-VLab ScenarioA. Datum Corporation has implemented the Hyper-V virtualization platform in one of their subsidiaries. Most of the host servers in the subsidiary have been converted to Hyper-V hosts, including several servers that run critical business applications. These critical applications need to be available at all times, and the availability should not be affected by the failure of a single host machine. A. Datum has identified failover clustering as the best option for implementing this level of availability.You need to implement a high availability solution for these virtual machines by deploying failover clustering for the virtual machines. You also need to configure highly available virtual machines and virtual machine monitoring.4620409A6: Implementing Failover Clustering with Hyper-VLab ReviewHow can you control which servers can access iSCSI virtual disks?When creating failover clustering in virtual machines, which storage types can virtual machines use as a shared storage?Where must you store a virtual hard disk if you want to use it as a shared storage for virtual machines?QuestionHow can you control which servers can access iSCSI virtual disks?AnswerServers can access iSCSI virtual disks only if they are assigned to an iSCSI target. One of the iSCSI target properties is a list of initiators that can view the iSCSI target and connect to it.QuestionWhen creating failover clustering in virtual machines, which storage types can virtual machines use as a shared storage?AnswerWhen creating failover clustering, virtual machines can use iSCSI Storage Area Network (SAN), Fibre Channel SAN, or shared virtual hard disks as a shared storage.QuestionWhere must you store a virtual hard disk if you want to use it as a shared storage for virtual machines?AnswerVirtual hard disk must be stored on a failover cluster, either on a CSV, or a on a highly available file share on a scale-out file server.4720409A6: Implementing Failover Clustering with Hyper-VModule Review and TakeawaysReview QuestionsReview QuestionsQuestionWhat must you do if you want support from Microsoft for a Windows Server 2012 R2 failover cluster?AnswerIf you want Microsoft support for a Windows Server 2012 R2 failover cluster, all failover cluster hardware components must be certified for Windows Server 2012 R2. The failover cluster configuration, which includes servers, network, and storage, must pass all tests in the Validate Cluster Configuration Wizard.QuestionHow can you configure anti-affinity for virtual machines that are running in a failover cluster?AnswerYou cannot configure anti-affinity for clustered roles in failover clustering or any graphical tool that is part of Windows Server 2012 R2. You can configure anti-affinity by using Windows PowerShell, or by using VMM.4820409A6: Implementing Failover Clustering with Hyper-V