HP 3PAR StoreServ ,000 Mailbox Resiliency Exchange 2010 Storage Solution

Transcription

1 Technical white paper HP 3PAR StoreServ ,000 Mailbox Resiliency Exchange 2010 Storage Solution Table of contents Overview... 2 Disclaimer... 2 Features of the tested solution... 2 HP 3PAR StoreServ 7000 Storage... 2 Solution description... 4 Storage configuration... 4 Mailbox configuration primary site operational... 5 Mailbox configuration primary site unavailable (planned or unplanned)... 6 Tested deployment... 7 Best practices... 8 Test results summary... 9 Reliability... 9 Storage performance results... 9 backup / recovery performance Conclusion Appendix A Stress testing Appendix B Performance testing Appendix C Streaming backup testing Appendix D Soft recovery testing For more information... 87

2 Overview This solution brief provides an HP 3PAR StoreServ 7400 storage solution for Microsoft Exchange Server 2010 (Exchange), based on the Microsoft Exchange Solution Review Program (ESRP) Storage Program. The ESRP Storage Program was developed by Microsoft Corporation to provide a common storage testing framework for vendors to provide information on their storage solutions for Microsoft Exchange Server software. For more details on the Microsoft ESRP V3.0 Storage Program, please see: Tested with: ESRP Storage Version 3.0 Test Date: November 2012 Disclaimer HP produced this document independently of Microsoft Corporation. Microsoft Corporation expressly disclaims responsibility for, and makes no warranty, express or implied, with respect to the accuracy of the contents of this document. Features of the tested solution This solution implements the Availability Group (DAG) mailbox resiliency features found in Microsoft Exchange Server 2010 (Exchange). This feature is the base component of the high availability and site resilience framework built into Exchange. A DAG is a group of up to 16 mailbox servers that host a set of databases and provides database-level recovery from failures that affect individual servers or databases. This solution brief describes a tested configuration for deploying Exchange in a 60,000 user mailbox resilient environment. The performance results and best practices outlined in this document provide tested guidelines for configuring Exchange with the HP 3PAR StoreServ 7400 and HP ProLiant BL460c Gen8 BladeSystem Servers in a SAN solution. This solution used two DAGs to support 60,000 mailboxes, each with a 2 GB mailbox capacity and a 0.14 IOPS workload per user. To provide mailbox resiliency, there are three copies of each database; two copies located in the primary site and one copy located in the disaster recovery site. The primary site hosts all 60,000 mailboxes during normal operations. The performance results are from the testing of the disaster recovery site. HP has developed the HP Sizer for Microsoft Exchange Server 2010 to assist customers with proper server and storage sizing for their Exchange Server 2010 deployments. The algorithms developed and implemented in this tool are based upon extensive testing of Exchange Server 2010 server roles and technologies, HP s deep experience with Microsoft Exchange, and intricate knowledge of server CPU, memory and subsystems. This tool is free to download and use, and is designed to simplify configuration across a broad range of deployments. For more information, please visit: hp.com/solutions/microsoft/exchange2010/sizer HP 3PAR StoreServ 7000 Storage HP 3PAR StoreServ 7000 Storage extends the innovative HP 3PAR StoreServ product line to the midrange with industry leading performance and features at the price you need. Spend less time managing storage, get more features for less money, and do it all without sacrificing performance or future scalability. HP 3PAR StoreServ 7000 Storage provides high performance and guarantees to double your virtual machine density. With hardware assisted thin storage, it is the only platform that guarantees a 50% reduction in capacity requirements. HP 3PAR StoreServ is also the first product family with a common architecture that meets small and medium business (SMB) needs and spans to the largest global enterprise giving you access to the same features as the world s largest service providers. You can start small and grow without painful upgrades down the road. 2

3 Efficient Get thin and stay thin Thin technologies unique to the HP 3PAR StoreServ family can reduce capacity requirements by 50%. Purchase only what you need, as you need it so you can focus resources on growing your business, not maintaining your storage. Additionally, the HP 3PAR ASIC with Thin Built In features an efficient, silicon-based zero-detection mechanism. This unique hardware capability gives HP 3PAR StoreServ Storage the power to remove allocated but unused space without impacting performance. Data center virtualization Increase virtualization return on investment. Double virtual machine density on your physical servers, spend up to 90 percent less time managing your storage, and support your virtualization deployment with 50 percent less storage capacity. HP 3PAR StoreServ is built from the ground up to deliver performance that exceeds the demands of virtualized data centers along with transformative levels of simplicity, agility, and efficiency. Service levels With policy-based autonomic sub-lun tiering, you can balance the cost of capacity and the cost of performance and put the right data on the right storage tier at the right time. Do more with less With HP 3PAR StoreServ Storage you can purchase up to 75 percent less capacity meaning less equipment to house, fewer disks to power and cool, less hardware to retire after it has reached its end of life, and a reduced carbon footprint. Autonomic It s like breathing you don t even have to think about it. Simplify, automate, and expedite storage management by handling storage provisioning, tiering, and change management autonomically intelligently, at a sub-system level, and without administrator intervention. SmartStart Software software designed to get you off to a quick start with your new HP 3PAR StoreServ 7000 system. Common architecture Access the same features as the world s largest service providers with a common architecture that meets SMB needs and spans to the largest global enterprise. Resilient Secure multi-tenancy Consolidate with confidence. Achieve higher service levels for more users and applications with less infrastructure. HP 3PAR StoreServ Storage is designed to support massive consolidation by supporting mixed workloads and secure administrative segregation of users, hosts, and application data. Deliver higher performance levels, greater availability, and next-generation functionality to multiple user groups and applications from a single storage system. Scalable HP 3PAR StoreServ 7000 provides affordable entry pricing and unique, non-disruptive scalability to four nodes. High Availability Featuring the same mesh-active architecture as all HP 3PAR StoreServ products, HP 3PAR StoreServ 7000 offers the highest levels of data availability and protection for the midrange. Intelligent data striping across all available enclosures provides HA Cage, the ability to maintain availability even when a whole drive enclosure fails. HP 3PAR Persistent Cache in four node configurations eliminates performance impacts that result from unplanned component failures, making it a must-have for maintaining service levels in the virtual data center a feature that you can t get from any other midrange storage platform. Storage federation Meet the needs of today s data center with the ability to move data and workloads between arrays without impact to applications, users, or services. Simply and non-disruptively shift data between any model HP 3PAR StoreServ system without additional management layers or appliances. Storage federation on HP 3PAR StoreServ Storage can also help you improve availability in clustered VMware environments. Mixed workload Mixed workload support serves transactional and throughput-intensive workloads from a single device. The purpose-built HP 3PAR ASIC delivers mixed workload support to alleviate performance concerns and cut traditional array costs. Transaction- and throughput-intensive workloads run on the same storage resources without contention, thereby cutting array purchases in half. For more details on the features and offerings of the HP 3PAR 7400 StoreServ Storage, please visit the following site and/or contact your HP sales representative. 3

