MS Exchange Performance – Nutanix vs VSAN 6.0

When I saw a post (20+ Common VSAN Questions) by Chuck Hollis on VMware’s corporate blog claiming (extract below) “stunning performance advantage (over Nutanix) on identical hardware with most demanding datacenter workloads” I honestly wondering where does he get this nonsense?

FUDfromChuckles

Then when I saw Microsoft Applications on Virtual SAN 6.0 white paper released I thought I would check out what VMware is claiming in terms of this stunning performance advantage for an application I have done lots of work with lately, MS Exchange.

I have summarized the VMware Whitepaper and the Nutanix testing I personally performed in the below table. Now these tests were not exactly the same, however the ESXi Host CPU and RAM were identical, both tests used 2 x 10Gb as well as 4 x SSD devices.

The main differences were ESXi 6.0 for VSAN testing and ESXi 5.5 U2 for Nutanix, I’d say that’s advantage number 1 for VMware, Advantage Number 2 is VMware use two LSI controllers, my testing used 1, and VMware had a cluster size of 8 whereas my testing (in this case) only used 3. The larger cluster size is a huge advantage for a distributed platform, especially VSAN since it does not have data locality, so the more nodes in the cluster, the less chance of a bottleneck.

Nutanix has one advantage, more spindles, but the advantage really goes away when you consider they are SATA compared to VSAN using SAS. But if you really want to kick up a stink about Nutanix having more HDDs, take 100 IOPS per drive (which is much more than you can get from a SATA drive consistently) off the Nutanix Jetstress result.

So the areas where I feel one vendor is at a disadvantage I have highlighted in Red, and to opposing solution in Green. Regardless of these opinions, the results really do speak for themselves.

So here is a summary of the testing performed by each vendor and the results:

 

VSANvNutanixThe VMware white paper did not show the Jetstress report, however for transparency I have copied the Nutanix Test Summary below.

NutanixNX8150Jetstress

Summary: Nutanix has a stunning performance advantage over VSAN 6.0 even on identical lesser hardware, and an older version of ESXi using lower spec HDDs while (apparently) having a significant disadvantage by not running in the Kernel.

Fight the FUD – Support for MS Exchange on Nutanix

Its disappointing that some vendors have so little respect for customers time that they continue to spread FUD (Fear Uncertainty and Doubt) about other vendors products.

This post is for existing and future Nutanix customers to get the facts about support for MS Exchange on Nutanix.

First of all, Nutanix Distributed File System (NDFS) is not Network File System (NFS).

NDFS is a file system which presents storage to hypervisors (ESXi, Hyper-V and Acropolis Hypervisor) via industry standard storage protocols being iSCSI, SMB 3.0 and NFS.

Currently Microsoft do not support Exchange running with VMDKs hosted on NFS for Exchange deployments on vSphere, this is due to an outdated and baseless support policy which experts from almost every major storage vendor agree.

For more information see the below article:

Virtualizing Exchange on vSphere with NFS backed storage?

However Nutanix have a published KB providing full support for MS Exchange when running within VMDKs on NFS datastores.

Nutanix aims to provide an Uncompromisingly Simple solution for customers which gives them maximum flexibility/choice. As such, when deploying applications such as MS Exchange on Nutanix, how the application/s are deployed and what storage protocol they use is ultimately the customers choice.

The below are some of the benefits of this include:

  1. Running a standard platform and storage protocol for all workloads is a simple model which reduces the unnecessary complexity of multiple protocols and/or in-guest storage configurations.
  2. The customer has the choice to deploy in multiple configurations to suit their specific requirements
If you want to run a 100% Microsoft supported Exchange configuration on Nutanix you currently have two options:
  1. vSphere running iSCSI
  2. Hyper-V running SMB 3.0
  3. Acropolis Hypervisor (AHV) running iSCSI (default)

If you understand that NFS datastores are not supported by Microsoft, but accept it is fully supported by Nutanix and you want to run Exchange in a VMDK on NFS datastores, then Nutanix will support for MS Exchange and Microsoft will provide commercially reasonable support directly or via TSAnet if the case needs to be escalated.

So there you have it, MS Exchange can be ran on Nutanix in 100% Microsoft supported configurations and Nutanix customers have the choice in how they wish to deploy with full support from Nutanix.

Exchange__transparent-1024x408

Related Articles:

Microsoft Support for MS SQL on NFS datastores

QUESTION: Is MS SQL supported when running in a vSphere environment where the SQL databases/logs are in a VMDK on an NFS datastore?

Short answer: YES!

Note: I have confirmed this with the Principal Program Manager for SAP, SQL & Azure Customer Programs.

Here are some important Microsoft Knowledge Base articles to confirm this statement.

1. Support policy for Microsoft SQL Server products that are running in a hardware virtualization environment

2. Support policy for Microsoft software that runs on non-Microsoft hardware virtualization software

It is important to note, no where in the above support policies is storage protocol even mentioned. To me this is a very smart move by the SQL team as the underlying storage protocol is abstracted from the VM, making it irrelevant.

The key requirements are:

a) The platform must be SVVP (Server Virtualization Validation Program) certified

VMware is SVVP certified, as is shown by on the SVVP Website.

b) The SQL Server product must be a supported version under its current Microsoft Support Lifecycle policy

For more information about Microsoft Support Lifecycle policies, visit the following Microsoft Support website: http://support.microsoft.com/?pr=lifecycle

c) Virtualization support per SQL features based on SQL Edition

This can be verified here under “Virtualization Support” and the below table is from this KB showing what is supported based on SQL edition.

virtusupportsql

Now in saying SQL is supported when running in a VMDK on NFS datastores, there are some limitations as discussed in SQL AlwaysOn Availability Group support in VMDKs on NFS Datastores.

In summary, old style SQL clustering requiring Shared disks which is not supported.

However SQL Always on Availability Groups (AAG) and SQL Mirroring are supported, which are the two configurations you should be considering these days.

I hope this helps clear up any confusion.

Now for the MS Exchange team to follow the lead of the SQL team!

See Virtualizing Exchange on vSphere with NFS backed storage for more details.