1© Copyright 2012 EMC Corporation. All rights reserved. EMC BACKUP AND RECOVERY FOR MICROSOFT EXCHANGE AND SHAREPOINT 2010 SERVERS EMC Avamar, EMC VNX, VMware vCenter EMC Solutions Group March 2012

2© Copyright 2012 EMC Corporation. All rights reserved. Agenda  Who we are and what we do  Proven Solutions approach  Business case  Solution  Solution objectives  Key benefits  Reference architecture  Network design  Customer profiles  Hardware resources  Software resources Disk layout Avamar deployment SharePoint 2010 user and SQL Server CPU performance Exchange 2010 mailbox server performance Backup test types Comparative backup times Comparative restore times Deduplication measurements Conclusion

3© Copyright 2012 EMC Corporation. All rights reserved.

4 Who we are and what we do 1. Solutions based on a combination of: HardwareSoftwareServices Proven Solution 2. Addressing customer business and technical challenges 3. Microsoft application centric, focusing on: Exchange, SQL Server, and SharePoint 4. Reference Architectures: Total Cost of Ownership (TCO) and Return on Investment (ROI) focus Tested, validated, documented Delivering measurable, predictable business results

5© Copyright 2012 EMC Corporation. All rights reserved. Proven Solutions approach Capture & Define Test and Validate DocumentPublish Singapore Shanghai, China Cork, Ireland Hopkinton, MA Santa Clara, CA Vienna, Austria Requirements

6© Copyright 2012 EMC Corporation. All rights reserved.

7 Business case  Data is one of the most valuable assets a company can own.  Downtime can represent failure to critical business processes, which can effectively halt business operations and lead to lost revenue, regulatory fines, and, potentially, lost customers.

8© Copyright 2012 EMC Corporation. All rights reserved. Solution  This solution offers an efficient approach to protect Microsoft Exchange 2010 and Microsoft SharePoint 2010 on a physical or virtualized environment. The solution uses a virtualized environment.  Avamar provides comprehensive backup and recovery for Microsoft environments by using Avamar 6.0 Volume Shadow Copy Services(VSS) agent.  This solution tests and validates Avamar and provides recommendations and best practices for using Avamar to back up Microsoft Exchange and SharePoint based on the test results.

9© Copyright 2012 EMC Corporation. All rights reserved. Solution objectives ObjectivesOverall results Prove Avamar as a comprehensive backup solution for Microsoft environment. Avamar was proved as a working solution for SharePoint and Exchange. Determine the backup solution performance and scalability. During Avamar backups, CPU load was high on the SQL Server and Exchange mailbox server, even though application performance was not affected. Determine backup deduplication ratios for each application. Deduplication rates for Avamar was good for first full backups and very high for subsequent backups. Demonstrate a granular restore out of a VSS backup. Exchange Granular Level Recovery (GLR) worked well for restores from Avamar. Exchange GLR cannot restore mailboxes containing over 21,000 items and is case sensitive to the database names – to be fixed in the next release. SharePoint granular restore from Avamar worked well. Demonstrate database-level recovery.Database restores from Avamar for Exchange and SharePoint worked well with good performance times.

10© Copyright 2012 EMC Corporation. All rights reserved. Key benefits Enables a rapid yet application-consistent backup and restore using Microsoft VSS framework. Enables fast recovery to support strict recovery time objectives (RTOs) for databases and single items without requiring a slow item-level based backup. Significantly reduces backup windows and backup-storage footprints by using Avamar client-side data deduplication to only store unique daily changes, while always maintaining daily full backups for immediate single-step restore. Provides easy management by using one Avamar GUI for Avamar backups. Provides hardware load balancing that introduces redundancy to SharePoint and improves SharePoint farm performance.

11© Copyright 2012 EMC Corporation. All rights reserved.

12© Copyright 2012 EMC Corporation. All rights reserved. Reference Architecture

13© Copyright 2012 EMC Corporation. All rights reserved. Network design

14© Copyright 2012 EMC Corporation. All rights reserved. Customer profiles DetailsQuantity/Type/Size Exchange Server 2010 Mailbox count (2,500 active per server)5,000 Mailbox size2 GB IOPS (per mailbox)0.15 IOPS (150 messages per day) Disk type2 TB NL-SAS – 7.2k RAID 1/0 SharePoint Server 2010 User count6,000 users at 10% concurrency Content size2.5 TB content Content database sizes55 – 200 GB Disk type600 GB SAS – 10k RAID Site collections15 Sites per site collection Document sizes200k - 2 Mb

15© Copyright 2012 EMC Corporation. All rights reserved. Hardware resources EquipmentUsed forQuantityConfiguration ESX Servers VMware, Exchange, SharePoint GB of RAM 32 core 146 GB RAID 5 internal HDD Management servers VMware vCenter Server 1 16 GB of RAM Dual core EMC VNX5500 VMWare virtual machines Exchange databases and logs SharePoint content databases and logs 1 Exchange – NL-SAS SharePoint – SAS EMC Avamar Backup of SharePoint and Exchange databases 1 Gen 4, 6-node OS version 6.0 SP1

