VMware recently released their best practice advice for Exchange 2010 and VSphere. The link is here: http://www.vmware.com/files/pdf/Exchange_2010_on_VMware_-_Best_Practices_Guide.pdf It's all very sensible advice that links out to and uses Microsoft best practices all the way through it. Unfortunately someone at Microsoft had a problem with the documentation and the Product group have launched forth with a long old rant: http://msexchangeteam.com/archive/2010/11/09/456851.aspx that bears little resemblance to reality. Some of the comments have tried to get MS honest on it, others have just swigged another mouthful of Kool-Aid and supported everything that was written.
So folks, the VMware document is good. The Microsoft blog post is revealing but, as you can read on page 64 of the VMware document, is calling out misleading advice that isn't actually present as advice in the first place. Please read the VMware document carefully. Once you have properly read the document there is no way on earth that you will ever think you could VMotion a running DAG member. Really. Honestly.
Subscribe to:
Post Comments (Atom)
2 comments:
FYI,during the Exchange 2010 session in this year vmWorld Europe, the speaker was very clear about it. He said it was not supported by Microsoft but it was supported by vmware all the way and they were in a process to validate it. Time will tell...
That's interesting news. But at the moment it is categorically unsupported by Microsoft so it shouldn't be done. To be fair lots of customers do it because it's 100% safe to do and Microsoft have absolutely no way of knowing that a particular guest has been VMotion'd to another host. There's no way that Microsoft cannot 'support' it, you just have to ensure that you answer every question carefully.
Post a Comment