EMC PROTECTION FOR MICROSOFT EXCHANGE SERVER 2010

1. EMC PROTECTION FOR MICROSOFT EXCHANGE SERVER 2010 EMC VNX5700, EMC RecoverPoint, EMC Replication Manager, EMC Data Protection Advisor, VMware vSphere, and VMware vCenter Site Recovery Manager Fully automated recovery for Microsoft Exchange Server 2010 Unlimited snapshots to protect from logical database corruption In-depth monitoring and reporting EMC Solutions Group — Strategic Solutions Engineering

2. Solution Offering and Options • Full end-to-end Protection for Exchange 2010 environment in a virtualized infrastructure • Local application protection with Exchange deployed in DAG • Local continuous data protection (CDP) with RecoverPoint (unlimited snaps) • Remote continuous replication (CRR) with RecoverPoint for DR • Automated failover and failback with vCenter SRM 5 • Database protection and instant restore with Replication Manager • In-depth monitoring and reporting with DPA • Flexible deployment options • White paper for this solution is published here:http://www.emc.com/collateral/hardware/white-papers/h8891-emc-protection-fr-microsoft-exchng-servr2010.pdf

3. Exchange 2010 DR Options

4. Solution Architecture • Two active-active Sites • 10,000 Exchange 2010 users per site (20,000 total) • 1 DAG per site with 2 local copies • 4 Mailbox Server VMs per DAG (each VM configured to run 5,000 users during local switchovers — 2,500 active/2,500 passive) • Exchange user profile • 2 GB mailbox per user • 0.15 IOPS per user

5. Site Protection with RecoverPoint and Automated Failover with SRM Site A Site B RecoverPoint WAN Link RecoverPoint SRM Data Data

6. Parameters Used to Test and Validate the Solution

7. ESXi Host & VM Design NOTE: CPU and memory requirements are based on Microsoft Guidelines. See http://technet.microsoft.com/en-us/library/ee712771.aspx for additional details.

8. Mailbox Server Role Design

9. Exchange 2010 Mailbox Server VM Design • Design Attributes • 5,000 users during local switchovers (2500 active/2500 passive) • 10 DBs per server • 500 users per DB • 1.6 TB DB LUNs • 100 GB Log LUNs • VNX pools • Physical isolation of DAG copies • Domains protected against failure • Mailbox server • Hypervisor host • Storage • Network Active Copies Passive Copies

10. Mailbox Server Building Block Design

11. Storage Design Details for a 5,000-User Mailbox Server Building Block

12. ESX/VMs Storage Design

13. RecoverPoint Design In this solution, EMC RecoverPoint provides protection from Exchange logical database corruption and DR protection in the case of a site failure. Native Exchange replication does not protect from logical corruption. Corruption can potentially replicate to other Exchange database copies within the DAG locally and remotely. In this solution, RecoverPoint is configured as follows: The replication method is Concurrent Local and Remote Replication (CLR) (combines both CDP and CRR). Each Mailbox server VM is placed into its own CG with all replicated database and log LUNs, including the LUN containing the guest OS. Ensures full consistency across all volumes used by the Mailbox Server Role virtual machines.

14. CDP CDP CDP CDP CDP CDP CRR CRR CRR CRR CDP CDP CRR CRR CRR CRR Consistency Group (CG) Design for Active/Active Data Centers Site B Site A MBX1 CG MBX1 • Ensures consistency across production and targets – one Exchange Mailbox server per CG • Application recovery can be independent from SLAs • Enables independent replication of various applications • Utilizes Consistency Groups to organize data MBX2 CG MBX2 MBX3 CG MBX4 CG MBX4 MBX4 MBX3 MBX3 MBX5 CG MBX1 MBX6 CG MBX2 MBX7 CG MBX8 CG

15. RecoverPoint Consistency Group Configuration • One Consistency Group per Mailbox Server VM • 21 Replication Sets per Consistency Group

16. RecoverPoint Group Sets A Group Set is a set of consistency groups to which the system applies parallel bookmarks at a user-defined frequency. • Allows for automatic, periodic bookmarking • Provides same RPO for multiple Consistency Groups distributed across multiple RPAs • Useful for consistency groups that depend on each other or must work together as a single unit • Four Mailbox servers in a DAG at each site – combined into one Group Set to meet 15-minute RPO requirement

17. RecoverPoint CG Policy Settings for SRM

