Right or wrong, go with what’s supported…
There has been a lot of drama recently between Microsoft and VMware with respect to virtualizing Exchange 2010. The background and details are summarized well in this article (in which I'm quoted). I think this situation brings up some important points about virtualizing critical Tier 1 applications - vendor support is very important, and disregarding vendor requirements for support can lead to problems when you need support the most.
There are a number of seemingly strange support requirements from Microsoft and VMware which often leads people to get confused on what is supported or how to configure their environments. A few of them are listed below:
vMotion of clustered VMs is supported in vSphere 4.1..or is it?
While looking over some of the new vSphere 4.1 documentation I noticed that VMware had updated their Setup for Failover Clustering and Microsoft Cluster Service document. As clustering becomes a bigger component of Microsoft's enterprise applications, support for clustering in vSphere becomes even more important.
As in previous versions of this document they list the limitations for clustering on vSphere. The list of limitation is below:
The following environments and functions are not supported for MSCS setups with this release of vSphere:
Migration with vMotion of clustered virtual machines.
Recent Posts
- Vote for top virtualization blogs–keep it lowercase!
- VCP 5 Exam–A few thoughts
- SQL 2012 per-core licensing clarification
- New SQL 2012 Licensing and Its Impact On Virtualization
Recent Comments
- Matt Liebowitz on New SQL 2012 Licensing and Its Impact On Virtualization
- Trey on New SQL 2012 Licensing and Its Impact On Virtualization
- Matt Liebowitz on New SQL 2012 Licensing and Its Impact On Virtualization
- Wad on New SQL 2012 Licensing and Its Impact On Virtualization