4 PAR StoreServ Drive Shelf M Drive Shelf M Drive Shelf M Drive Shelf M Drive Shelf M Drive Shelf M Drive Shelf M Drive Shelf M Drive Shelf M6720 Reset Reset UID UID Gb SAN Switch 8Gb SAN Switch UID 15K 146 GB HP ProLiant BL460c Gen8 15K 146 GB UID 15K 146 GB HP ProLiant BL460c Gen8 15K 146 GB UID 15K 146 GB HP ProLiant BL460c Gen8 15K 146 GB UID 15K 146 GB HP ProLiant BL460c Gen8 15K 146 GB OK UID 15K 146 GB HP ProLiant BL460c Gen8 15K 146 GB UID 15K 146 GB HP ProLiant BL460c Gen8 15K 146 GB Technical white paper HP 3PAR StoreServ ,000 Mailbox Resiliency Exchange 2010 Storage Solution Solution description The solution brief provides tested best practices to help administrators implement an Exchange deployment, with the following requirements: 60,000 mailbox users 0.14 IOPS workload per user 2 GB mailbox size Availability Group (DAG) deployment with 2 DAGs. Each DAG has 6 mailbox servers in the primary site and 3 mailbox servers in the disaster recovery site, for a total of 18 mailbox servers across the entire solution 3 copies of each mailbox database (1 active / 2 passive) background maintenance (DBM) enabled Designed for server and site resiliency TB NL disks for the Exchange databases and logs Storage deployed in a single CPG using RAID 1. See the Storage configuration section for more information Storage configuration In this solution, the HP 3PAR StoreServ 7400 has been configured with 216 2TB NL LFF disks. The disks are configured into a single CPG with RAID 1 (2 data). The step size has been set to 512 KiB. There are 13 VVols (12 /Log LUNs and 1 Restore LUN) presented to each server. Each server has 2 paths (12 total paths) to the storage for high availability and load balancing. Figure 1 below illustrates the major hardware components of the solution. Figure 1: Major hardware components in solution brief : HP 3PAR StoreServ : 2TB NL LFF Drives 3: HP Brocade 8Gb SAN Switches for HP BladeSystem c-class 4: HP ProLiant BL460c Gen8 BladeSystem Servers 5: HP BladeSystem c7000 Enclosure 4

5 Mailbox configuration primary site operational Figure 2 shows the mailbox layout for active and passive database copies when the primary site is operational. This solution brief provides tested best practices to help administrators implement the Exchange deployment, with the following requirements: 60,000 mailbox users 0.14 IOPS workload per user 2 GB mailbox size Each mailbox server in the primary site has 12 database copies (6 active and 6 passive). All active database copies are accessed on the primary site during normal operations. Each mailbox server in the disaster recovery site has 12 database copies (12 passive). Background database maintenance (BDM) enabled Figure 2: Normal operation all mailboxes hosted on Primary Site Active Passive Primary Site MBX1 MBX2 MBX3 MBX4 MBX5 MBX6 Disaster Recovery Site MBX7 MBX8 MBX9 DAG 1 DB1 DB1 DB2 DB3 DB4 DB5 DB1 DB2 DB3 DB6 DB2 DB3 DB4 DB5 DB6 DB4 DB5 DB6 DB7 DB8 DB7 DB8 DB9 DB10 DB7 DB8 DB9 DB32 DB33 DB34 DB35 DB36 DB36 DB35 DB36 DB34 MBX10 MBX11 MBX12 MBX13 MBX14 MBX15 MBX16 MBX17 MBX18 DAG 2 DB1 DB1 DB2 DB3 DB4 DB5 DB1 DB2 DB3 DB6 DB2 DB3 DB4 DB5 DB6 DB4 DB5 DB6 DB7 DB8 DB7 DB8 DB9 DB10 DB7 DB8 DB9 DB32 DB33 DB34 DB35 DB36 DB36 DB35 DB36 DB34 5

