1EMC CONFIDENTIAL—INTERNAL USE ONLY FAST VP and Exchange Server 2010 Don Turner Consultant Systems Integration Engineer Microsoft TPM

2EMC CONFIDENTIAL—INTERNAL USE ONLY Introduction Don Turner –Consultant Systems Integration Engineer –Contact details –Work in Txomin Barturen’s team within the Microsoft TPM –Currently focused on Exchange and things Microsoft (less SQL) on VMAX –Background Previously Per-Sales Technology Business Consultant specializing in EMC products and Exchange Server 2003/2007/2010 in UK Technical Architect for Windows Server, AD and Exchange.

3EMC CONFIDENTIAL—INTERNAL USE ONLY Agenda Brief talk on the EMC version of the Microsoft Exchange Server mailbox role calculator Why FAST VP Testing and test results

4EMC CONFIDENTIAL—INTERNAL USE ONLY Why FAST for Exchange Server 2010? Exchange Server sizing recap –Sized for 100% of users –Not all users accessing mailbox at the same time, running at a lower utilization –Not accurately sized (SWAG) –Placement of users in mailbox stores and / or servers by name not by IO profile –All disks procured for the Exchange environment are predominantly the same: Speed 10K/15K RAID type, RAID10/RAID 5/RAID 6 –Not usually mixed speed or RAID on deployment This differing of I/O profiles across the storage platform can mean that: –Some LUNs are over-utilized –Some LUNs are under-utilized

5EMC CONFIDENTIAL—INTERNAL USE ONLY FAST VP for Exchange Server 2010 Exchange Sizing recap –It will always be an estimation of the number of disk drives that are required. It is only when the Exchange Server mailbox server is in production, with users carrying out their daily functions and effective performance monitoring is carried out, can the real workload be verified.

6EMC CONFIDENTIAL—INTERNAL USE ONLY FAST VP for Exchange 2010 cont Virtual Provisioning and FAST VP now gives us the tools to provision the initial deployment at a more cost effective price point. No longer have to provision “10GB mailboxes” up front. Thin pools and a mix of FC and SATA can meet both the capacity requirements and the performance, using FAST VP to put the correct data on the correct tier of storage for the initial deployment.

7EMC CONFIDENTIAL—INTERNAL USE ONLY VMAX Config

8EMC CONFIDENTIAL—INTERNAL USE ONLY Initial Thin Pool configuration 2 Disk Groups –2TB SATA 35physical drives –600GB 15K FC 189 physical drives 2 Thin Pools DB –600GB FC 420 Data Devices 10 Thin Devices –2TB SATA 100 Data Devices 10 Thin Devices 1 Thin Pool Log –600GB FC 30 Data Devices 10 Thin Devices

9EMC CONFIDENTIAL—INTERNAL USE ONLY FAST VP – Settings & Policy

10EMC CONFIDENTIAL—INTERNAL USE ONLY Setting The Jetstress Environment 36 hour Jetstress tests used to determine the functionality of FAST VP. Databases created before FAST VP enabled FAST settings –workload analysis period set to 4 hours –Time to sample before first analysis set to 4 hours Typically, an Exchange Server 2010 mailbox server will be allocated storage from a single VMAX storage group (which is also in the FAST VP Policy). A single Hyper-V server was allocated LUNs from that storage group and 4 VM’s were used to simulate differing loads over 10 database stores. All LUNs were provisioned on thin devices from the 600GB FC pool Jetstress cannot run successful tests and compile the reports in a multi threaded scenario. First Test will report but all other reports will fail, perfmon data is still captured.

11EMC CONFIDENTIAL—INTERNAL USE ONLY Jetstress Multi-host Test new feature

12EMC CONFIDENTIAL—INTERNAL USE ONLY Setting The Jetstress Environment Tests run were: –600GB FC 15k RAID 5(3+1) 3 40 threads 2 30 threads 3 20 threads 2 5 threads Tests were run with and without BDM to determine whether the constant access would make a differenc

13EMC CONFIDENTIAL—INTERNAL USE ONLY FAST VP – Getting the stats Scripts were run at 60 minute intervals to gather the thin pool allocation and piped into a text file. symcfg –sid 0587 show –pool FC_R5_DB –thin –detail –mb >>no_bdmfcthinpool.txt symcfg –sid 0587 show –pool SATA_R10_DB – thin –detail –mb >>no_bdmsatathinpool.txt

14EMC CONFIDENTIAL—INTERNAL USE ONLY FAST VP – Getting the stats SATA No BDM SATA BDM

15EMC CONFIDENTIAL—INTERNAL USE ONLY Summary –Sizing for Exchange is more common sense and now we have the tools to mix drive technologies and RAID types for the initial deployment –Virtual Provisioning and FAST VP must be the “Value Add” for running Exchange Server 2010 on VMAX –DAS is not the ONLY option