18. RecoverPoint Journal Sizing RecoverPoint journal volumes store consistent point-in-time snapshots (or bookmarks) to enable point-in-time recovery of Exchange data. Journal size will dictate how much protection you will have (how many snaps you can keep). For each CG in the RecoverPoint CLR configuration, three journals are set up: Two at the local site One at the remote site The two most important considerations when sizing storage for journal volumes: Performance Protection window

19. RecoverPoint Journal Sizing (cont.) Formula to calculate journal volume size based on the expected change rate and required rollback time period: Example • Protection requirements: 3 days (72 hours) • Change rate: 5 Mbps Journal size = 5 Mbps x 259,200 seconds / 0.8 x 1.05 = 1,701,000 Mb (~213 GB)

20. RecoverPoint Journal Sizing (cont.) • Journals deployed in this solution

21. RecoverPoint Storage Design Summary

22. RecoverPoint Integration with Replication Manager • RM leverages RP replication technology to automate and schedule VSS copies of Exchange, both locally and remotely • RM automates Exchange 2010 tasks such as: • Create Exchange database application sets • Create and manage multiple-site, application-consistent replicas of Exchange databases • Run a full Exchange job to create a VSS bookmark, run the Microsoft Exchange utility eseutil, and then truncate the Exchange logs • Run an Exchange copy job that creates a VSS bookmark • Start an on-demand mount and dismount of an Exchange database • Restore Exchange databases from either local or remote bookmarks to the production Exchange server in seconds

23. How this solution uses RM RM automates RecoverPoint application-consistent replicas and performs Exchange log truncation • 24 application-consistent (VSS) snapshots in a 24-hour cycle • In addition to maintaining hourly application-consistent snapshots initiated by RM, RP journal maintains many more crash-consistent snapshots from which Exchange databases can easily be recovered • RM application set is created for each Exchange Mailbox server virtual machine. • Application set includes all ten databases configured on the server • This design aligns with the RP CG design, where each consistency group contains all of the Exchange databases and logs for a specific Mailbox server

24. Replication Manager Design • RM Application Set configuration • Created for each Mailbox VM • Includes 10 DB’s per Mailbox Server • Design aligned with RecoverPoint

25. Special Environment Variable for RM • In this solution each RecoverPoint consistency group is configured with an additional replication set for the Mailbox server OS LUN that resides on the VMware VMFS datastore volume • This configuration creates a potential conflict between Replication Manager and RecoverPoint, because the Microsoft VSS framework does not support VMFS data stores • To resolve this conflict, environment variable is created on each Exchange Mailbox server virtual machine with Replication Manager Agent installed: ERM_RP_EXTRA_DEVS_ALLOWED=1 • With this environment setting in place • RecoverPoint continues to provide crash-consistent replicas of all LUNs attached to the Exchange Mailbox server virtual machine (including the OS VMFS volume) • Replication Manager continues to provide application-consistent replicas of all Exchange RDM volumes

26. RM Replication options • In this solution, RM jobs are configured with two Replica Type options to protect the Exchange Server 2010 databases: • Online Full • Online Copy • Online Full jobs are set up for daily backups • Online Copy jobs are set up to run at hourly intervals during business hours to provide application-consistent recovery (24 snapshots per 24 hours)

27. BOOKMARK BOOKMARK LUN LUN RecoverPoint RecoverPoint SAN SAN RecoverPoint + RM = Integrated Local/Remote Protection Replication Manager Server Exchange Mount Host Exchange Production WAN Production LUN Local CDP Copy Local CDP Journal Remote CRR Journal Remote CRR Copy • Replication Manager server freezes application • Replication Manager server requests VSS-compliant bookmark • Replication Manager server thaws application

28. Site Recovery Manager Core Capabilities Centralized managementfor DR Create, test, update and execute recovery plans from a single point of management Seamless integration with Virtual Center Disaster recovery automation Build recovery process in advance Automate testing of recovery plans Automate execution of recovery process Simplified setup and integration Allocate and manage recovery resources Easy integration with leading vendors’ storage replication systems Virtual Center Site Recovery Manager Virtual Machines ESX Server ESX Server ESX Server ESX Server Servers Storage

29. Key SRM Components Recovery site Protected site VC Server 1 VC Server 2 VC 2 DB VC 1 DB SRM Server 1 SRM Server 2 SRM 2 DB SRM 1 DB Storage Replication Adapter Storage Replication Adapter Array 1 Array 2 RecoverPoint replication RecoverPoint replication

30. vCenter SRM Requirements SRM requirements for the vSphere configuration at each site: Each site must include a vCenter server containing at least one vSphere data center. The recovery site must support array‐based replication with the protected site, and the recovery site must have hardware and network resources that can support the same virtual machines and workloads as the protected site. At least one virtual machine must be located on a data store that is replicated by RecoverPoint at the protected site. The protected and recovery sites must be connected by a reliable IP network. Storage arrays may have additional network requirements. The recovery site must have access to the same public and private networks as the protected site, although the recovery site does not necessarily require access to the same range of network addresses. VMware tools must be installed on all virtual machines.

31. SRM Configuration Steps Install and configure SRM with the RecoverPoint SRA adapter. Configure the connection between the protected and recovery sites. Configure RecoverPoint array managers. Configure resource inventory mappings. Configure protection groups. Create the recovery plan. Customize virtual machine recovery options, including IP customization.

32. SRM Protection Groups An SRM protection group is a collection of virtual machines that all use the same datastore group (the same set of replicated LUNs) and that all fail over together. For this solution, an SRM protection group is created for each Exchange Mailbox VM.

33. SRM Protection Groups (cont.) After a protection group is created, shadow VMs are automatically created in the recovery site vCenter inventory. They act as placeholders for the virtual machines that can be failed over with SRM. The shadow VMs cannot be started independently from SRM and are removed if their protection group is deleted.

34. SRM Configuration — Recovery Plans

35. SRM 5 Features for Multi-subnet Data Centers • Recovery and Reprotectoptions • IP customization • Power-on priority and dependencies

36. Changing the DAG IP address at the Recovery Site Set-DatabaseAvailabilityGroup-Identity <DAG Name>-DatabaseAvailabilityGroupIPAddresses <new DAG IP-address at recovery site>

37. Testing an SRM Recovery Plan • Recovery plans can be tested at any time without interrupting replication or the business’s RPO. • Predict how much time the recovery of the virtual environment is likely to take. • Administrators can quickly access a replica of the entire protected environment for testing purposes. • Automatically generated summary reports can be used to demonstrate compliance with regulatory requirements.

38. Testing an SRM Recovery Plan (cont.)

39. SRM Site Failover Test Results Failover of all Mailbox Servers from Site A to Site B Results include DNS name change and IP changes

40. Site Failback with SRM SRM 5 provides automatic failback functionality RecoverPoint SRA version 2.0 integrates with SRM 5 This functionality enables you to perform an automated failback operation after a planned or unplanned failover

41. SRM Failback Process Verify all network communications between the recovery site and the original protected site. Verify connectivity between vCenter servers. Ensure all resource mappings are in place. Ensure no changes need to be made to SRM protection groups or protected virtual machines. Modify the recovery plan to update any custom scripts. For example, update Exchange DAG IP addresses that have changed. Also update CAS array IP addresses if the CAS array was previously replicated. To perform failback: Incrementally—Use the RecoverPoint or Unisphere management console to replicate data and resynchronize configuration settings from the recovery site back to the originally protected site. Automatically—Initiate “Reprotect” from the SRM management interface. When failback process completed, ensure that all Microsoft Exchange services are started and the databases are mounted. Verify email flow and user access.

42. Recovery with Replication Manager

43. RecoverPoint Journal Usage With Exchange Server 2010 Under Load • LoadGen workload for 5,000 users per server with 150 sent/received messages per user • Hourly application-consistent (VSS) bookmarks for a RecoverPoint consistency group with all of the LUNs for a single Mailbox server with 10 databases • Automatic crash-consistent (VSS) bookmarks for a RecoverPoint consistency group with all of the LUNs for a single Mailbox server with 10 databases • Nightly scheduled backup job initiated by Replication Manager *Percentages are based on a 375 GB usable journal space (500 GB minus 25 percent reserved by RecoverPoint) provisioned for each consistency group and 13.6 TB of replicated Exchange data (80 percent of 17 TB provisioned storage).

44. DPA Reporting — RP Journal Utilization

45. Press In Case of Disaster Summary • VMware vCenter Site Recovery Manager and EMC RecoverPoint make Exchange 2010 Disaster Recovery… Rapid Automate disaster recovery process Eliminate complexities of traditional recovery Reliable Ensure proper execution of recovery plans Enable easier, more frequent tests Manageable Centrally manage recovery plans Make plans dynamic to match environment Affordable Utilize recovery site infrastructure Reduce management costs • White paper for this solution is published here:http://www.emc.com/collateral/hardware/white-papers/h8891-emc-protection-fr-microsoft-exchng-servr2010.pdf