6 Mailbox configuration primary site unavailable (planned or unplanned) Figure 3 shows the mailbox layout for active and passive database copies when the primary site is unavailable due to a planned or unplanned event. This solution brief provides tested best practices to help administrators implement the Exchange deployment, with the following requirements: 60,000 mailbox users 0.14 IOPS workload per user 2 GB mailbox size Primary site s database copies are unavailable due to a planned or unplanned event Each mailbox server in the disaster recovery site has 12 database copies (12 active). All active database copies are accessed on the disaster recovery site. Background database maintenance (BDM) enabled Limitations of the tested single copy Disaster Recovery Site: You may lose quorum and have to manually re-form the DAG All mailbox databases will be limited to a single copy for the duration of the Primary Site being offline A single mailbox server failure will cause several mailbox databases to dismount Figure 3: Primary site unavailable all mailboxes hosted on Disaster Recovery Site Active Passive DAG 1 Primary Site X X X X X X MBX1 MBX2 MBX3 MBX4 MBX5 MBX6 Disaster Recovery Site MBX7 MBX8 MBX9 DB1 DB1 DB2 DB3 DB4 DB5 DB1 DB2 DB3 DB6 DB2 DB3 DB4 DB5 DB6 DB4 DB5 DB6 DB7 DB8 DB7 DB8 DB9 DB10 DB7 DB8 DB9 DB32 DB33 DB34 DB35 DB36 DB36 DB35 DB36 DB34 X X X MBX10 MBX11 MBX12 MBX13 MBX14 MBX15 MBX16 MBX17 MBX18 DAG 2 X X X DB1 DB1 DB2 DB3 DB4 DB5 DB1 DB2 DB3 DB6 DB2 DB3 DB4 DB5 DB6 DB4 DB5 DB6 DB7 DB8 DB7 DB8 DB9 DB10 DB7 DB8 DB9 DB32 DB33 DB34 DB35 DB36 DB36 DB35 DB36 DB34 6

7 Tested deployment The following tables summarize the tested environment. Simulated Exchange configuration Number of Exchange mailboxes simulated 60,000 Number of Availability Groups (DAGs) 2 Number of mailbox servers per DAG 9 Number of mailboxes/database 833 Simulated profile: operations per second per mailbox (IOPS, include 20% headroom) Background database maintenance (BDM) 0.14 Tested with 24/7 BDM enabled % storage capacity used by Exchange databases 70% Storage hardware Storage connectivity Fibre Channel Storage model and firmware version HP 3PAR StoreServ 7400 Firmware Version: Number of storage controllers Number of storage ports Maximum bandwidth of storage connectivity to host Switch model and firmware version HBA model and firmware version 2 controller nodes, each controller node has 8 GB of control cache and 8 GB of data cache 12 Fibre Channel ports available (12 used 2 Paths per Host) 96 Gb/s (12 ports * 8Gb Fibre Channel) HP Brocade 8Gb SAN Switch for HP BladeSystem c-class Firmware Version: v7.0.2 HP QHM2572 8Gb FC HBA Firmware Version: Number of HBAs per host 2 Host server type HP ProLiant BL460c Gen8 Total number of disks tested in solution 216 Maximum number of disks that can be hosted in the storage 480 7

8 Storage software HBA Driver STOR Miniport HBA Queue Depth Setting 321 Multipathing Host OS Microsoft MPIO Windows Server 2008 R2 Enterprise with SP1 ESE.dll file version Storage disk configuration (mailbox & log disks) Disk type, speed, and firmware revision Raw capacity per disk (GB) 2 TB NL Disk Drive Firmware: ,938 GB Number of physical disks in test 216 Total raw storage capacity (GB) RAID level 418,608 GB* RAID 1 (2 data) Set Size 2 Step Size (KiB) 512 Provisioning Total formatted capacity (GB) Fully Provisioned 178,200 GB Storage capacity utilization 43% capacity utilization 30% * Capacity of drives, and therefore the raw data capacity of the disk array, is based on 1KB = 1000 bytes, not 1024 bytes. This means that 1 GB = 1,000,000,000 bytes, not (1,073,741,824 bytes) Best practices Exchange Server is a disk-intensive application. For Exchange 2010 best practices on storage design from Microsoft, please visit For Exchange Server solution guidance, please visit HP at hp.com/solutions/microsoft/exchange. The best practices for this solution are: Drivers and Firmware Ensure firmware and drivers for all hardware in the solution are up to date. For more information, please see: Multipathing Install Microsoft s Multipath (MPIO). Multipathing allows for redundant physical paths to the storage and load balancing of the. For more information, please see:

9 Jetstress 2010 Before installing Exchange Server 2010, test your storage solution with Jetstress to ensure it is configured optimally and meets your requirements. For more information on Jetstress, please see: Mailbox Copies Site resiliency was achieved with 3 copies of the mailbox databases. There are 2 database copies at the primary site and 1 database copy at the disaster recovery site, ensuring business continuity through superior disaster recovery and Exchange availability options. Step Size The step size is configured for 512 KiB. For Exchange deployments, it is recommended to use the largest step size for your selected RAID level. For more information, please see: RAID Level The disks used in this solution were configured as RAID 1 with a set size of 2. RAID 1 and using the largest set size possible is recommended for Exchange deployments with disks. For more information, please see: Shared Logical Disks (LD) Enabling shared LDs is recommended for HP 3PAR storage when deploying Exchange to maximize the benefits of a wide stripe virtualized array. For more information on the -shared feature, please refer to your HP 3PAR documentation or contact your HP Representative. Windows Volumes Ensure that the Windows volumes are formatted with the 64KB allocation unit size for best performance. Test results summary This section provides a high level summary of the test data from ESRP and a reference to the detailed HTML reports which are generated by the ESRP testing framework. For solutions that utilize a uniform building block style where each building block is independent and isolated, ESRP requires testing only one building block. A building block includes six (6) HP ProLiant BL460c Gen8 BladeSystem Servers, a single HP 3PAR StoreServ 7400 with 2-Nodes and 216 2TB disks. However, for production deployments of this solution, a second identical hardware configuration is required. Reliability Reliability testing exercises the storage with the maximum sustainable Exchange load for 24 hours. The goal is to verify the storage can handle the maximum load for an extended amount of time. Both log and database files are analyzed for integrity after the stress test to ensure no database / log corruption. The following list provides an overview: Any errors reported in the saved event log file? There were no relevant errors reported in the event log for the storage reliability testing. Any errors reported during the database and log checksum process? There were no errors reported for the checksum process. Storage performance results The storage performance testing exercises the storage with the maximum sustainable Exchange load for 2 hours. The test measures storage response times under the maximum sustainable Exchange load. The data below is the sum of all logical disk s and an average of all the logical disk latency in the 2 hour test duration. This solution is designed around an Exchange deployment with 2 DAGs. Each DAG has 6 mailbox servers in the primary site and 3 mailbox servers in the disaster recovery site. The performance results tables below are specific to the disaster recovery site when it is hosting all active mailboxes due to the Primary Site being offline (planned or unplanned). 9

