Better Intelligence for Automatic Placement?

I'm running System Center 2012 R2 CU4 on a 7 blade Windows Server 2012 R2 Hyper-V Cluster. All blades have dual-socket 6 core processors with 128GB of RAM. I'm starting to deploy Cluster Aware Updating and I've noticed that when a node goes down for maintenance, the placement of VMs when the node is drained is not very, well, intelligent.

For example, I have a few 64GB SQL VMs and when CAU live migrates them to another node, it will place them on a node with only 50GB of free memory which causes the VM to fail to start. I have to manually migrate the VM to another node with enough free RAM.

This seems to only happen with my larger VMs, 64GB of RAM and above.

Is there any way I can make this process more intelligent?

November 19th, 2014 5:11pm
PRO Tips with SCOM!
Free Windows Admin Tool Kit Click here and download it now
February 4th, 2015 5:08pm
Are the SQL VMs using dynamic memory? But PRO tips should provide correct VM placement in this scenario.
February 13th, 2015 12:38am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics