Last week I was asked about how you would introduce new, bigger, Hyper-V hosts to a cluster. For example, there was a time (not long ago) when the sweet spot for RAM in a host was 32GB RAM. You might have a number of these hosts in a cluster. For example, a cluster with 8 or less hosts would have 1 redundant node with 32GB RAM. If one host fails, then the redundant host can take up the slack.<\/p>\n
In reality, virtual machines will be running across all of the hosts in a load balanced environment. You will have the equivalent of 1 host in redundant capacity<\/em>.<\/p>\n A cluster with 9-16 nodes will probably have 2 redundant hosts (or equivalent capacity).<\/p>\n Say I have 5 hosts with 32GB RAM with 1 of those being redundant. Now I can purchase hosts with 64GB of RAM at a decent rate because servers have many more memory slots and I don\u2019t need to buy the exponentially more expensive 8GB or 16GB memory boards. Can I buy just one of those servers and add it to the existing cluster of 32GB RAM hosts? Sure you can. But you will have trouble when you add more VM\u2019s to it than you could add to a 32GB RAM host.<\/p>\n Let\u2019s put it this way: Say I have 2 * 1 gallon buckets. 1 is full of water. I can put .5 gallon in each bucket. I can pour .5 gallon from one bucket to another to wash it or repair the original bucket. I always have 1 gallon of water \u2026 clustered between my 2 * 1 gallon buckets. Now I want to carry much more water and I buy a 2 gallon bucket to add to my collection of buckets. I have 1 * 1 gallon bucket that is full. I have 1 * 2 gallon bucket that is full. I have 1 empty 1 gallon bucket as a spare. But it can only be a spare for the other 1 gallon bucket. I will have to throw away 1 gallon if I need to wash or repair the 2 gallon bucket and pour its contents into the spare 1 gallon bucket.<\/p>\n The same goes for Hyper-V hosts (purely on RAM capacity). A 32GB RAM host cannot offer full redundancy for a 64GB RAM host. Half of the virtual machines can migrate and stay running\/reboot, but the other half will not be able to start.<\/p>\n Here\u2019s what you can do in a growth scenario:<\/p>\n I haven\u2019t got the h\/w to test this out but I suspect that VMM will scream at you about loss of redundancy in the cluster if you don\u2019t do this right.<\/p>\n Last week I was asked about how you would introduce new, bigger, Hyper-V hosts to a cluster. For example, there was a time (not long ago) when the sweet spot for RAM in a host was 32GB RAM. You might have a number of these hosts in a cluster. For example, a cluster with 8 … Continue reading “Hyper-V Cluster with Different Capacity Hosts”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"_wpcom_ai_launchpad_first_post":false,"footnotes":""},"categories":[20],"tags":[63,181,195],"class_list":["post-10802","post","type-post","status-publish","format-standard","hentry","category-hyper-v","tag-failover-clustering","tag-hyper-v","tag-virtualisation"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n