16© Copyright 2012 EMC Corporation. All rights reserved. Software resources SoftwareVersion Microsoft Windows Server2008 R2 Enterprise Edition Microsoft Exchange Server2010 SP1 Enterprise Edition Microsoft SharePoint Server2010 Enterprise Edition Microsoft SQL Server2008 R2 Enterprise Edition EMC Avamar Windows Client6.0 SP1 EMC Avamar Windows Exchange VSS Plug-in6.0 SP1 EMC Avamar Windows Exchange GLR Plug-in6.0 SP1 EMC Avamar Windows SharePoint VSS Plug-in6.0 SP1 Kroll Ontrack PowerControls6.1 VMware vSphere4.1

17© Copyright 2012 EMC Corporation. All rights reserved. Disk layout

18© Copyright 2012 EMC Corporation. All rights reserved. Avamar deployment Avamar was deployed with:  One utility node  Five storage nodes Each Avamar node has:  Dual internal network connections  One external network connection

19© Copyright 2012 EMC Corporation. All rights reserved.

20© Copyright 2012 EMC Corporation. All rights reserved. SharePoint 2010 user and SQL Server CPU performance

21© Copyright 2012 EMC Corporation. All rights reserved. Exchange 2010 Mailbox Server performance Performance counterTarget Baseline workload (Exchange) Combined workload (Exchange + SharePoint Server) Avamar backup under workload Processor\%Processor time <80%30%38%90% MSExchange database\I/O database reads (attached) average latency <20 ms61017 MSExchange database\I/O database writes (attached) average latency <20 ms <reads avg. 112 MSExchange database\I/O database reads (recovery) average latency <200 ms MSExchange database\I/O database writes (recovery) average latency <200 ms2215 MSExchange database\IO log read average latency <20 ms333 MSExchange database\IO log writes average latency <20 ms336 MSExchange Replication(*)\ReplayQueueLength <2111 MSExchangeIS\RPC requests <70222 MSExchangeIS\RPC averaged latency <10 ms333

22© Copyright 2012 EMC Corporation. All rights reserved. Backup test types  No data change and no load backup This backup test gave a baseline backup result that EMC could compare to other backup tests. Even though there is no data change, there is still time, CPU, IOPS, and processing costs related to segmenting and hashing functions.  Percentage data change with no load backup This test was a percentage data change with no load. For SharePoint this was approximately 10 percent, and for Exchange this was approximately 3 percent. This test simulated a customer environment where backups would take place daily during a backup window where there was no user load.  Same daily percentage data change with full user load backup The final backup test simulated backups run after a data change rate of 10 percent for SharePoint and 3 percent for Exchange and with a full user load at the same time. This would be the case for customers who have no downtime window for backups, for example, customers who have to be running 24 hours a day but still want to do daily backups.

23© Copyright 2012 EMC Corporation. All rights reserved. Comparative backup times Exchange backups 3.4 TB per server (Hours) SharePoint backups 2.7 TB per database (Hours)

24© Copyright 2012 EMC Corporation. All rights reserved. Comparative restore times SharePoint restore times (Hours) Exchange restore times (Hours)

25© Copyright 2012 EMC Corporation. All rights reserved. Deduplication measurements

26© Copyright 2012 EMC Corporation. All rights reserved. Conclusion ObjectivesDetailed results Show backup times for SharePoint 2010 and Exchange 2010 to Avamar With the recommended eight cores, CPU load on SharePoint SQL Server and Exchange mailbox servers was at 90 percent. Microsoft does not recommend such a high CPU usage for SQL Server or Exchange, although it did not affect application performance in EMC’s tests. Show deduplication rates for backups to Avamar Initial deduplication rate of 1.67:1 for Exchange data Initial deduplication rate of 1.98:1 for SharePoint data Subsequent data change deduplication rate of 85:1 for Exchange data Subsequent data change deduplication rate of 12.61:1 for SharePoint data Show restore times from Avamar for SharePoint 2010 and Exchange 2010 Restore times for Avamar were acceptable for both Exchange and SharePoint Demonstrate how to improve backup times for Avamar Avamar backup times can be improved by adding more cores to the SQL Server and Exchange mailbox servers. Show how Avamar affects SharePoint and Exchange Avamar backups used almost all of the spare CPU of the SQL Server and Exchange mailbox servers, but application performance was not affected by this. Show in which environments Avamar is best suited With the advent of Avamar 6.0 and its multi-streaming backup capability, Avamar backs up and restores everything from small to enterprise-level environments, as proven in this solution.

27© Copyright 2012 EMC Corporation. All rights reserved.