Jaa

  • Artikkeli

Configuring Availability Options for Virtual Machines Overview

 

Updated: May 13, 2016

Applies To: System Center 2012 SP1 - Virtual Machine Manager, System Center 2012 R2 Virtual Machine Manager

Starting with System Center 2012 Service Pack 1 (SP1), you can use Virtual Machine Manager (VMM) to configure availability options for virtual machines that are deployed on Hyper-V host clusters. By using VMM, you can configure the following availability options:

  • Virtual machine priority: Based on these settings, the host cluster starts or places high-priority virtual machines before medium-priority or low-priority virtual machines. This ensures that the high-priority virtual machines are allocated memory and other resources first, for better performance. Also, after a node failure, if the high-priority virtual machines do not have the necessary memory and other resources to start, the lower priority virtual machines will be taken offline to free up resources for the high-priority virtual machines. Virtual machines that are preempted are restarted later in priority order.

  • Preferred and possible owners of virtual machines: These settings influence the placement of virtual machines on the nodes of the host cluster. By default, there are no preferred owners (there is no preference), and the possible owners include all server nodes on the cluster.

  • Availability sets: When you place multiple virtual machines in an availability set, VMM will attempt to keep those virtual machines on separate hosts and avoid placing them together on the same host whenever possible. This helps to improve continuity of service. Another way to configure this setting is to use Windows PowerShell commands for failover clustering. In this context, the setting appears in the Get-ClusterGroup listing and is called AntiAffinityClassNames.

The following topics describe how to configure availability options for virtual machines that are being managed with VMM, starting with VMM in System Center 2012 SP1:

See Also

Creating a Hyper-V Host Cluster in VMM Overview