Microsoft Exchange Server workloads perform very well on VMware vSphere. Run all Exchange server roles, including the mailbox server, on vSphere with confidence, to not only match but exceed the performance of physical servers. Each VMware vSphere virtual machine scales to 128 vCPU and 6 TB of memory, and can effortlessly support the IO requirements of the largest and most intensive Exchange mailbox servers configurable. With VMware vSphere, multiple mailboxes can be scaled out on larger multicore servers to increase overall throughput.
By right-sizing an Exchange Mailbox Server (or any other role), we have demonstrated that virtualized Exchange Server achieve comparable performance level (or better than) with fewer compute resources than typically recommended in the Microsoft “Preferred Architecture” Guide. In its virtual incarnation, an Exchange Server on the vSphere platform benefits greatly from the superior resource scheduling, efficiency and redundancy inherent in the hypervisor – two major considerations informing the typical over-allocated compute and storage resource recommendation common in a “Preferred Architecture” implementation.
Maximize Exchange availability by combining the native High Availability capabilities of Exchange Server (Database Availability Group – DAG) with VMware vSphere’s HA and DRS.
Simplify Disaster Recovery by reducing hardware compatibility constraints and the number of physical servers required at the recovery site. Utilize the VMware Site Recovery Manager (SRM) for true, easier, faster, better, more simplified, more efficient, and more unified and predictable Disaster Recovery solution.
Microsoft officially supports VMware vSphere, vMotion, HA and DRS in virtualized Exchange environments. Run Windows Server and Microsoft applications get cooperative support from Microsoft and VMware. Get the same level of support you received on physical servers.
Virtualized Exchange infrastructure require fewer Physical Servers because of the native consolidation benefits of the VMware vSphere platform. Whereas a single physical Server can contain only one instance of an Exchange Server workload, no other workload can be placed on the same physical server even if the available resources exceed the maximum resource capabilities of Exchange Server. The native resource partitioning capabilities of vSphere enables customers to run more than one instance of an Exchange Server role on the same physical server, resulting in fewer physical servers required to support the same infrastructure. Consolidating multiple Exchange server instances onto shared physical servers enables customers to eliminate or minimize the need to deploy dedicated standby hosts for high availability and disaster recovery. Reduce costs by reducing the amount of hardware, thereby also reducing power, cooling and management costs.
Leverage the latest advances in VMware vSphere and Exchange performance to run the largest mailbox server instances with confidence that performance will match or exceed physical performance.
The performance and scalability of VMware vSphere have improved dramatically over the latest product releases. vSphere is able to handle the most demanding workloads thanks to improvements such as:
Today, a single virtual machine with 128 vCPUs is larger than the largest Microsoft recommended Exchange Server 2019 configurations for a single mailbox server (48 cores or vCPUs). At the same time, Microsoft Exchange Server 2019 includes architectural and performance improvements that significantly reduce the IO requirements as compared to all previous version of Exchange Server. Together, these performance improvements ensure that even large, demanding mailbox servers perform well on vSphere with no IO bottlenecks or other performance problems.
Increase the performance of your physical infrastructure by 100 percent or more. For example, without VMware, a single Exchange 2-7 mailbox running on a physical server can scale up to about 8,000 heavy user mailboxes. Using larger servers doesn’t help because the mailbox can’t leverage the additional capacity.
With VMware, Exchange mailboxes can be scaled out on multiple smaller virtual machines to maximize the throughput of the physical server. Using this approach, we have demonstrated that Exchange can be scaled out on 8 virtual machines, each supporting 2,000 very heavy mailbox users, to support 16,000 users on one 16-core server.
Provide simple and cost-effective high availability and disaster recovery for all Exchange server roles with VMware Fault Tolerance, VMware High Availability, vMotion and Site Recovery Manager. Eliminate the need to deploy complex Microsoft Clustering solutions and dedicated standby servers. Alternatively, run Microsoft Clustering on vSphere and combine with vSphere availability solutions to achieve best-in-class availability. Eliminate planned downtime for hardware maintenance with VMware vMotion. Simply vMotion your Exchange virtual machines to another physical host for the duration of the maintenance, with no impact on service availability.
Protect all Exchange server roles against hardware failures and operating system problems with VMware Fault Tolerance or VMware High Availability. In the event of hardware failure, VMware FT ensures continuous availability with no data loss, while VMware HA automatically restarts the virtual machines on another host in minutes.
Implement a simple, automated disaster recovery plan with VMware disaster recovery solutions and Site Recovery Manager. Replicate and recover virtual machines on a secondary site, including entire Exchange deployments, without dedicated standby hardware.
For continuous application-aware availability, combine Microsoft Clustering with VMware availability solutions to provide an additional layer of protection and maximize uptime.
Sizing Exchange infrastructure leads to a difficult compromise between providing enough capacity to support future requirements while keeping infrastructure costs under control. Use vSphere to “right-size” virtual machines for today’s needs with the ability to scale dynamically to support future loads.
Provisioning new email services into production can take months of lead time to procure and install dedicated hardware, provision and configure the operating system, and finally configure the application. This long manual process is also error-prone and can lead to configuration mistakes and service downtime.
With vSphere, create a library of vApps that can be provisioned on demand onto your existing virtual infrastructure in minutes. For example, with virtual appliances, reduce the lead time to deploy BlackBerry Enterprise Server from weeks or months down to minutes.
Test and troubleshoot your complex email applications quickly while minimizing risk of change. Use vCenter Snapshots and Clones to reproduce your vApps, encapsulating entire multitier applications, in the lab in minutes. Test your application changes in the context of related application tiers, and on an exact copy of your production configuration, to minimize the risk of errors. Eliminate the need to provision applications manually for each test cycle.
Microsoft officially supports Windows Server and Server products running on VMware ESX. This includes Windows Server 2000 SP4, Windows Server 2003 SP2 or later, and Windows Server 2008 and specialty roles provided by the operating system such as Active Directory or File Services. Major applications that are supported include Microsoft Exchange, SQL Server and SharePoint Server. Microsoft has published a complete list of supported applications, and continues to update it. Supported ESX configurations are also listed
VMware ESX was the first hypervisor to be validated under the Microsoft Virtualization Validation Program (SVVP), providing customers who run Windows Server and Microsoft applications with cooperative support from Microsoft and VMware. Customers can now run Exchange on VMware with the peace of mind that they will receive the support they need.
Microsoft licensing has recently been modified to allow customers to reassign licenses between physical servers as frequently as desired. In the past, licenses could only be reassigned once every 90 days, limiting the benefits of vMotion. The new licensing flexibility enables efficient use of vMotion for Windows Server and major applications including Exchange, SQL Server and SharePoint Server.
What happens if you are running a non SVVP-validated configuration of ESX and Microsoft products? Customers routinely tell us they still receive the Microsoft support benefits. Support options vary, however, depending on how customers purchase VMware and Microsoft products.
The following scenarios are common:
Server resellers including Dell, Fujitsu, Fujitsu-Siemens, HP, IBM and Unisys offer end-to-end support for Microsoft software running on their servers and VMware if VMware products are purchased with the server hardware and are covered by a valid support agreement with the server reseller. This provides customers one-stop support via the server reseller if an issue arises. See Support for Microsoft Software in VMware Virtual Machines for more details.
Microsoft states that it will use “commercially reasonable efforts” to support its products running on VMware virtual machines. Customers regularly tell us that Microsoft’s commercially reasonable efforts are effective and appropriate to maintain operations as planned. There may be confusion within Microsoft’s field and channel organizations regarding the scope of support that can be provided, and in some cases, customers may perceive that “commercially reasonable efforts” will not meet their expectations. In general, Microsoft offers its large customers excellent support for their products running on VMware. Microsoft’s policy states that after such efforts are exhausted, Microsoft support specialists may request that customers replicate the issue on a physical machine in order to proceed with the investigation. See Microsoft KB 897615 for more details.
Microsoft’s level of support for these customers can be more restrictive. Before providing support, Microsoft specialists may request that customers first replicate the issue on a physical machine per Microsoft KB 897615.
Virtualizing Exchange can be very simple. Many VMware customers simply deploy Exchange on vSphere exactly like they would deploy Exchange on physical infrastructure. But vSphere also offers many new options and capabilities that enable Exchange to run better. For example, customers can leverage VMware High Availability as an alternative or complement to Microsoft clustering, and mailbox servers can be scaled out on smaller and more efficient virtual machines.
Many customers turn to VMware for expert assistance in optimizing their Exchange environment on vSphere. To answer this demand, VMware has created a community of partners that are trained on VMware solutions for virtualizing Exchange. VMware works closely with this community to develop best practices, and implement these best practices in customer projects. The partner community has unique expertise to help you optimize your Exchange environment on vSphere – all the way from initial design to full production implementation.