Home > Exchange, Microsoft, VMware > Microsoft and VMware blog wars, the Empire Strikes Back (Exchange 2010 DAG)

Microsoft and VMware blog wars, the Empire Strikes Back (Exchange 2010 DAG)

Update: Microsoft has changed it’s support stance, see the below article.

http://blogs.technet.com/b/exchange/archive/2011/05/16/announcing-enhanced-hardware-virtualization-support-for-exchange-2010.aspx

In this article Microsoft clarifies it’s position on VMware HA in conjunction with Exchange DAG’s and VMware has replies.

I agree that using the Exchange DAG functionality within 2010 is the best High Availability solution you can implement to protect your mailboxes and provide the best uptime available. VMware HA alone does not provide an alternative solution, therefore due to the MS support requirements, you must disable HA by setting the VMware Cluster HA restart priority to disabled for Mailbox VMs within a DAG.

The MS article bases it’s case on not using VMware HA for DAG Mailbox Server as it is a better application aware HA solution and the additional costs of VMware HA. Now as stated above I agree on DAG’s being a better solution but costs? Every version of vSphere, (except the free version) licenses unlimited number of VMs for HA. If a customer already has vSphere then there is no additional costs. The only other requirement for VMware HA that could be perceived to have a cost associated is shared storage.

The primary advantage of Shared storage is also lost when using DAS, host failure means the data stored on that host cannot be used until the host failure is resolved. Well you might say fine, my database copies will activate on another DAG member. True but the surviving DAG member will be required to run more databases until the failed DAG member is restored. Depending on the load, size of your hosts and number or users, it is more than likely that during this time the users will notice slower performance. Where as an Exchange DAG using shared storage, another host can bring those database copies back online quickly and the databases can be redistributed back across two DAG members.
Therefore I do see benefits in continuing to use shared storage and do not believe cost is a significant hurdle to using a DAG.

Shared storage can be anything from iSCSI from an Openfiler server, NFS or Fibre Channel. Storage is a major component when designing and deploying MS Exchange 2010 with or without DAG’s. Exchange 2010 single instance storage is gone, for each database copy you plan to have increases the amount of storage required, plus you must have a restore volume. Therefore it is common depending on the level of protection required to need up to two or three times the storage you would normally require without DAG’s. This is clearly why MS pushes JBOD and cheaper DAS, instead of RAID FIbre channel so that your Exchange 2010 project doesn’t break the budget. Generally though Shared storage prices have reduced considerably and a lot more companies now have a SAN or NAS with SAS and SATA for either their current physical or virtual environment. If you do have existing equipment DAS in fact can be more expensive as it must be managed separately, it’s no cheaper to purchase and may require additional or different backup technologies.

I think this is another Microsoft blogging blunder much like the old blog wars over memory oversubscription. It is also clearer than ever before that Microsoft simply do not understand storage and the changes that have occured across the IT industry driven by companies Virtualizing their workloads.

Advertisements
Categories: Exchange, Microsoft, VMware
  1. November 12, 2010 at 5:06 am

    I’ll be first to admit I’m not a VSphere expert but this table indicates that not all VSphere customers necessarily have HA (though how many actually buy just the Standard is unknown to me).

    http://www.vmware.com/products/vsphere/mid-size-and-enterprise-business/buy.html

    • November 12, 2010 at 5:25 am

      That table is misleading, check the below comparison table that lists all the features, Standard along with even the Essentials version includes HA, you just need a vCenter Server and the VM must reside on shared storage so that other hosts in the Cluster can power on the VM. VMware DRS and vMotion are not licensed on standard.

  2. Stewart Anderson
    November 13, 2010 at 10:48 am

    Couldn’t agree more, when I read the ms blog post I forwarded to Steve and said something along the lines of WTF ?!

  1. November 25, 2010 at 11:40 pm

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: