Windows Server-Hyper-V Failover cluster virtual machine affinity policy detailed

Received a mail consultation today how to implement a virtual machine affinity policy in Windows Server 2012, a technical home familiar with VMware vsphere Solutions is sure to be familiar with a dynamic migration strategy called DRS, The VM affinity policy can be configured to control two virtual machine applications running on different physical ESXi hosts. This function is still very practical, for example, if a virtual machine application runs a guest cluster, one of the basic requirements is to have the guest virtual machine run on a different physical host, and the high availability of the cluster is lost if the DRS control policy is performance-enabled for two guest virtual machines to run on the same physical host. Another common case is in the solution of a site cluster, if you want to use cluster control to failover within one site, the flexibility of transferring virtual machines between sites via online migration, so is this functionality available in Windows Server Hyper-V?

There has been a significant increase in high availability in Windows Server 2012, including:

1. Virtual machine replication

2. Network Aggregation

3. Integrated High Availability

4. Virtual Machine Application Monitoring

5. Cluster Awareness Update

6. Cluster switching priority control

7. Virtual Machine Affinity Strategy

In my blog once on the above labeled two features have been introduced, then today to take this opportunity to share with you on the Internet through a number of documents learned to the virtual machine affinity strategy set up method.

Failover group switching is based on the following policy to control the switching target physical host,

First, the physical node belongs to a possible physical node list member.

Second, switch nodes are selected according to the preferred physical node order.

If a node in the Preferred physical node list is a member of the Affinity control group, the toggle policy jumps to the next preferred physical node, and so on.

When all the preferred nodes are members of the Affinity policy control group, in order to ensure high availability, the Cluster service ignores the affinity policy and chooses a preferred node as the failover node.

According to the above switching policy control conditions, you need to configure the list of available nodes, preferred node list, and affinity policy of these three parts.

1. List of available nodes

In the failover cluster of Windows Server 2012, select Set up available nodes