10 Individual server metrics The tables below show the sum of across databases and the average latency across all databases on a per server basis. Host 1 Disk Transfers/sec 1921 Disk /sec 1210 Disk /sec 711 Disk Read (ms) Disk Write (ms) 1.96 Transaction Log Log Disk /sec 632 Log Disk Write (ms) 0.58 Host 2 Disk Transfers/sec 1920 Disk /sec 1210 Disk /sec 710 Disk Read (ms) Disk Write (ms) 2.03 Transaction Log Log Disk /sec 633 Log Disk Write (ms) 0.58 Host 3 Disk Transfers/sec 1929 Disk /sec 1215 Disk /sec 714 Disk Read (ms) Disk Write (ms) 2.01 Transaction Log Log Disk /sec 635 Log Disk Write (ms)

11 Host 4 Disk Transfers/sec 1930 Disk /sec 1216 Disk /sec 714 Disk Read (ms) Disk Write (ms) 1.97 Transaction Log Log Disk /sec 636 Log Disk Write (ms) 0.57 Host 5 Disk Transfers/sec 1932 Disk /sec 1217 Disk /sec 715 Disk Read (ms) Disk Write (ms) 2.02 Transaction Log Log Disk /sec 636 Log Disk Write (ms) 0.57 Host 6 Disk Transfers/sec 1938 Disk /sec 1221 Disk /sec 717 Disk Read (ms) Disk Write (ms) 2.02 Transaction Log Log Disk /sec 638 Log Disk Write (ms)

12 Aggregate performance across all servers The table below shows the sum of and the average latency across all servers in the solution. Needed Disk Transfers/sec* 8,400 Disk Transfers/sec 11,570 Disk /sec 7,289 Disk /sec 4,281 Disk Read (ms) Disk Write (ms) 2.00 Transaction Log Log Disk /sec 3,810 Log Disk Write (ms) 0.58 * This row represents the total IOPS necessary to satisfy the IOPS for all mailboxes in the solution. backup / recovery performance There are two test reports in this section. The first one is to measure the sequential read rate of the database files and the second is to measure the recovery / replay performance (playing transaction logs into the database). One important characteristic of the tests is the read rates and log replay rates are measured with all mailboxes under concurrent or simultaneous load. Read-Only Performance This test measures the maximum back up rate for Volume Shadow Copy Service (VSS) aware backup applications. The following table shows the average and sum of the database reads. MB read/sec per database MB read/sec total 2,910 Transaction Log Recovery / Replay Performance This test measures the maximum rate that log files can play against the databases. The following table shows the average rate for log files played. Each log file is 1 MB in size. number of log files played per database 509 time to play one log file (sec)

13 Conclusion The information discussed in this solution brief highlights the tested performance results and configuration best practices for an Exchange Server solution supporting 60,000 2GB mailboxes and a 0.14 IOPS workload per user. The tested solution included an HP 3PAR StoreServ 7400 with 2 Nodes and with 216 2TB NL Disks for the Exchange database storage and transaction logs. The testing demonstrated the storage subsystem is capable of supporting both the IOPS needed for 60,000 Exchange users as well as providing additional performance headroom. The test results and data presented in this document are from the ESRP test framework. The test results are only a guide; customers should test their specific solution to make sure it meets their requirements. The ESRP program is not a benchmarking program. The tests do not measure the maximum throughput for a given solution. Rather, its focus is on producing recommendations from vendors for Exchange Server storage solutions, not direct comparisons among solutions. 13

14 Appendix A Stress testing Stress Test Result Report Test Summary Overall Test Result Machine Name Test Description Test Start Time Test End Time Pass HOST1 11/12/2012 9:37:05 PM 11/13/2012 9:42:41 PM Collection Start Time 11/12/2012 9:39:24 PM Collection End Time 11/13/2012 9:39:13 PM Jetstress Version ESE Version Operating System Windows Server 2008 R2 Enterprise Service Pack 1 ( ) Performance Log C:\Program Files\Exchange Jetstress\24HR_Test\Stress_2012_11_12_21_37_31.blg Sizing and Throughput Achieved Transactional per Second Target Transactional per Second 1400 Initial Size (bytes) Final Size (bytes) Files (Count) 12 Jetstress System Parameters Thread Count 8 (per database) Minimum Cache MB Maximum Cache MB Insert Operations 40% Delete Operations 20% Replace Operations 5% Read Operations 35% Lazy Commits 70% Run Background Maintenance True Number of Copies per 3 Configuration Instance Log path: C:\DBLG1 : C:\DBLG1\Jetstress edb Instance Log path: C:\DBLG2 : C:\DBLG2\Jetstress edb Instance Log path: C:\DBLG3 : C:\DBLG3\Jetstress edb Instance Log path: C:\DBLG4 : C:\DBLG4\Jetstress edb Instance Log path: C:\DBLG5 : C:\DBLG5\Jetstress edb Instance Log path: C:\DBLG6 : C:\DBLG6\Jetstress edb Instance Log path: C:\DBLG7 : C:\DBLG7\Jetstress edb Instance Log path: C:\DBLG8 14

