Iâ€™ll set the scene a littleâ€¦
Iâ€™m working late, Iâ€™ve just installed Update Manager and Iâ€˜m going to run my first updates. Like all new systems, Iâ€™m not always confident so I decided â€œOut of hoursâ€ would be the best time to try.
I hit â€œRemediateâ€ on my first Host then sat back, cup of tea in hand and watch to see what happensâ€¦.The Hostâ€™s VMâ€™s were slowly migrated off 2 at a time onto other Hosts.
â€œItâ€™s gonna be a long nightâ€ I thought to myself. So whilst I was going through my Hosts one at time, I also fired up Google and tried to find out if there was anyway I could speed up the VMotion process. There didnâ€™t seem to be any article or blog posts (that I could find) about improving VMotion Performance so I created a new Servicedesk Job for myself to investigate this further.
3 months later whilst at a product review at VMware UK, I was chatting to their Inside Systems Engineer, *********, and I asked him if there was a way of increasing the amount of simultaneous VMotions from 2 to something more. He was unsure, so did a little digging and managed to find a little info that might be helpful and fired it across for me to test.
After a few hours of basic testing over the quiet Christmas period, I was able to increase the amount of simultaneous VMotionsâ€¦Happy Days!!
But after some further testing it seemed as though the amount of simultaneous VMotions is actually set per Host. This means if I set my vCenter server to allow 6 VMotions, I then place 2 Hosts into maintenance mode at the same time, there would actually be 12 VMotions running simultaneously. This is certainly something you should consider when deciding how many VMotions you would like running at once
Found this over at Jason Bocheâ€™s blog. Iâ€™ts a guest post by Simon Long. It beats the heck out of a similar post I had in my drafts folder. Woo! Great work!