Académique Documents
Professionnel Documents
Culture Documents
© 2010 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual
property laws. This product is covered by one or more patents listed at
http://www.vmware.com/download/patents.html.
VMware, VMware vSphere, VMware vCenter, the VMware ―boxes‖ logo and design, Virtual SMP and VMotion are
registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. All other marks
and names mentioned herein may be trademarks of their respective companies.
VMware, Inc
3401 Hillview Ave
Palo Alto, CA 94304
www.vmware.com
Contents
1. Introduction .................................................................................. 5
2. VMware vSphere Platform Advantages........................................ 5
3. Increase Availability across the Exchange Lifecycle .................... 6
3.1 Simplify Upgrades and Reduce or Eliminate Downtime ................................................ 6
3.2 Performance and Recovery Advantages ....................................................................... 6
1. Introduction
By leveraging the inherent benefits of a VMware-based platform, a Microsoft® Exchange Server 2010
deployment on VMware vSphere™ offers a choice of several availability and recovery options, each
providing varying levels of protection and cost. This solution brief provides a description of the various
options available. Topics include:
vSphere Platform Advantages
Increased Availability across the Exchange Lifecycle
Local Site Availability Options
Remote Site Availability Options
Backup and Restore Options
Note The combination of hypervisor based high-availability and MSCS is not currently supported
for production implementations by Microsoft; however, VMware IT and our customers have
reported positive results from the combination.
VMware Distributed Resource Scheduler (DRS) can balance workloads and speed recovery –
VMware DRS is VMware VMotion™ with intelligence. As Exchange workloads increase, VMware
DRS can move a bottlenecked virtual machine to another host with more available resources,
automatically and without downtime. VMware DRS can also help to recover more quickly after server
hardware failure. For example, if a physical server fails, VMware HA will reboot the virtual machine on
another physical server. When the failed server is replaced, VMware DRS migrates the virtual
machine back to its original location with no downtime and no interruption to the end-user.
load distribution are also available to allow the highest level of performance and recovery in the case of a
host failure.
4.1.4 Example: Standalone Exchange Mailbox Server VM with VMware HA, DRS,
and VMotion
Out of the box, vSphere features can help to protect your standalone Exchange virtual machine from
server host failure. VMware HA automatically reboots your Exchange VM on another server if the current
one fails, so your VM can be restored to normal operation in the time that it takes to reboot the operating
system and start the Exchange services. After the original server hardware is fixed or replaced, VMware
DRS and VMware VMotion can be used to quickly move the VM back to its original ESX host, with no
additional downtime.
4.2.2 Example: VMware HA Used with DAG Clustering for Faster Recovery
Database level high availability can be achieved through the use of database availability groups. In the
event of a server host failure, a passive copy of the affected mailbox databases is activated. Client
access servers establish MAPI connectivity to the newly active database copy and client connections are
reestablished. In the background, VMware HA powers-on the failed virtual machine on another server
host, restoring the DAG membership and bringing the newly passive database up to date and ready to
take over in case of a failure, or to be manually reactivated as the primary active database. While the use
of database availability groups on top of hypervisor based clustering is not formerly supported by
Microsoft, internal VMware tests have shown that the two technologies can co-exist and can be a viable
solution to ensure maximum recoverability in the case of a host failure.
Figure 4. VMware vCenter Site Recovery Manager with Database Availability Groups
6.2.1 Example: Using VDR with Exchange Client Access and Hub Transports
The Client Access and Hub Transport roles do not store end-user data, but they do contain data that is
critical to the functionality of the roles. You can quickly recover a failed Client Access or Hub Transport
virtual machine by using VMware Data Recovery to back up the entire contents of the VM. In the case of
guest OS corruption or unsuccessful changes to the Exchange configuration the entire VM can be
restored in minutes using the latest VMware Data Recovery back up image.
Figure 8. Using VDR with Exchange Client Access and Hub Transports
7. Additional Information
vSphere offers many tools and features to increase the availability of Exchange 2010. VMotion, HA, and
DRS can help reduce downtime and improve flexibility in your Exchange 2010 architecture while lowering
costs. In some cases VMware and Exchange features can be combined to improve overall availability.
However, a few things to keep in mind when architecting a solution:
VMotion, HA, and DRS are not currently supported for MSCS nodes. We’ve seen lab results and real-
world customers combine the functionality successfully, just understand that there are support
implications. You can disable HA and DRS in the properties of the affected virtual machines.
If shared storage is used by MSCS nodes, it is only supported on Fibre Channel. Servers, where
shared storage is not required (e.g. stand-alone, CCR and DAG nodes), can use Fibre Channel or
iSCSI. This pertains to storage handled by ESX hosts i.e. RDMs or Virtual Disks on VMFS volumes.
NOTE: if a LUN mapped via PassthruRDMs (Physical Compatibility Mode) is reset, MSCS active
node failover may be triggered in response to that LUN reset. This is independent from such a LUN
being used as a shared storage or non-shared storage.
Network Attached Storage is not currently supported for Exchange, whether the Exchange server is
physical or virtual.
Use of software iSCSI initiators within Guest Operating Systems configured with MSCS, in any
configuration supported by Microsoft, is transparent to ESX hosts and there is no need for explicit
support statements from VMware.
Please visit www.vmware.com/go/exchange for more information.