15 : C:\DBLG8\Jetstress edb Instance Log path: C:\DBLG9 : C:\DBLG9\Jetstress edb Instance Log path: C:\DBLG10 : C:\DBLG10\Jetstress edb Instance Log path: C:\DBLG11 : C:\DBLG11\Jetstress edb Instance Log path: C:\DBLG12 : C:\DBLG12\Jetstress edb Transactional Performance MSExchange ==> Instances /sec /sec /sec /sec Instance Instance Instance Instance Instance Instance Instance Instance Instance Instance Instance Instance Background Maintenance Performance MSExchange ==> Instances Maintenance IO /sec Maintenance IO Instance Instance Instance Instance Instance Instance Instance Instance Instance Instance Instance Instance Log Replication Performance MSExchange ==> Instances /sec Instance Instance Instance Instance Instance Instance Instance

16 Instance Instance Instance Instance Instance Total Performance MSExchange ==> Instances /sec /sec /sec /sec Instance Instance Instance Instance Instance Instance Instance Instance Instance Instance Instance Instance Host System Performance Counter Minimum Maximum % Processor Time Available M Free System Page Table Entries Transition Pages RePurposed/sec Pool Nonpaged Pool Paged Page Fault Stalls/sec Test Log11/12/2012 9:37:05 PM -- Jetstress testing begins... 11/12/2012 9:37:05 PM -- Preparing for testing... 11/12/2012 9:37:18 PM -- Attaching databases... 11/12/2012 9:37:18 PM -- Preparations for testing are complete. 11/12/2012 9:37:18 PM -- Starting transaction dispatch.. 11/12/2012 9:37:18 PM -- cache settings: (minimum: MB, maximum: 3.0 GB) 11/12/2012 9:37:18 PM -- flush thresholds: (start: 30.7 MB, stop: 61.4 MB) 11/12/2012 9:37:31 PM -- read latency thresholds: (average: 20 msec/read, maximum: 200 msec/read). 11/12/2012 9:37:31 PM -- Log write latency thresholds: (average: 10 msec/write, maximum: 200 msec/write). 11/12/2012 9:37:40 PM -- Operation mix: Sessions 8, Inserts 40%, Deletes 20%, Replaces 5%, 35%, Lazy Commits 70%. 11/12/2012 9:37:40 PM -- Performance logging started (interval: ms). 11/12/2012 9:37:40 PM -- Attaining prerequisites: 11/12/2012 9:39:24 PM -- \MSExchange (JetstressWin)\ Cache Size, Last: (lower bound: , upper bound: none) 11/13/2012 9:39:24 PM -- Performance logging has ended. 11/13/2012 9:42:38 PM -- JetInterop batch transaction stats: , , , , , , , , , , and /13/2012 9:42:38 PM -- Dispatching transactions ends. 11/13/2012 9:42:38 PM -- Shutting down databases... 11/13/2012 9:42:41 PM -- Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete) and Instance (complete) 11/13/2012 9:42:41 PM -- C:\Program Files\Exchange Jetstress\24HR_Test\Stress_2012_11_12_21_37_31.blg has 5757 samples. 11/13/2012 9:42:41 PM -- Creating test report... 11/13/2012 9:43:31 PM -- Instance has 19.9 for. 16

