Solution: You set the memory-weight threshold value to High for each business-critical VM, Does this meet the goal?

You manage a Hyper-V 2012 cluster by using System Center Virtual Machine Manager 2012 SP1. You
need to ensure high availability for business-critical virtual machines (VMs) that host business-critical
SQL Server databases.
Solution: You set the memory-weight threshold value to High for each business-critical VM, Does this
meet the goal?

You manage a Hyper-V 2012 cluster by using System Center Virtual Machine Manager 2012 SP1. You
need to ensure high availability for business-critical virtual machines (VMs) that host business-critical
SQL Server databases.
Solution: You set the memory-weight threshold value to High for each business-critical VM, Does this
meet the goal?

A.
Yes

B.
No



Leave a Reply 6

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


Monkeh

Monkeh

Should this be Yes?

http://blogs.technet.com/b/kevinremde/archive/2013/04/22/hardware-profiles-in-system-center-2012-sp1-vmm-build-your-private-cloud-series.aspx

From the above article – “we see that we can further prioritize the memory that these machines will need to run. When memory resources on a virtualization host are running low, this is a good way to help ensure that your most important machines are able to run; even at the potential exclusion of other less important machines.”

correction

correction

Yes same opinion…

Jon

Jon

I think this should be no, from reading the technet article below setting the threshold to High will make sure that it gets priority over other vm’s, but this will not change the availability of the virtual machine. Utilizing some type of clustering with the Hyper V hosts or network redundancy would ensure the availability of these machines.

https://technet.microsoft.com/en-us/library/jj628160.aspx

puck

puck

Forget My above answer.

This is a series of very similar yes or no questions by microsoft. Most of the answers are “no”.

The answer to this questions is YES when they say –

Solution: You create an availability set and place each business-critial VM in the set.

“If you create an Availability Set in Virtual Machine Manager for two different virtual machines, Virtual Machine Manager 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 service update for these virtual machines, especially if you run a guest cluster for example SQL server, Exchange or even an IIS web server farm behind load balancers.”

http://www.thomasmaurer.ch/2013/07/how-to-configure-availability-sets-in-virtual-machine-manager/

puck

puck

These virtual machines are in a cluster already, so ticking the “high availability” box on VMM will NOT work. This box will be greyed out. We cannot use preferred owner or high availability box or memory weight as those options are only available when we INITIALLY configure the VM.

Since the VM is already running, we need to add it to an availability set.