Microsoft supports Exchange Server virtualization when the deployment meets the vendor's requirements, but there...
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
are other measures administrators should take to keep the email flowing.
In my work as a consultant, I find many customers get a lot of incorrect information about virtualizing Exchange. These organizations often deploy Exchange on virtual hardware in ways that Microsoft does not support or recommend, which results in major performance issues. This tip will explain the proper way to deploy Exchange Server on virtual hardware and why it's better to avoid cutting-edge hypervisor features.
When is Exchange Server virtualization the right choice?
The decision to virtualize a new Exchange deployment would be easy if the only concerns were technical. This choice gets difficult when politics enter the equation.
Email is one of the more visible services provided by an IT department. Apart from accounting systems, companies rely on email services more than other information technology. Problems with email availability can affect budgets, jobs -- even careers.
Some organizations spend a sizable portion of the IT department budget on the storage systems that run under the virtual platform. It may be a political necessity to use those expensive resources for high-visibility services such as messaging even when it is less expensive and overall a better technical answer to deploy Exchange on dedicated hardware. While I believe that the best Exchange deployment is almost always done on physical hardware -- in accordance with the Preferred Architecture guidelines published by the Exchange engineering team -- a customer's requirements might steer the deployment to virtualized infrastructure.
How do I size my virtual Exchange servers?
Microsoft recommends sizing virtual Exchange servers the same way as physical Exchange servers. My recommendations for this procedure are:
- Use the Exchange Server Role Requirements Calculator as if the intent was to build physical servers.
- Take the results, and create virtual servers that are as close as possible to the results from the calculator.
- Turn off any advanced virtualization features in the hypervisor.
Why should I adjust the hypervisor settings?
Some hypervisor vendors say that the X or Y feature in their product will help the performance or stability of virtualized Exchange. But keep in mind these companies want to sell a product. Some of those add-on offerings are beneficial, some are not. I have seen some of these vaunted features cause terrible problems in Exchange. In my experience, most stable Exchange Server deployments do not require any fancy virtualization features.
What virtualization features does Microsoft support?
Microsoft's support statement for virtualization of Exchange 2016 is lengthy, but the essence is to make the Exchange VMs as close to physical servers as possible.
Microsoft does not support features that move a VM from one host to another unless the failover event results in cold boot of the Exchange Server. The company does not support features that allow resource sharing among multiple VMs of virtualized Exchange.
Where are the difficulties with Exchange Server virtualization?
The biggest problem with deploying Exchange on virtual servers is it's often impossible to follow the proper deployment procedures, specifically with the validation of storage IOPS of a new Exchange Server with Jetstress. This tool checks that the storage hardware delivers enough IOPS to Exchange for a smooth experience.
Generally, a virtual host will use shared storage for the VMs it hosts. Running Jetstress on a new Exchange VM on that storage setup will cause an outage for other servers and applications. Due to this shared arrangement, it is difficult to gauge whether the storage equipment for a virtualized Exchange Server will provide sufficient performance.
While it's an acceptable practice to run Exchange Server on virtual hardware, I find it often costs more money and performs worse than a physical deployment. That said, there are often circumstances outside of the control of an Exchange administrator that require the use of virtualization.
To avoid trouble, try not to veer too far from Microsoft's guidelines. The farther you stray from the company's recommendations, the more likely you are to have problems.
Dig Deeper on Exchange Server Deployment and Migration Advice