17 11/13/2012 9:43:31 PM -- Instance has 0.6 for. 11/13/2012 9:43:31 PM -- Instance has 0.6 for. 11/13/2012 9:43:31 PM -- Instance has 19.8 for. 11/13/2012 9:43:31 PM -- Instance has 0.6 for. 11/13/2012 9:43:31 PM -- Instance has 0.6 for. 11/13/2012 9:43:31 PM -- Instance has 19.8 for. 11/13/2012 9:43:31 PM -- Instance has 0.6 for. 11/13/2012 9:43:31 PM -- Instance has 0.6 for. 11/13/2012 9:43:31 PM -- Instance has 19.8 for. 11/13/2012 9:43:31 PM -- Instance has 0.6 for. 11/13/2012 9:43:31 PM -- Instance has 0.6 for. 11/13/2012 9:43:31 PM -- Instance has 19.8 for. 11/13/2012 9:43:31 PM -- Instance has 0.6 for. 11/13/2012 9:43:31 PM -- Instance has 0.6 for. 11/13/2012 9:43:31 PM -- Instance has 19.8 for. 11/13/2012 9:43:31 PM -- Instance has 0.6 for. 11/13/2012 9:43:31 PM -- Instance has 0.6 for. 11/13/2012 9:43:31 PM -- Instance has 19.8 for. 11/13/2012 9:43:31 PM -- Instance has 0.6 for. 11/13/2012 9:43:31 PM -- Instance has 0.6 for. 11/13/2012 9:43:31 PM -- Instance has 19.8 for. 11/13/2012 9:43:31 PM -- Instance has 0.6 for. 11/13/2012 9:43:31 PM -- Instance has 0.6 for. 11/13/2012 9:43:31 PM -- Instance has 19.8 for. 11/13/2012 9:43:31 PM -- Instance has 0.6 for. 11/13/2012 9:43:31 PM -- Instance has 0.6 for. 11/13/2012 9:43:31 PM -- Instance has 19.8 for. 11/13/2012 9:43:31 PM -- Instance has 0.6 for. 11/13/2012 9:43:31 PM -- Instance has 0.6 for. 11/13/2012 9:43:31 PM -- Instance has 19.8 for. 11/13/2012 9:43:31 PM -- Instance has 0.6 for. 11/13/2012 9:43:31 PM -- Instance has 0.6 for. 11/13/2012 9:43:31 PM -- Instance has 19.8 for. 11/13/2012 9:43:31 PM -- Instance has 0.6 for. 11/13/2012 9:43:31 PM -- Instance has 0.6 for. 11/13/2012 9:43:31 PM -- Test has 0 Maximum Page Fault Stalls/sec. 11/13/2012 9:43:31 PM -- The test has 0 Page Fault Stalls/sec samples higher than 0. 11/13/2012 9:43:31 PM -- C:\Program Files\Exchange Jetstress\24HR_Test\Stress_2012_11_12_21_37_31.xml has 5750 samples queried. Stress Test Result Report Test Summary Overall Test Result Machine Name Pass HOST2 Test Description Test Start Time 11/12/2012 9:37:07 PM Test End Time 11/13/2012 9:42:43 PM Collection Start Time 11/12/2012 9:39:33 PM Collection End Time 11/13/2012 9:39:29 PM Jetstress Version ESE Version Operating System Windows Server 2008 R2 Enterprise Service Pack 1 ( ) Performance Log C:\Program Files\Exchange Jetstress\24HR_Test\Stress_2012_11_12_21_37_33.blg Sizing and Throughput Achieved Transactional per Second Target Transactional per Second 1400 Initial Size (bytes) Final Size (bytes)

18 Files (Count) 12 Jetstress System Parameters Thread Count Minimum Cache Maximum Cache Insert Operations 40% Delete Operations 20% Replace Operations 5% Read Operations 35% Lazy Commits 70% Run Background Maintenance True Number of Copies per 3 8 (per database) MB MB Configuration Instance Log path: C:\DBLG1 : C:\DBLG1\Jetstress edb Instance Log path: C:\DBLG2 : C:\DBLG2\Jetstress edb Instance Log path: C:\DBLG3 : C:\DBLG3\Jetstress edb Instance Log path: C:\DBLG4 : C:\DBLG4\Jetstress edb Instance Log path: C:\DBLG5 : C:\DBLG5\Jetstress edb Instance Log path: C:\DBLG6 : C:\DBLG6\Jetstress edb Instance Log path: C:\DBLG7 : C:\DBLG7\Jetstress edb Instance Log path: C:\DBLG8 : C:\DBLG8\Jetstress edb Instance Log path: C:\DBLG9 : C:\DBLG9\Jetstress edb Instance Log path: C:\DBLG10 : C:\DBLG10\Jetstress edb Instance Log path: C:\DBLG11 : C:\DBLG11\Jetstress edb Instance Log path: C:\DBLG12 : C:\DBLG12\Jetstress edb Transactional Performance MSExchange ==> Instances /sec /sec /sec /sec Instance Instance

19 Instance Instance Instance Instance Instance Instance Instance Instance Instance Instance Background Maintenance Performance MSExchange ==> Instances Maintenance IO /sec Maintenance IO Instance Instance Instance Instance Instance Instance Instance Instance Instance Instance Instance Instance Log Replication Performance MSExchange ==> Instances /sec Instance Instance Instance Instance Instance Instance Instance Instance Instance Instance Instance Instance Total Performance MSExchange ==> Instances /sec /sec /sec /sec Instance Instance Instance Instance Instance Instance Instance Instance Instance Instance

