Implementing Windows Server 2012 R2 Hyper-V Failover Cluster – Part 1 – Design and implementation overview

This article is not part of the Building Microsoft System Center Cloud series but we will use the new cluster to host our VMs in the cloud series.


High-level design

  • None. It is very simple…

Low-level design


First we should configure the network.

  • In the production environment you would like to have physical or VLAN separation of the networks but in our case in our testing environment we will use this configuration because this is the best configuration that currently I am able to use.
  • Another possibility is to have multiple 10 Gb network adapters on a single network, team them to a single virtual switch and create multiple virtual network adapters with configured Quality of Services (QoS – configured minimal bandwidths). It is possible to do this configuration on a single Hyper-V cluster using PowerShell but it is much simpler to do it later from the System Center Virtual Machine Manager.
  • Do not forgot to use different subnets for inter-cluster communication (heartbeat and other communication) and live migration.


  • Direct connection to the SAN (Fibre-Channel).

Implementation overview

Leave a Reply

Your email address will not be published. Required fields are marked *

Active Directory Advanced function AlwaysOn Availability Groups AlwaysOn Failover Cluster Instances Building Cloud Cloud Cluster Cmdlet Database Deployment Design DFS Domain Controller DSC Fabric Failover Clustering File Server Group Policy Hardware Profile Host Hyper-V Installation Library Library Asset Library Server Network Operations Manager Orchestrator PowerShell PowerShell User Group PowerShell Workflow Security Service Manager SQL Server Storage System Center Template Time Time Synchronization Tips Virtual Machine Virtual Machine Manager VM Network VM Template Windows Server 2012 R2