20 Instance Instance Host System Performance Counter Minimum Maximum % Processor Time Available M Free System Page Table Entries Transition Pages RePurposed/sec Pool Nonpaged Pool Paged Page Fault Stalls/sec Test Log11/12/2012 9:37:07 PM -- Jetstress testing begins... 11/12/2012 9:37:07 PM -- Preparing for testing... 11/12/2012 9:37:20 PM -- Attaching databases... 11/12/2012 9:37:20 PM -- Preparations for testing are complete. 11/12/2012 9:37:20 PM -- Starting transaction dispatch.. 11/12/2012 9:37:20 PM -- cache settings: (minimum: MB, maximum: 3.0 GB) 11/12/2012 9:37:20 PM -- flush thresholds: (start: 30.7 MB, stop: 61.4 MB) 11/12/2012 9:37:33 PM -- read latency thresholds: (average: 20 msec/read, maximum: 200 msec/read). 11/12/2012 9:37:33 PM -- Log write latency thresholds: (average: 10 msec/write, maximum: 200 msec/write). 11/12/2012 9:37:43 PM -- Operation mix: Sessions 8, Inserts 40%, Deletes 20%, Replaces 5%, 35%, Lazy Commits 70%. 11/12/2012 9:37:43 PM -- Performance logging started (interval: ms). 11/12/2012 9:37:43 PM -- Attaining prerequisites: 11/12/2012 9:39:33 PM -- \MSExchange (JetstressWin)\ Cache Size, Last: (lower bound: , upper bound: none) 11/13/2012 9:39:33 PM -- Performance logging has ended. 11/13/2012 9:42:41 PM -- JetInterop batch transaction stats: , , , , , , , , , , and /13/2012 9:42:41 PM -- Dispatching transactions ends. 11/13/2012 9:42:41 PM -- Shutting down databases... 11/13/2012 9:42:43 PM -- Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete) and Instance (complete) 11/13/2012 9:42:43 PM -- C:\Program Files\Exchange Jetstress\24HR_Test\Stress_2012_11_12_21_37_33.blg has 5758 samples. 11/13/2012 9:42:43 PM -- Creating test report... 11/13/2012 9:43:34 PM -- Instance has 19.8 for. 11/13/2012 9:43:34 PM -- Instance has 0.6 for. 11/13/2012 9:43:34 PM -- Instance has 0.6 for. 11/13/2012 9:43:34 PM -- Instance has 19.8 for. 11/13/2012 9:43:34 PM -- Instance has 0.6 for. 11/13/2012 9:43:34 PM -- Instance has 0.6 for. 11/13/2012 9:43:34 PM -- Instance has 19.8 for. 11/13/2012 9:43:34 PM -- Instance has 0.6 for. 11/13/2012 9:43:34 PM -- Instance has 0.6 for. 11/13/2012 9:43:34 PM -- Instance has 19.8 for. 11/13/2012 9:43:34 PM -- Instance has 0.6 for. 11/13/2012 9:43:34 PM -- Instance has 0.6 for. 11/13/2012 9:43:34 PM -- Instance has 19.8 for. 11/13/2012 9:43:34 PM -- Instance has 0.6 for. 11/13/2012 9:43:34 PM -- Instance has 0.6 for. 11/13/2012 9:43:34 PM -- Instance has 19.8 for. 11/13/2012 9:43:34 PM -- Instance has 0.6 for. 11/13/2012 9:43:34 PM -- Instance has 0.6 for. 11/13/2012 9:43:34 PM -- Instance has 19.8 for. 11/13/2012 9:43:34 PM -- Instance has 0.6 for. 11/13/2012 9:43:34 PM -- Instance has 0.6 for. 11/13/2012 9:43:34 PM -- Instance has 19.8 for. 11/13/2012 9:43:34 PM -- Instance has 0.6 for. 11/13/2012 9:43:34 PM -- Instance has 0.6 for. 20

21 11/13/2012 9:43:34 PM -- Instance has 19.8 for. 11/13/2012 9:43:34 PM -- Instance has 0.6 for. 11/13/2012 9:43:34 PM -- Instance has 0.6 for. 11/13/2012 9:43:34 PM -- Instance has 19.8 for. 11/13/2012 9:43:34 PM -- Instance has 0.6 for. 11/13/2012 9:43:34 PM -- Instance has 0.6 for. 11/13/2012 9:43:34 PM -- Instance has 19.8 for. 11/13/2012 9:43:34 PM -- Instance has 0.6 for. 11/13/2012 9:43:34 PM -- Instance has 0.6 for. 11/13/2012 9:43:34 PM -- Instance has 19.8 for. 11/13/2012 9:43:34 PM -- Instance has 0.6 for. 11/13/2012 9:43:34 PM -- Instance has 0.6 for. 11/13/2012 9:43:34 PM -- Test has 0 Maximum Page Fault Stalls/sec. 11/13/2012 9:43:34 PM -- The test has 0 Page Fault Stalls/sec samples higher than 0. 11/13/2012 9:43:34 PM -- C:\Program Files\Exchange Jetstress\24HR_Test\Stress_2012_11_12_21_37_33.xml has 5750 samples queried. Stress Test Result Report Test Summary Overall Test Result Machine Name Test Description Pass HOST3 Test Start Time 11/12/2012 9:37:08 PM Test End Time 11/13/2012 9:42:45 PM Collection Start Time 11/12/2012 9:39:35 PM Collection End Time 11/13/2012 9:39:32 PM Jetstress Version ESE Version Operating System Windows Server 2008 R2 Enterprise Service Pack 1 ( ) Performance Log C:\Program Files\Exchange Jetstress\24HR_Test\Stress_2012_11_12_21_37_34.blg Sizing and Throughput Achieved Transactional per Second Target Transactional per Second 1400 Initial Size (bytes) Final Size (bytes) Files (Count) 12 Jetstress System Parameters Thread Count Minimum Cache 8 (per database) MB Maximum Cache MB Insert Operations 40% Delete Operations 20% Replace Operations 5% Read Operations 35% Lazy Commits 70% Run Background Maintenance True Number of Copies per 3 Configuration Instance Log path: C:\DBLG1 : C:\DBLG1\Jetstress edb Instance Log path: C:\DBLG2 : C:\DBLG2\Jetstress edb Instance Log path: C:\DBLG3 21

22 : C:\DBLG3\Jetstress edb Instance Log path: C:\DBLG4 : C:\DBLG4\Jetstress edb Instance Log path: C:\DBLG5 : C:\DBLG5\Jetstress edb Instance Log path: C:\DBLG6 : C:\DBLG6\Jetstress edb Instance Log path: C:\DBLG7 : C:\DBLG7\Jetstress edb Instance Log path: C:\DBLG8 : C:\DBLG8\Jetstress edb Instance Log path: C:\DBLG9 : C:\DBLG9\Jetstress edb Instance Log path: C:\DBLG10 : C:\DBLG10\Jetstress edb Instance Log path: C:\DBLG11 : C:\DBLG11\Jetstress edb Instance Log path: C:\DBLG12 : C:\DBLG12\Jetstress edb Transactional Performance MSExchange ==> Instances /sec /sec /sec /sec Instance Instance Instance Instance Instance Instance Instance Instance Instance Instance Instance Instance Background Maintenance Performance MSExchange ==> Instances Maintenance IO /sec Maintenance IO Instance Instance Instance Instance Instance Instance Instance Instance

23 Instance Instance Instance Instance Log Replication Performance MSExchange ==> Instances /sec Instance Instance Instance Instance Instance Instance Instance Instance Instance Instance Instance Instance Total Performance MSExchange ==> Instances /sec /sec /sec /sec Instance Instance Instance Instance Instance Instance Instance Instance Instance Instance Instance Instance Host System Performance Counter Minimum Maximum % Processor Time Available M Free System Page Table Entries Transition Pages RePurposed/sec Pool Nonpaged Pool Paged Page Fault Stalls/sec Test Log11/12/2012 9:37:07 PM -- Jetstress testing begins... 11/12/2012 9:37:08 PM -- Preparing for testing... 11/12/2012 9:37:20 PM -- Attaching databases... 11/12/2012 9:37:20 PM -- Preparations for testing are complete. 11/12/2012 9:37:21 PM -- Starting transaction dispatch.. 11/12/2012 9:37:21 PM -- cache settings: (minimum: MB, maximum: 3.0 GB) 11/12/2012 9:37:21 PM -- flush thresholds: (start: 30.7 MB, stop: 61.4 MB) 11/12/2012 9:37:34 PM -- read latency thresholds: (average: 20 msec/read, maximum: 200 msec/read). 11/12/2012 9:37:34 PM -- Log write latency thresholds: (average: 10 msec/write, maximum: 200 msec/write). 23

24 11/12/2012 9:37:43 PM -- Operation mix: Sessions 8, Inserts 40%, Deletes 20%, Replaces 5%, 35%, Lazy Commits 70%. 11/12/2012 9:37:43 PM -- Performance logging started (interval: ms). 11/12/2012 9:37:43 PM -- Attaining prerequisites: 11/12/2012 9:39:35 PM -- \MSExchange (JetstressWin)\ Cache Size, Last: (lower bound: , upper bound: none) 11/13/2012 9:39:35 PM -- Performance logging has ended. 11/13/2012 9:42:42 PM -- JetInterop batch transaction stats: , , , , , , , , , , and /13/2012 9:42:43 PM -- Dispatching transactions ends. 11/13/2012 9:42:43 PM -- Shutting down databases... 11/13/2012 9:42:45 PM -- Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete) and Instance (complete) 11/13/2012 9:42:45 PM -- C:\Program Files\Exchange Jetstress\24HR_Test\Stress_2012_11_12_21_37_34.blg has 5758 samples. 11/13/2012 9:42:45 PM -- Creating test report... 11/13/2012 9:43:37 PM -- Instance has 19.8 for. 11/13/2012 9:43:37 PM -- Instance has 0.6 for. 11/13/2012 9:43:37 PM -- Instance has 0.6 for. 11/13/2012 9:43:37 PM -- Instance has 19.8 for. 11/13/2012 9:43:37 PM -- Instance has 0.6 for. 11/13/2012 9:43:37 PM -- Instance has 0.6 for. 11/13/2012 9:43:37 PM -- Instance has 19.8 for. 11/13/2012 9:43:37 PM -- Instance has 0.6 for. 11/13/2012 9:43:37 PM -- Instance has 0.6 for. 11/13/2012 9:43:37 PM -- Instance has 19.8 for. 11/13/2012 9:43:37 PM -- Instance has 0.6 for. 11/13/2012 9:43:37 PM -- Instance has 0.6 for. 11/13/2012 9:43:37 PM -- Instance has 19.8 for. 11/13/2012 9:43:37 PM -- Instance has 0.6 for. 11/13/2012 9:43:37 PM -- Instance has 0.6 for. 11/13/2012 9:43:37 PM -- Instance has 19.8 for. 11/13/2012 9:43:37 PM -- Instance has 0.6 for. 11/13/2012 9:43:37 PM -- Instance has 0.6 for. 11/13/2012 9:43:37 PM -- Instance has 19.8 for. 11/13/2012 9:43:37 PM -- Instance has 0.6 for. 11/13/2012 9:43:37 PM -- Instance has 0.6 for. 11/13/2012 9:43:37 PM -- Instance has 19.8 for. 11/13/2012 9:43:37 PM -- Instance has 0.6 for. 11/13/2012 9:43:37 PM -- Instance has 0.6 for. 11/13/2012 9:43:37 PM -- Instance has 19.8 for. 11/13/2012 9:43:37 PM -- Instance has 0.6 for. 11/13/2012 9:43:37 PM -- Instance has 0.6 for. 11/13/2012 9:43:37 PM -- Instance has 19.8 for. 11/13/2012 9:43:37 PM -- Instance has 0.6 for. 11/13/2012 9:43:37 PM -- Instance has 0.6 for. 11/13/2012 9:43:37 PM -- Instance has 19.8 for. 11/13/2012 9:43:37 PM -- Instance has 0.6 for. 11/13/2012 9:43:37 PM -- Instance has 0.6 for. 11/13/2012 9:43:37 PM -- Instance has 19.8 for. 11/13/2012 9:43:37 PM -- Instance has 0.6 for. 11/13/2012 9:43:37 PM -- Instance has 0.6 for. 11/13/2012 9:43:37 PM -- Test has 0 Maximum Page Fault Stalls/sec. 11/13/2012 9:43:37 PM -- The test has 0 Page Fault Stalls/sec samples higher than 0. 11/13/2012 9:43:37 PM -- C:\Program Files\Exchange Jetstress\24HR_Test\Stress_2012_11_12_21_37_34.xml has 5750 samples queried. Stress Test Result Report Test Summary Overall Test Result Machine Name Test Description Pass HOST4 24