Hitachi Unified Storage 110 Dynamically Provisioned 27,200 Mailbox Exchange 2010 Mailbox Resiliency Storage Solution

1 Hitachi Unified Storage 110 Dynamically Provisioned 27,200 Mailbox Exchange 2010 Mailbox Resiliency Storage Solution Tested with: ESRP Storage Version 3.0 Test Date: July August 2012 Month Year

Notices and Disclaimer Copyright 2012 Hitachi Data Systems Corporation. All rights reserved. The performance data contained herein was obtained in a controlled isolated environment. Actual results that may be obtained in other operating environments may vary significantly. While Hitachi Data Systems Corporation has reviewed each item for accuracy in a specific situation, there is no guarantee that the same results can be obtained elsewhere. All designs, specifications, statements, information and recommendations (collectively, "designs") in this manual are presented "AS IS," with all faults. Hitachi Data Systems Corporation and its suppliers disclaim all warranties, including without limitation, the warranty of merchantability, fitness for a particular purpose and non-infringement or arising from a course of dealing, usage or trade practice. In no event shall Hitachi Data Systems Corporation or its suppliers be liable for any indirect, special, consequential or incidental damages, including without limitation, lost profit or loss or damage to data arising out of the use or inability to use the designs, even if Hitachi Data Systems Corporation or its suppliers have been advised of the possibility of such damages. This document has been reviewed for accuracy as of the date of initial publication. Hitachi Data Systems Corporation may make improvements and/or changes in product and/or programs at any time without notice. 1

Table of Contents Overview... 3 Disclaimer... 3 Features... 4 Solution Description... 5 Targeted Customer Profile... 10 Test Deployment... 11 Replication Configuration... 13 Best Practices... 15 Core Storage... 15 Storage-based Replication... 16 Backup Strategy... 16 Test Results Summary... 17 Reliability... 17 Storage Performance Results... 17 Backup and Recovery Performance... 19 Conclusion... 20 Appendix Test Reports... 21 Performance Test Result: CB10... 21 Performance Test Checksums Result: CB10... 30 Stress Test Result: CB10... 34 Stress Test Checksums Result: CB10... 43 Backup Test Result: CB10... 47 Soft Recovery Test Result: CB10... 51 Soft Recovery Test Performance Result: CB10... 58 2

Hitachi Unified Storage 110 Dynamically Provisioned 27,200 Mailbox Exchange 2010 Mailbox Resiliency Storage Solutions Tested with: ESRP Storage Version 3.0 Test Date: July-August 2012 Overview This document provides information on a Microsoft Exchange Server 2010 mailbox resiliency storage solution that uses Hitachi Unified Storage 110 storage systems with Hitachi Dynamic Provisioning. This solution is based on the Microsoft Exchange Solution Reviewed Program (ESRP) Storage program. For more information about the contents of this document or Hitachi Data Systemsbest practice recommendations for Microsoft Exchange Server 2010 storage design, see Hitachi Data Systems Microsoft Exchange Solutions Web page. The ESRP Storage program was developed by Microsoft Corporation to provide a common storage testing framework for vendors to provide information on its storage solutions for Microsoft Exchange Server software. For more information about the Microsoft ESRP Storage program, see TechNet s overview of the program. Disclaimer This document has been produced 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. The information contained in this document represents the current view of Hitachi Data Systems on the issues discussed as of the date of publication. Due to changing market conditions, it should not be interpreted to be a commitment on the part of Hitachi Data Systems, and Hitachi Data Systems cannot guarantee the accuracy of any information presented after the date of publication. 3

Features The purpose of this testing was to measure the ESRP 3.0 results on a Microsoft Exchange 2010 environment with 27,200 users and four servers. This testing used Hitachi Unified Storage 110 with Hitachi Dynamic Provisioning in a two-pool RAID-10 (4D+4D) (one for databases and one for logs) resiliency configuration. These results help answer questions about the kind of performance capabilities to expect with a large-scale Exchange deployment on Hitachi Unified Storage 110. Testing used four Hitachi Compute Blade 2000 server blades in a single chassis, each with the following: 64 GB of RAM Two quad-core Intel Xeon X5690 3.46 GHz CPUs Two dual-port 8 Gb/sec Fibre Channel PCIe HBA (Emulex LPe1205-HI, using two port per HBA) located in the chassis expansion tray Microsoft Windows Server 2008 R2 Enterprise This solution includes Exchange 2010 Mailbox Resiliency by using the database availability group (DAG) feature. This tested configuration uses four DAGs, each containing twelve database copies and two servers. The test configuration was capable of supporting 27,200 users with a 0.18 IOPS per user profile and user mailbox size of 3 GB. A Hitachi Unified Storage 110 with the following was used for these tests: 120 2TB 7.2K RPM SAS disks 8 GB of cache 8 8Gb/sec paths used Hitachi Unified Storage 110 is a medium-sized, highly reliable midrange storage system that can scale to 120 disks while maintaining 99.999% availability. It is highly suitable for a variety of applications and host platforms and is modular in scale. With the option of in-system and cross-system replication functionality, the Hitachi Unified Storage 110 is fully capable of being used as the core underlying storage platform for highperformance Exchange Server 2010 architectures. 4

Solution Description Deploying Microsoft Exchange Server 2010 requires careful consideration of all aspects of the solution architecture. Host servers need to be configured so that they are robust enough to handle the required Exchange load. The storage solution must be designed to provide the necessary performance while also being reliable and easy to administer. Of course, an effective backup and recovery plan should be incorporated into the solution as well. The aim of this solution report is to provide a tested configuration that uses Hitachi Unified Storage 110 to meet the needs of a large Exchange Server deployment. This solution uses Hitachi Dynamic Provisioning, which is enabled on Hitachi Unified Storage 110 via a license key. In the most basic sense, Hitachi Dynamic Provisioning is similar to the use of a host-based logical volume manager (LVM), but with several additional features available within Hitachi Unified Storage 110 and without the need to install software on the host or incur host processing overhead. Hitachi Dynamic Provisioning is a superior solution by providing for one or more pools of wide striping across many RAID groups within Hitachi Unified Storage 110. One or more dynamic provisioning virtual volumes (DP-VOLs) of a user-specified logical size (with no initial physical space allocated) are created and associated with a single pool. Primarily, Hitachi Dynamic Provisioning is deployed to avoid the routine issue of hot spots that occur on logical units (LUs) from individual RAID groups when the host workload exceeds the IOPS or throughput capacity of that RAID group. By using many RAID groups as members of a striped Hitachi Dynamic Provisioning pool underneath the virtual or logical volumes seen by the hosts, a host workload is distributed across many RAID groups, which provides a smoothing effect that dramatically reduces hot spots and results in fewer mailbox moves for the Exchange administrator. Hitachi Dynamic Provisioning also carries the side benefit of thin provisioning, where physical space is only assigned from the pool to the DP-VOL as needed using 1 GB chunks per RAID Group, up to the logical volume size specified for each DP-VOL. Space from a 1 GB chunk is then allocated as needed as 32 MB pool pages to that DP-VOL s logical block address range. A pool can also be dynamically expanded by adding more RAID groups without disruption or requiring downtime. Upon expansion, a pool can be rebalanced easily so that the data and workload are wide striped evenly across the current and newly added RAID groups thatmake up the pool. High availability is also a part of this solution with the use of database availability groups (DAG), which is the base component of the high availability and site resilience framework built into Microsoft Exchange Server 2010. A DAG is a group of up to 16 mailbox servers that host a set of databases and logs and use continuous replication to provide automatic database-level recovery from failures that affect individual servers or databases. Any server in a DAG can host a copy of a mailbox database from any other server in the DAG. When a server is added to a DAG, it monitors and works with the other servers in the DAG to provide automatic recovery delivering a robust, highly available Exchange solution without the administrative complexities of traditional failover clustering. For more information about the DAG feature in Exchange Server 2010, see http://technet.microsoft.com/en-us/library/dd979799.aspx This solution includes two copies of each Exchange database using four DAGs, with each DAG configured with two servers (one simulated) that host active mailboxes in twelve databases. To target the 27,200-user resiliency solution, a Hitachi Unified Storage 110 storage system was configured with 120 disks (maximum 120). Four servers (one per DAG) were used, with each server configured with 6,800 mailboxes. There were 12 active databases and the simulated database copies for the tests. 5

Each DAG contained two copies of the databases hosted by that DAG; A local, active copy on a server connected to the primary Hitachi Unified Storage 110 A passive copy (simulated) on another server connected to a second Hitachi Unified Storage 110 (simulated). This recommended configuration can support both high-availability and disaster-recovery scenarios when the active and passive database copies are allocated among both DAG members and dispersed across both storage systems. Each simulated DAG server node in this solution maintains a mirrored configuration and possesses adequate capacity and performance capabilities to support the second set of replicated databases. Figure 1 illustrates the two systems that make up the simulated DAG configuration. For more information, see the Hitachi Data Systems Storage Systems web page. Figure 1 This solution enables organizations to consolidate Exchange Server 2010 DAG deployments on two Hitachi Unified Storage 110 storage systems. Using identical hardware and software configurations guarantees that an active database and its replicated copy do not share storage paths, disk spindles or storage controllers, making it a very reliable, high-performing, highly available Exchange Server 2010 solution that is cost effective and easy to manage. This helps ensure that performance and service levels related to storage are maintained regardless of which server is hosting the active database. If further protection is needed in a production 6

environment, additional Exchange Server 2010 mailbox servers can be easily added to support these failover scenarios. Table 1 illustrates how the disks in Hitachi Unified Storage 110 were organized into RAID groups for use by databases or logs. Each set of colored disks represents a RAID-10 (4D+4D) group. There were 120 2TB 7.2K RPM SAS disks used in these tests configured as 13 RAID groups for the Exchange databases and logs. Table 1. Hitachi Unified Storage 110 RAID Groups by Tray Layout HUS110, 2TB 7.2K SAS, R-10(4+4) HDP Pool Disk Layout Unit 4 RG37 RG36 RG35 Unit 3 RG40 RG39 RG38 Unit 2 RG43 RG42 RG41 Unit 1 RG46 RG45 RG44 Unit 0 RG49 RG48 RG47 Slot # 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 DB Pool Log Pool Disk trays 0 through 4 each held 24 7.2K RPM SAS disks. Two dynamic provisioning pools were created, one for the databases and the other for the logs. The database pool was created from 13 RAID-10 (4D+4D) RAID groups and the log pool was created from 2 RAID-10 (4D+4D) groups. From the database pool, 48 DP-VOLs (each specified to have a 1,900 GB size limit) were created for 48 databases (twelve per server). From the log pool, 48 DP-VOLs (each specified to have a size limit of 190 GB) were created for 48 logs (twelve per server). Table 2 outlines the port layout for the primary storage system and servers. An identical configuration would be deployed on the replicated storage and servers for this solution. 7

Table 2. Hitachi Unified Storage 110 Ports to Server Layout Server Mapping Configuration Server Primary path Secondary path CB10 0A 1A 0C 1C CB11 1A 0A 1C 0C CB12 0B 1B 0D 1D CB13 1B 0B 1D 0D Table 3 outlines the port layout with the database DP-VOL assignments for the primary storage and servers. An identical configuration would be deployed on the replicated storage and servers for this solution. Table 3. Hitachi Unified Storage 110 Ports to DP-VOL Layout Port DB DP-VOLs 0A s 1-6 0-5 1A s 13-17 12-17 0B s 25-30 24-29 1B s 37-42 36-41 0C s 7-12 6-11 1C s 18-24 18-23 0D s 31-36 30-35 1D s 43-48 42-47 Table 4 outlines the port layout with the log DP-VOL assignments for the primary storage system and servers. An identical configuration would be deployed on the replicated storage system and servers for this solution. 8

Table 4. Hitachi Unified Storage 110Ports to Log DP-VOL Layout Port Log Log DP-VOLs 0A log 49-54 48-53 1A log 61-66 60-65 0B log 73-78 72-77 1B log 85-90 84-89 0C log 55-60 54-59 1C log 67-72 66-71 0D log 79-84 78-83 1D log 91-96 90-95 Table 5 provides the detailed specifications for the storage configuration which uses RAID-10 (4D+4D) RAID groups and 2TB 7.2KRPM disks. Dynamic Provisioning Pool 1 is dedicated for the databases and Dynamic Provisioning Pool 0 is dedicated for the logs. Table 5. Hitachi Unified Storage 110 Configuration Details Host Pool Port DP-VOL Size (GB) RAID Level Description CB10 1 0A/1A 0-5 1900 RAID-10 s 1-6 1 0C/1C 6-11 1900 RAID-10 s 7-12 CB11 1 1A/0A 12-17 1900 RAID-10 s 13-17 1 1C/0C 18-23 1900 RAID-10 s 18-24 CB12 1 0B/1B 24-29 1900 RAID-10 s 25-30 1 0D/1D 30-35 1900 RAID-10 s 31-36 CB13 1 1B/0B 36-41 1900 RAID-10 s 37-42 1 1D/0D 42-47 1900 RAID-10 s 43-48 CB10 0 0A/1A 48-53 190 RAID-10 log 49-54 0 0C/1C 54-59 190 RAID-10 log 55-60 CB11 0 1A/0A 60-65 190 RAID-10 log 61-66 0 1C/0C 66-71 190 RAID-10 log 67-72 CB12 0 0B/1B 72-77 190 RAID-10 log 73-78 0 0D/1D 78-83 190 RAID-10 log 79-84 CB13 0 1B/0B 84-89 190 RAID-10 log 85-90 0 1D/0D 90-95 190 RAID-10 log 91-96 9

The ESRP Storage program focuses on storage solution testing to address performance and reliability issues with storage design. However, storage is not the only factor to take into consideration when designing a scale-up Exchange solution. These factors also affect server scalability: Server processor utilization Server physical and virtual memory limitations Resource requirements for other applications Directory and network service latencies Network infrastructure limitations Replication and recovery requirements Client usage profiles These factors are all beyond the scope of the ESRP Storage program. Therefore, the number of mailboxes hosted per server as part of the tested configuration might not necessarily be viable for some customer deployments. For more information about identifying and addressing performance bottlenecks in an Exchange system, see Microsoft's Troubleshooting Microsoft Exchange Server Performance. Targeted Customer Profile This solution is designed for medium to large organizations that plan to consolidate their Exchange Server 2010 storage on high-performance, high-reliability storage systems. This configuration is designed to support 27,200 Exchange users with the following specifications: Eight Exchange servers (four tested, four simulated for the database copies) Four database availability groups (DAG) each with two servers (one simulated) and two copies per database Two Hitachi Unified Storage 110 (one tested) 0.15 IOPS per user (0.18 tested for 20 percent growth) 3 GB mailbox size Mailbox resiliency provides high-availability and used as primary data protection mechanism. Hitachi Unified Storage RAID protection against physical failure or loss. 24x7 background database maintenance enabled. 10

Test Deployment The following tables summarize the testing environment. Table 6. Simulated Exchange Configuration Number of Exchange mailboxes simulated 27,200 Number of database availability groups (DAGs) 4 Number of servers per DAG 2 Number of active mailboxes per server 6,800 Number of databases per host 12 Number of copies per database 2 Number of mailboxes per database 566 Simulated profile: s per second per mailbox (IOPS, include 20% headroom) 0.18 LU size Log LU siz Total database size for performance testing 1900 GB 190 GB 81,600 GB % storage capacity used by Exchange database** 88.7% **Storage performance characteristics change based on the percentage utilization of the individual disks. Tests that use a small percentage of the storage (~25%) might exhibit reduced throughput if the storage capacity utilization is significantly increased beyond what was tested for this paper. Table 7. Storage Hardware Storage connectivity (Fibre Channel, SAS, SATA, iscsi) Storage model and OS/firmware revision Storage cache Fibre Channel 1 Hitachi Unified Storage 110 Firmware: 0920/A-W WHQL listing: Hitachi Unified Storage 110 8 GB Number of storage controllers 2 Number of storage ports 8 Maximum bandwidth of storage connectivity to host 64 Gb/sec (8 8 Gb/sec ports) Switch type/model/firmware revision HBA model and firmware Number of HBAs per host Brocade 5300, Fabric OS v7.0.1b Emulex LPe1205-HI FW : 1.11X14 2 dual-ported HBA per host, 2 8 Gb/sec port used per HBA 11

Host server type Hitachi Compute Blade E55A2 2 3.46GHz Intel Xeon Processors, 32 GB memory Total number of disks tested in solution 120 Maximum number of spindles that can be hosted in the storage 120 Table 8. Storage Software HBA driver Storport Miniport 7.2.20.006 HBA QueueTarget setting 0 HBA QueueDepth setting 32 Multipathing Host OS Hitachi Dynamic Link Manager v7.2.1-00 Microsoft Windows Server 2008 R2 Enterprise ESE.dll file version 14.01.0225.017 Replication solution name/version N/A Table 9. Storage Disk Configuration (Mailbox Store Disks) Disk type, speed and firmware revision SAS Disk 2TB 7.2K 5C0C Raw capacity per disk (GB) Number of physical disks in test 2 TB 104 (dynamic provisioning pool) Total raw storage capacity (GB) 208,000 Disk slice size (GB) N /A Number of slices per LU or number of disks per LU RAID level Total formatted capacity N/A RAID-10 (4D+4D) at storage level 92,040 GB Storage capacity utilization 44.3% capacity utilization 43.8% Table 10. Storage Disk Configuration (Transaction Log Disks) Disk type, speed and firmware revision SAS Disk 2TB 7.2K 5C0C Raw capacity per disk (GB) Number of spindles in test 2 TB 8 (dynamic provisioning pool) Total raw storage capacity (GB) 16,000 12

Disk slice size (GB) Number of slices per LU or number of disks per LU RAID level Total formatted capacity N/A N/A RAID-10 (4D+4D) at storage level 7,080 GB Replication Configuration Table 11. Replication Configuration Replication mechanism Exchange Server 2010 Availability Group (DAG) Number of links 2 Simulated link distance Link type Link bandwidth N/A IP GigE (1Gb/sec) Table 12. Replicated Storage Hardware Storage connectivity (Fibre Channel, SAS, SATA, iscsi) Storage model and OS/firmware revision Storage cache Fibre Channel 1 Hitachi Unified Storage 110 Firmware: 0920/A-W WHQL listing: Hitachi Unified Storage 110 8 GB Number of storage controllers 2 Number of storage ports 8 Maximum bandwidth of storage connectivity to host 64 Gb/sec (8 8 Gb/sec ports) Switch type/model/firmware revision HBA model and firmware Number of HBAs per host Host server type Brocade 5300, Fabric OS v7.0.1b Emulex LPe1205-HI FW : 1.11X14 2 dual-ported HBA per host, 2 8Gb/sec port used per HBA Hitachi Compute Blade E55A2 2 3.46GHz Intel Xeon Processors, 32 GB memory Total number of disks tested in solution 120 Maximum number of spindles that can be hosted in the storage 120 13

Table 13. Replicated Storage Software HBA driver Storport Miniport 7.2.20.006 HBA QueueTarget setting 0 HBA QueueDepth setting 32 Multipathing Host OS Hitachi Dynamic Link Manager v7.2.1-00 Microsoft Windows Server 2008 R2 Enterprise ESE.dll file version 14.01.0225.017 Replication solution name/version N/A Table 14. Replicated Storage Disk Configuration (MailboxStore Disks) Disk type, speed and firmware revision SAS Disk 2TB 7.2K 5C0C Raw capacity per disk (GB) Number of physical disks in test 2 TB 104 (dynamic provisioning pool) total raw storage capacity (GB) 208,000 Disk slice size (GB) N /A Number of slices per LU or number of disks per LU Raid level Total formatted capacity N/A RAID-10 (4D+4D) at storage level 92,040 GB Storage capacity utilization 44.3% capacity utilization 43.8% Table 15. Replicated Storage Disk Configuration (Transactional Log Disks) Disk type, speed and firmware revision SAS Disk 2TB 7.2K 5C0C Raw capacity per disk (GB) Number of spindles in test 2 TB 8 (dynamic provisioning pool) Total raw storage capacity (GB) 16,000 Disk slice size (GB) Number of slices per LU or number of disks per LU Raid level Total formatted capacity N/A N/A RAID-10 (4D+4D) at storage level 7,080 GB 14

Best Practices Microsoft Exchange Server 2010 is a disk-intensive application. It presents two distinct workload patterns to the storage, with 32 KB random read/write operations to the databases, and sequential write operations of varying size (between 512 bytes up to the log buffer size) to the transaction logs. For this reason, designing an optimal storage configuration can prove challenging in practice. Based on the testing run using the ESRP framework, Hitachi Data Systems recommends these best practices to improve the performance of Hitachi Unified Storage 110 running Exchange 2010. For more information about Exchange 2010 best practices for storage design, see the Microsoft TechNet article Mailbox Server Storage Design. Core Storage 1. When formatting a newly partitioned LU, Hitachi Data Systems recommends setting the ALU to 64K for the database files and 4K for the log files. 2. Disk alignment is no longer required when using Microsoft Windows Server 2008. 3. Keep the Exchange workload isolated from other applications. Mixing another intensive application whose workload differs from Exchange can cause the performance for both applications to degrade. 4. Use Hitachi Dynamic Link Manager multipathing software to provide fault tolerance and high availability for host connectivity. 5. Use Hitachi Dynamic Provisioning to simplify storage management of the Exchange database and log volumes. 6. Due to the difference in patterns, isolate the Exchange database from the log groups. Create a dedicated Hitachi Dynamic Provisioning pool for the databases and a separate pool for the logs. 7. Hitachi Data Systems recommends RAID-5 or RAID-1+0 groups for both the database pools and for the log pool. Use of RAID-10 allows more writes at a lower response time under heavier loads. RAID-10 also supports a shorter RAID group rebuild time on failure of a disk. 8. The log LUs should be at least 10 percent of the size of the database LUs. 9. Hitachi Data Systems does not recommend using LU concatenation. 10. Hitachi Data Systems recommends implementing Mailbox Resiliency using the Exchange Server 2010 Availability Group feature. 11. Ensure that each DAG maintains at least two database copies to provide high availability. 12. Isolate active databases and their replicated copies in separate dynamic provisioning pools or ensure that they are located on a separate Hitachi Unified Storage 110. 13. Use fewer, larger LUs for Exchange 2010 databases (up to 2TB) with Background Maintenance (24x7) enabled. 14. Size storage solutions for Exchange based primarily on performance criteria. The number of disks, RAID level and percent utilization of each disk directly affect the level of achievable performance. Factor in capacity requirements only after performance is addressed. 15

15. Disk size is unrelated to performance with regards to IOPS or throughput rates. Disk size is related to the usable capacity of all of the LUs from a RAID group, which is a choice users make. 16. The number of spindles, coupled with the RAID level, determines the physical IOPS capacity of the RAID group and all of its LUs. If the disk has too few spindles, the response times grow to large values very quickly. Storage-based Replication N/A Backup Strategy N/A 16

Test Results Summary This section provides a high-level summary of the test data from ESRP and the link to the detailed HTML reports that are generated by ESRP testing framework. Reliability A number of tests in the framework check reliability spanning a 24-hour window. The goal is to verify the storage can handle high load for a long period of time. Following these stress tests, both log and database files are analyzed for integrity to ensure that no database or log corruption occurs. No errors were reported in the event log file for the storage reliability testing. No errors were reported for the database and log checksum process. If done, no errors were reported during the backup to disk test process. No errors were reported for the database checksum on the remote storage database. Storage Performance Results Primary storage performance testing exercises the storage with maximum sustainable Exchange type of for two hours. The test shows how long it takes for the storage to respond to an under load. The following data is the sum of all of the logical disk s and average of all the logical disks latency in the two-hour test duration. Individual Server Metrics These individual server metrics show the sum of the s across the storage groups and the average latency across all storage groups on a per-server basis. Table 16. Individual Server Metrics for Exchange Server (CB10) Disk Transfers Per Second 1383 Disk Reads Per Second 747 Disk Writes Per Second 637 Disk Read Latency (ms) 14.4 Disk Write Latency (ms) 2.2 Transaction Log Log Disk Writes Per Second 539 Log Disk Write Latency (ms) 0.7 17

Table 17. Individual Server Metrics for Exchange Server (CB11) Disk Transfers Per Second 1379 Disk Reads Per Second 744 Disk Writes Per Second 635 Disk Read Latency (ms) 14.4 Disk Write Latency (ms) 2.2 Transaction Log Log Disk Writes Per Second 536 Log Disk Write Latency (ms) 0.7 Table 18. Individual Server Metrics for Exchange Server (CB12) Disk Transfers Per Second 1384 Disk Reads Per Second 747 Disk Writes Per Second 637 Disk Read Latency (ms) 14.4 Disk Write Latency (ms) 2.2 Transaction Log Log Disk Writes Per Second 539 Log Disk Write Latency (ms) 0.7 Table 19. Individual Server Metrics for Exchange Server (CB13) Disk Transfers Per Second 1389 Disk Reads Per Second 749 Disk Writes Per Second 639 Disk Read Latency (ms) 14.3 Disk Write Latency (ms) 2.1 Transaction Log Log Disk Writes Per Second 540 Log Disk Write Latency (ms) 0.7 18

Aggregate Performance Across All Servers Metric The aggregate performance across all server metrics shows the sum of s across all servers in the solution and the average latency across all servers in the solution. Table 20. Aggregate Performance for Exchange Server 2010 Disk Transfers Per Second 5534.96 Disk Reads Per Second 2986.59 Disk Writes Per Second 2548.37 Disk Read Latency (ms) 14.37 Disk Write Latency (ms) 2.16 Transaction Log Log Disk Writes Per Second 2152.80 Log Disk Write Latency (ms) 0.68 Backup and Recovery Performance This section has two tests: The first measures the sequential read rate of the database files and the second measures recovery/replay performance (playing transaction logs in to the database). Read-only Performance This test measures the maximum rate at which databases can be backed up via VSS. The following tables show the average rate for a single database file. Table 21. Read-only Performance MB Read Per Second Per 57.40 MB Read Per Second Total Per Server 688.77 Transaction Log Recovery/Replay Performance This test measures the maximum rate at which the log files can be played against the databases. The following table shows the average rate for 500 log files played in a single storage group. Each log file is 1MB in size. Table 22. Transaction Log Recovery/Replay Performance Time to Play One Log File (sec) 2.89226 19

Conclusion This document details a tested and robust Exchange Server 2010 Resiliency solution capable of supporting 27,200 users with a 0.18 IOPS per user profile and user mailbox size of 3 GB using four DAG s each configured with 2 server nodes (one simulated). A Hitachi Unified Storage 110 storage system, with 8 GB of cache and four 8 Gb/sec Fibre Channel host paths, using Hitachi Dynamic Provisioning (with two pools) and 120 2TB 7K RPM SAS disks in a RAID-10 (4D+4D) configuration was used for these tests. Testing confirmed that Hitachi Unified Storage 110 is more than capable of delivering the IOPS and capacity requirements needed to support the active and replicated databases for 27,200 Exchange mailboxes configured with the specified user profile, while maintaining additional headroom to support peak throughput. The solution outlined in this document does not include data protection components, such as VSS snapshot or clone backups, and relies on the built-in Mailbox Resiliency features of Exchange Server 2010 coupled with Hitachi Unified Storage RAID technology to provide high-availability and protection from logical and physical failures. Adding additional protection requirements may affect performance and capacity requirements of the underlying storage configuration, and as such need to be factored into the storage design accordingly. For more information to about planning Exchange Server 2010 storage architectures for the Hitachi Unified Storage family, see http://www.hds.com/ This document is developed by Hitachi Data Systems and reviewed by the Microsoft Exchange product team. The test results and data presented in this document are based on the tests introduced in the ESRP test framework. Do not quote the data directly for pre-deployment verification. It is still necessary to validate the storage design for a specific customer environment. The ESRP program is not designed to be a benchmarking program; tests do not generate the maximum throughput for a given solution. Rather, it is focused on producing recommendations from vendors for Exchange application. Thus, do not use the data presented in this document for direct comparisons among the solutions 20

Appendix Test Reports This appendix contains Jetstress test results for one of the servers used in testing this storage solution. These test results are representative of the results obtained for all of the servers tested. Performance Test Result: CB10 Test Summary Overall Test Result Machine Name Pass CB10 Test Description Test Start Time Test End Time Collection Start Time Collection End Time 7/30/2012 10:19:28 PM 7/31/2012 12:23:23 AM 7/30/2012 10:23:11 PM 7/31/2012 12:22:56 AM Jetstress Version 14.01.0225.017 ESE Version 14.01.0218.012 Operating System Windows Server 2008 R2 Enterprise Service Pack 1 (6.1.7601.65536) Performance Log C:\HUS110_PE108_C1B1_SAS7K_ESRP_R10_3GB_mbox_2000 Users\Performance Test\Performance_2012_7_30_22_19_54.blg Sizing and Throughput Achieved Transactional per Second 1383.18 Target Transactional per Second 1224 Initial Size (bytes) 3587896508416 Final Size (bytes) 3592980004864 Files (Count) 12 21

Jetstress System Parameters Thread Count Minimum Cache Maximum Cache 5 (per database) 384.0 MB 3072.0 MB Insert Operations 40% Delete Operations 20% Replace Operations 5% Read Operations 35% Lazy Commits 70% Run Background Maintenance True Number of Copies per 2 22

Configuration Instance1944.1 Instance1944.2 Instance1944.3 Instance1944.4 Instance1944.5 Instance1944.6 Instance1944.7 Instance1944.8 Instance1944.9 Instance1944.10 Instance1944.11 Instance1944.12 Log path: C:\logluns\0A_P1_log1 : C:\dbluns\0A_P1_db1\Jetstress001001.edb Log path: C:\logluns\0A_P1_log2 : C:\dbluns\0A_P1_db2\Jetstress002001.edb Log path: C:\logluns\0A_P1_log3 : C:\dbluns\0A_P1_db3\Jetstress003001.edb Log path: C:\logluns\0A_P1_log4 : C:\dbluns\0A_P1_db4\Jetstress004001.edb Log path: C:\logluns\0A_P1_log5 : C:\dbluns\0A_P1_db5\Jetstress005001.edb Log path: C:\logluns\0A_P1_log6 : C:\dbluns\0A_P1_db6\Jetstress006001.edb Log path: C:\logluns\0C_P2_log7 : C:\dbluns\0C_P2_db7\Jetstress007001.edb Log path: C:\logluns\0C_P2_log8 : C:\dbluns\0C_P2_db8\Jetstress008001.edb Log path: C:\logluns\0C_P2_log9 : C:\dbluns\0C_P2_db9\Jetstress009001.edb Log path: C:\logluns\0C_P2_log10 : C:\dbluns\0C_P2_db10\Jetstress010001.edb Log path: C:\logluns\0C_P2_log11 : C:\dbluns\0C_P2_db11\Jetstress011001.edb Log path: C:\logluns\0C_P2_log12 : C:\dbluns\0C_P2_db12\Jetstress012001.edb 23

Transactional Performance MSExchange ==> Instances Reads Latency (msec) Writes Latency (msec) Reads/sec Writes/sec Reads Bytes Writes Bytes Reads Latency (msec) Writes Latency (msec) Reads/sec Writes/sec Reads Bytes Writes Bytes Instance1944.1 16.039 2.430 62.055 52.961 34336.632 35309.166 0.000 0.669 0.000 44.994 0.000 4554.234 Instance1944.2 14.161 2.427 61.890 52.786 34722.348 35291.201 0.000 0.689 0.000 44.606 0.000 4547.224 Instance1944.3 14.480 2.285 62.333 53.245 34642.300 35310.352 0.000 0.676 0.000 44.869 0.000 4537.232 Instance1944.4 14.370 2.289 62.296 53.059 34426.571 35273.899 0.000 0.698 0.000 44.429 0.000 4565.172 Instance1944.5 14.253 2.067 62.619 53.460 34601.419 35247.478 0.000 0.670 0.000 44.672 0.000 4519.856 Instance1944.6 14.286 2.107 62.411 53.165 34563.840 35259.300 0.000 0.695 0.000 45.074 0.000 4519.047 Instance1944.7 14.240 2.146 62.270 53.184 34565.377 35281.795 0.000 0.664 0.000 44.869 0.000 4558.098 Instance1944.8 14.227 2.204 61.653 52.402 34729.236 35278.841 0.000 0.682 0.000 44.590 0.000 4555.640 Instance1944.9 14.337 2.067 62.152 52.977 34615.130 35289.105 0.000 0.664 0.000 44.890 0.000 4571.140 Instance1944.10 14.108 2.110 61.948 52.821 34492.240 35304.047 0.000 0.684 0.000 44.993 0.000 4547.479 Instance1944.11 14.226 2.017 62.599 53.268 34703.693 35235.098 0.000 0.663 0.000 45.263 0.000 4507.158 Instance1944.12 14.236 2.092 62.390 53.235 34484.492 35268.348 0.000 0.679 0.000 45.259 0.000 4556.336 24

Background Maintenance Performance MSExchange ==> Instances Maintenance IO Reads/sec Maintenance IO Reads Bytes Instance1944.1 36.570 260891.160 Instance1944.2 38.253 260855.065 Instance1944.3 37.432 260898.239 Instance1944.4 37.755 260879.283 Instance1944.5 38.055 260839.319 Instance1944.6 38.094 260813.731 Instance1944.7 38.025 260874.364 Instance1944.8 37.869 260853.701 Instance1944.9 37.569 260770.036 Instance1944.10 38.251 260871.970 Instance1944.11 37.961 260862.114 Instance1944.12 37.967 260815.617 25

Log Replication Performance MSExchange ==> Instances Reads/sec Reads Bytes Instance1944.1 0.828 230576.814 Instance1944.2 0.820 231473.961 Instance1944.3 0.823 232078.662 Instance1944.4 0.820 231587.091 Instance1944.5 0.816 232055.448 Instance1944.6 0.824 231015.983 Instance1944.7 0.827 230098.577 Instance1944.8 0.821 230138.667 Instance1944.9 0.829 231015.955 Instance1944.10 0.827 230687.056 Instance1944.11 0.824 230014.264 Instance1944.12 0.834 231061.065 26

Total Performance MSExchange ==> Instances Reads Latency (msec) Writes Latency (msec) Reads/sec Writes/sec Reads Bytes Writes Bytes Reads Latency (msec) Writes Latency (msec) Reads/sec Writes/sec Reads Bytes Writes Bytes Instance1944.1 16.039 2.430 98.626 52.961 118342.981 35309.166 28.051 0.669 0.828 44.994 230576.814 4554.234 Instance1944.2 14.161 2.427 100.144 52.786 121101.544 35291.201 27.325 0.689 0.820 44.606 231473.961 4547.224 Instance1944.3 14.480 2.285 99.764 53.245 119533.652 35310.352 30.296 0.676 0.823 44.869 232078.662 4537.232 Instance1944.4 14.370 2.289 100.051 53.059 119879.663 35273.899 31.311 0.698 0.820 44.429 231587.091 4565.172 Instance1944.5 14.253 2.067 100.674 53.460 120119.085 35247.478 29.962 0.670 0.816 44.672 232055.448 4519.856 Instance1944.6 14.286 2.107 100.506 53.165 120318.382 35259.300 29.064 0.695 0.824 45.074 231015.983 4519.047 Instance1944.7 14.240 2.146 100.295 53.184 120365.282 35281.795 29.645 0.664 0.827 44.869 230098.577 4558.098 Instance1944.8 14.227 2.204 99.522 52.402 120770.678 35278.841 32.577 0.682 0.821 44.590 230138.667 4555.640 Instance1944.9 14.337 2.067 99.721 52.977 119817.542 35289.105 28.713 0.664 0.829 44.890 231015.955 4571.140 Instance1944.10 14.108 2.110 100.198 52.821 120913.047 35304.047 33.430 0.684 0.827 44.993 230687.056 4547.479 Instance1944.11 14.226 2.017 100.560 53.268 120077.013 35235.098 28.505 0.663 0.824 45.263 230014.264 4507.158 Instance1944.12 14.236 2.092 100.358 53.235 120110.017 35268.348 32.452 0.679 0.834 45.259 231061.065 4556.336 Host System Performance Counter Minimum Maximum % Processor Time 2.159 1.017 3.464 Available MBytes 58032.259 58027.000 58192.000 Free System Page Table Entries 33555793.619 33555792.000 33555795.000 Transition Pages RePurposed/sec 0.000 0.000 0.000 Pool Nonpaged Bytes 85725672.435 85676032.000 86036480.000 Pool Paged Bytes 130998777.573 130957312.000 131047424.000 Page Fault Stalls/sec 0.000 0.000 0.000 Test Log7/30/2012 10:19:28 PM -- Jetstress testing begins... 27

7/30/2012 10:19:28 PM -- Preparing for testing... 7/30/2012 10:19:41 PM -- Attaching databases... 7/30/2012 10:19:41 PM -- Preparations for testing are complete. 7/30/2012 10:19:41 PM -- Starting transaction dispatch.. 7/30/2012 10:19:41 PM -- cache settings: (minimum: 384.0 MB, maximum: 3.0 GB) 7/30/2012 10:19:41 PM -- flush thresholds: (start: 30.7 MB, stop: 61.4 MB) 7/30/2012 10:19:54 PM -- read latency thresholds: (average: 20 msec/read, maximum: 100 msec/read). 7/30/2012 10:19:54 PM -- Log write latency thresholds: (average: 10 msec/write, maximum: 100 msec/write). 7/30/2012 10:20:04 PM -- Operation mix: Sessions 5, Inserts 40%, Deletes 20%, Replaces 5%, Reads 35%, Lazy Commits 70%. 7/30/2012 10:20:04 PM -- Performance logging started (interval: 15000 ms). 7/30/2012 10:20:04 PM -- Attaining prerequisites: 7/30/2012 10:23:11 PM -- \MSExchange (JetstressWin)\ Cache Size, Last: 2909118000.0 (lower bound: 2899103000.0, upper bound: none) 7/31/2012 12:23:11 AM -- Performance logging has ended. 7/31/2012 12:23:11 AM -- JetInterop batch transaction stats: 29865, 29599, 29588, 29552, 29908, 29806, 29695, 29900, 29803, 29811, 29798 and 29997. 7/31/2012 12:23:11 AM -- Dispatching transactions ends. 7/31/2012 12:23:11 AM -- Shutting down databases... 7/31/2012 12:23:23 AM -- Instance1944.1 (complete), Instance1944.2 (complete), Instance1944.3 (complete), Instance1944.4 (complete), Instance1944.5 (complete), Instance1944.6 (complete), Instance1944.7 (complete), Instance1944.8 (complete), Instance1944.9 (complete), Instance1944.10 (complete), Instance1944.11 (complete) and Instance1944.12 (complete) 7/31/2012 12:23:23 AM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R10_3GB_mbox_2000 Users\Performance Test\Performance_2012_7_30_22_19_54.blg has 490 samples. 7/31/2012 12:23:23 AM -- Creating test report... 7/31/2012 12:23:28 AM -- Instance1944.1 has 16.0 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.1 has 0.7 for Writes Latency. 7/31/2012 12:23:28 AM -- Instance1944.1 has 0.7 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.2 has 14.2 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.2 has 0.7 for Writes Latency. 7/31/2012 12:23:28 AM -- Instance1944.2 has 0.7 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.3 has 14.5 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.3 has 0.7 for Writes Latency. 7/31/2012 12:23:28 AM -- Instance1944.3 has 0.7 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.4 has 14.4 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.4 has 0.7 for Writes Latency. 7/31/2012 12:23:28 AM -- Instance1944.4 has 0.7 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.5 has 14.3 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.5 has 0.7 for Writes Latency. 7/31/2012 12:23:28 AM -- Instance1944.5 has 0.7 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.6 has 14.3 for Reads Latency. 28

7/31/2012 12:23:28 AM -- Instance1944.6 has 0.7 for Writes Latency. 7/31/2012 12:23:28 AM -- Instance1944.6 has 0.7 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.7 has 14.2 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.7 has 0.7 for Writes Latency. 7/31/2012 12:23:28 AM -- Instance1944.7 has 0.7 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.8 has 14.2 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.8 has 0.7 for Writes Latency. 7/31/2012 12:23:28 AM -- Instance1944.8 has 0.7 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.9 has 14.3 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.9 has 0.7 for Writes Latency. 7/31/2012 12:23:28 AM -- Instance1944.9 has 0.7 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.10 has 14.1 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.10 has 0.7 for Writes Latency. 7/31/2012 12:23:28 AM -- Instance1944.10 has 0.7 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.11 has 14.2 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.11 has 0.7 for Writes Latency. 7/31/2012 12:23:28 AM -- Instance1944.11 has 0.7 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.12 has 14.2 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.12 has 0.7 for Writes Latency. 7/31/2012 12:23:28 AM -- Instance1944.12 has 0.7 for Reads Latency. 7/31/2012 12:23:28 AM -- Test has 0 Maximum Page Fault Stalls/sec. 7/31/2012 12:23:28 AM -- The test has 0 Page Fault Stalls/sec samples higher than 0. 7/31/2012 12:23:28 AM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R10_3GB_mbox_2000 Users\Performance Test\Performance_2012_7_30_22_19_54.xml has 477 samples queried. 29

Performance Test Checksums Result: CB10 Checksum Statistics - All Seen pages Bad pages Correctable pages Wrong page-number pages File length / seconds taken C:\dbluns\0A_P1_db1\Jetstress001001.edb 9137442 0 0 0 285545 MB/9878 sec C:\dbluns\0A_P1_db2\Jetstress002001.edb 9137442 0 0 0 285545 MB/9552 sec C:\dbluns\0A_P1_db3\Jetstress003001.edb 9137442 0 0 0 285545 MB/9874 sec C:\dbluns\0A_P1_db4\Jetstress004001.edb 9136674 0 0 0 285521 MB/9539 sec C:\dbluns\0A_P1_db5\Jetstress005001.edb 9136418 0 0 0 285513 MB/9875 sec C:\dbluns\0A_P1_db6\Jetstress006001.edb 9137442 0 0 0 285545 MB/9546 sec C:\dbluns\0C_P2_db7\Jetstress007001.edb 9137186 0 0 0 285537 MB/9868 sec C:\dbluns\0C_P2_db8\Jetstress008001.edb 9137698 0 0 0 285553 MB/9557 sec C:\dbluns\0C_P2_db9\Jetstress009001.edb 9138466 0 0 0 285577 MB/9856 sec C:\dbluns\0C_P2_db10\Jetstress010001.edb 9137698 0 0 0 285553 MB/9551 sec C:\dbluns\0C_P2_db11\Jetstress011001.edb 9137442 0 0 0 285545 MB/9849 sec C:\dbluns\0C_P2_db12\Jetstress012001.edb 9137698 0 0 0 285553 MB/9558 sec (Sum) 109649048 0 0 0 3426532 MB/9878 sec 30

Disk Subsystem Performance (of checksum) LogicalDisk Avg. Disk sec/read Avg. Disk sec/write Disk Reads/sec Disk Writes/sec Avg. Disk Bytes/Read C:\dbluns\0A_P1_db1 0.052 0.000 461.612 0.000 65536.000 C:\dbluns\0A_P1_db2 0.050 0.000 477.610 0.000 65536.000 C:\dbluns\0A_P1_db3 0.052 0.000 461.919 0.000 65536.000 C:\dbluns\0A_P1_db4 0.050 0.000 478.410 0.000 65536.000 C:\dbluns\0A_P1_db5 0.052 0.000 462.109 0.000 65536.000 C:\dbluns\0A_P1_db6 0.050 0.000 478.180 0.000 65536.000 C:\dbluns\0C_P2_db7 0.052 0.000 461.874 0.000 65536.000 C:\dbluns\0C_P2_db8 0.050 0.000 477.270 0.000 65536.000 C:\dbluns\0C_P2_db9 0.052 0.000 462.971 0.000 65536.000 C:\dbluns\0C_P2_db10 0.050 0.000 477.875 0.000 65536.000 C:\dbluns\0C_P2_db11 0.052 0.000 463.366 0.000 65536.000 C:\dbluns\0C_P2_db12 0.050 0.000 477.212 0.000 65536.000 Memory System Performance (of checksum) Counter Minimum Maximum % Processor Time 1.836 1.057 2.425 Available MBytes 61177.550 61157.000 61195.000 Free System Page Table Entries 33555793.085 33555793.000 33555795.000 Transition Pages RePurposed/sec 0.000 0.000 0.000 Pool Nonpaged Bytes 86487363.696 86245376.000 87080960.000 Pool Paged Bytes 131557668.571 131469312.000 132812800.000 Test Log7/30/2012 10:19:28 PM -- Jetstress testing begins... 7/30/2012 10:19:28 PM -- Preparing for testing... 7/30/2012 10:19:41 PM -- Attaching databases... 7/30/2012 10:19:41 PM -- Preparations for testing are complete. 7/30/2012 10:19:41 PM -- Starting transaction dispatch.. 7/30/2012 10:19:41 PM -- cache settings: (minimum: 384.0 MB, maximum: 3.0 GB) 31

7/30/2012 10:19:41 PM -- flush thresholds: (start: 30.7 MB, stop: 61.4 MB) 7/30/2012 10:19:54 PM -- read latency thresholds: (average: 20 msec/read, maximum: 100 msec/read). 7/30/2012 10:19:54 PM -- Log write latency thresholds: (average: 10 msec/write, maximum: 100 msec/write). 7/30/2012 10:20:04 PM -- Operation mix: Sessions 5, Inserts 40%, Deletes 20%, Replaces 5%, Reads 35%, Lazy Commits 70%. 7/30/2012 10:20:04 PM -- Performance logging started (interval: 15000 ms). 7/30/2012 10:20:04 PM -- Attaining prerequisites: 7/30/2012 10:23:11 PM -- \MSExchange (JetstressWin)\ Cache Size, Last: 2909118000.0 (lower bound: 2899103000.0, upper bound: none) 7/31/2012 12:23:11 AM -- Performance logging has ended. 7/31/2012 12:23:11 AM -- JetInterop batch transaction stats: 29865, 29599, 29588, 29552, 29908, 29806, 29695, 29900, 29803, 29811, 29798 and 29997. 7/31/2012 12:23:11 AM -- Dispatching transactions ends. 7/31/2012 12:23:11 AM -- Shutting down databases... 7/31/2012 12:23:23 AM -- Instance1944.1 (complete), Instance1944.2 (complete), Instance1944.3 (complete), Instance1944.4 (complete), Instance1944.5 (complete), Instance1944.6 (complete), Instance1944.7 (complete), Instance1944.8 (complete), Instance1944.9 (complete), Instance1944.10 (complete), Instance1944.11 (complete) and Instance1944.12 (complete) 7/31/2012 12:23:23 AM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R10_3GB_mbox_2000 Users\Performance Test\Performance_2012_7_30_22_19_54.blg has 490 samples. 7/31/2012 12:23:23 AM -- Creating test report... 7/31/2012 12:23:28 AM -- Instance1944.1 has 16.0 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.1 has 0.7 for Writes Latency. 7/31/2012 12:23:28 AM -- Instance1944.1 has 0.7 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.2 has 14.2 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.2 has 0.7 for Writes Latency. 7/31/2012 12:23:28 AM -- Instance1944.2 has 0.7 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.3 has 14.5 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.3 has 0.7 for Writes Latency. 7/31/2012 12:23:28 AM -- Instance1944.3 has 0.7 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.4 has 14.4 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.4 has 0.7 for Writes Latency. 7/31/2012 12:23:28 AM -- Instance1944.4 has 0.7 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.5 has 14.3 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.5 has 0.7 for Writes Latency. 7/31/2012 12:23:28 AM -- Instance1944.5 has 0.7 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.6 has 14.3 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.6 has 0.7 for Writes Latency. 7/31/2012 12:23:28 AM -- Instance1944.6 has 0.7 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.7 has 14.2 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.7 has 0.7 for Writes Latency. 7/31/2012 12:23:28 AM -- Instance1944.7 has 0.7 for Reads Latency. 32

7/31/2012 12:23:28 AM -- Instance1944.8 has 14.2 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.8 has 0.7 for Writes Latency. 7/31/2012 12:23:28 AM -- Instance1944.8 has 0.7 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.9 has 14.3 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.9 has 0.7 for Writes Latency. 7/31/2012 12:23:28 AM -- Instance1944.9 has 0.7 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.10 has 14.1 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.10 has 0.7 for Writes Latency. 7/31/2012 12:23:28 AM -- Instance1944.10 has 0.7 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.11 has 14.2 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.11 has 0.7 for Writes Latency. 7/31/2012 12:23:28 AM -- Instance1944.11 has 0.7 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.12 has 14.2 for Reads Latency. 7/31/2012 12:23:28 AM -- Instance1944.12 has 0.7 for Writes Latency. 7/31/2012 12:23:28 AM -- Instance1944.12 has 0.7 for Reads Latency. 7/31/2012 12:23:28 AM -- Test has 0 Maximum Page Fault Stalls/sec. 7/31/2012 12:23:28 AM -- The test has 0 Page Fault Stalls/sec samples higher than 0. 7/31/2012 12:23:28 AM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R10_3GB_mbox_2000 Users\Performance Test\Performance_2012_7_30_22_19_54.xml has 477 samples queried. 7/31/2012 12:23:29 AM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R10_3GB_mbox_2000 Users\Performance Test\Performance_2012_7_30_22_19_54.html was saved. 7/31/2012 12:23:30 AM -- Performance logging started (interval: 30000 ms). 7/31/2012 12:23:30 AM -- Verifying database checksums... 7/31/2012 3:08:08 AM -- C:\dbluns\0A_P1_db1 (100% processed), C:\dbluns\0A_P1_db2 (100% processed), C:\dbluns\0A_P1_db3 (100% processed), C:\dbluns\0A_P1_db4 (100% processed), C:\dbluns\0A_P1_db5 (100% processed), C:\dbluns\0A_P1_db6 (100% processed), C:\dbluns\0C_P2_db7 (100% processed), C:\dbluns\0C_P2_db8 (100% processed), C:\dbluns\0C_P2_db9 (100% processed), C:\dbluns\0C_P2_db10 (100% processed), C:\dbluns\0C_P2_db11 (100% processed) and C:\dbluns\0C_P2_db12 (100% processed) 7/31/2012 3:08:08 AM -- Performance logging has ended. 7/31/2012 3:08:08 AM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R10_3GB_mbox_2000 Users\Performance Test\DBChecksum_2012_7_31_0_23_29.blg has 329 samples. 33

Stress Test Result: CB10 Test Summary Overall Test Result Machine Name Pass CB10 Test Description Test Start Time Test End Time Collection Start Time Collection End Time 7/31/2012 3:57:41 AM 8/1/2012 4:01:32 AM 7/31/2012 4:01:24 AM 8/1/2012 4:01:16 AM Jetstress Version 14.01.0225.017 ESE Version 14.01.0218.012 Operating System Windows Server 2008 R2 Enterprise Service Pack 1 (6.1.7601.65536) Performance Log C:\HUS110_PE108_C1B1_SAS7K_ESRP_R10_3GB_mbox_2000 Users\Stress Test\Performance_2012_7_31_3_58_6.blg Sizing and Throughput Achieved Transactional per Second 1366.787 Target Transactional per Second 1224 Initial Size (bytes) 3592980004864 Final Size (bytes) 3651968696320 Files (Count) 12 34

Jetstress System Parameters Thread Count Minimum Cache Maximum Cache 5 (per database) 384.0 MB 3072.0 MB Insert Operations 40% Delete Operations 20% Replace Operations 5% Read Operations 35% Lazy Commits 70% Run Background Maintenance True Number of Copies per 2 35

Log Replication Performance MSExchange ==> Instances Reads/sec Reads Bytes Instance1944.1 0.814 231120.622 Instance1944.2 0.812 231188.108 Instance1944.3 0.811 230779.659 Instance1944.4 0.811 231098.934 Instance1944.5 0.812 230805.522 Instance1944.6 0.813 230934.961 Instance1944.7 0.811 230563.882 Instance1944.8 0.810 230755.000 Instance1944.9 0.812 231286.570 Instance1944.10 0.813 230793.528 Instance1944.11 0.813 231059.871 Instance1944.12 0.813 231117.604 39

Total Performance MSExchange ==> Instances Reads Latency (msec) Writes Latency (msec) Reads/sec Writes/sec Reads Bytes Writes Bytes Reads Latency (msec) Writes Latency (msec) Reads/sec Writes/sec Reads Bytes Writes Bytes Instance1944.1 16.300 2.366 97.607 52.565 118095.600 35214.832 29.250 0.664 0.814 44.390 231120.622 4536.956 Instance1944.2 14.645 2.390 98.750 52.519 119964.675 35208.907 29.931 0.689 0.812 44.160 231188.108 4551.145 Instance1944.3 14.769 2.238 98.357 52.376 119678.070 35202.781 29.942 0.663 0.811 44.151 230779.659 4543.906 Instance1944.4 14.606 2.258 98.850 52.391 120373.294 35207.476 30.630 0.689 0.811 44.090 231098.934 4549.434 Instance1944.5 14.723 2.038 98.726 52.650 119537.520 35194.929 28.624 0.665 0.812 44.275 230805.522 4537.532 Instance1944.6 14.579 2.069 98.954 52.568 120154.097 35210.283 30.097 0.687 0.813 44.209 230934.961 4546.647 Instance1944.7 14.665 2.104 98.313 52.345 119703.456 35209.216 28.651 0.655 0.811 44.107 230563.882 4546.187 Instance1944.8 14.509 2.141 98.965 52.369 120587.641 35196.958 33.151 0.672 0.810 44.071 230755.000 4542.839 Instance1944.9 14.637 2.012 98.494 52.332 120035.728 35212.092 28.732 0.656 0.812 44.103 231286.570 4556.261 Instance1944.10 14.512 2.072 98.997 52.475 120412.461 35208.944 33.179 0.672 0.813 44.146 230793.528 4554.169 Instance1944.11 14.671 1.982 98.561 52.472 119801.823 35210.567 28.153 0.653 0.813 44.168 231059.871 4555.205 Instance1944.12 14.564 2.044 99.104 52.599 120244.163 35200.775 31.266 0.669 0.813 44.199 231117.604 4549.401 Host System Performance Counter Minimum Maximum % Processor Time 2.176 0.357 5.176 Available MBytes 57988.186 57958.000 58209.000 Free System Page Table Entries 33555793.004 33555785.000 33555795.000 Transition Pages RePurposed/sec 0.000 0.000 0.000 Pool Nonpaged Bytes 86150958.314 85671936.000 87748608.000 Pool Paged Bytes 131826953.495 130752512.000 136593408.000 Page Fault Stalls/sec 0.000 0.000 0.000 Test Log7/31/2012 3:57:41 AM -- Jetstress testing begins... 40

7/31/2012 3:57:41 AM -- Preparing for testing... 7/31/2012 3:57:53 AM -- Attaching databases... 7/31/2012 3:57:53 AM -- Preparations for testing are complete. 7/31/2012 3:57:53 AM -- Starting transaction dispatch.. 7/31/2012 3:57:53 AM -- cache settings: (minimum: 384.0 MB, maximum: 3.0 GB) 7/31/2012 3:57:53 AM -- flush thresholds: (start: 30.7 MB, stop: 61.4 MB) 7/31/2012 3:58:06 AM -- read latency thresholds: (average: 20 msec/read, maximum: 100 msec/read). 7/31/2012 3:58:06 AM -- Log write latency thresholds: (average: 10 msec/write, maximum: 100 msec/write). 7/31/2012 3:58:17 AM -- Operation mix: Sessions 5, Inserts 40%, Deletes 20%, Replaces 5%, Reads 35%, Lazy Commits 70%. 7/31/2012 3:58:17 AM -- Performance logging started (interval: 15000 ms). 7/31/2012 3:58:17 AM -- Attaining prerequisites: 7/31/2012 4:01:24 AM -- \MSExchange (JetstressWin)\ Cache Size, Last: 2912432000.0 (lower bound: 2899103000.0, upper bound: none) 8/1/2012 4:01:25 AM -- Performance logging has ended. 8/1/2012 4:01:25 AM -- JetInterop batch transaction stats: 344324, 344657, 344257, 344292, 344054, 344168, 343302, 343818, 342984, 343580, 344640 and 344732. 8/1/2012 4:01:25 AM -- Dispatching transactions ends. 8/1/2012 4:01:25 AM -- Shutting down databases... 8/1/2012 4:01:32 AM -- Instance1944.1 (complete), Instance1944.2 (complete), Instance1944.3 (complete), Instance1944.4 (complete), Instance1944.5 (complete), Instance1944.6 (complete), Instance1944.7 (complete), Instance1944.8 (complete), Instance1944.9 (complete), Instance1944.10 (complete), Instance1944.11 (complete) and Instance1944.12 (complete) 8/1/2012 4:01:32 AM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R10_3GB_mbox_2000 Users\Stress Test\Performance_2012_7_31_3_58_6.blg has 5755 samples. 8/1/2012 4:01:32 AM -- Creating test report... 8/1/2012 4:02:25 AM -- Instance1944.1 has 16.3 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.1 has 0.7 for Writes Latency. 8/1/2012 4:02:25 AM -- Instance1944.1 has 0.7 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.2 has 14.6 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.2 has 0.7 for Writes Latency. 8/1/2012 4:02:25 AM -- Instance1944.2 has 0.7 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.3 has 14.8 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.3 has 0.7 for Writes Latency. 8/1/2012 4:02:25 AM -- Instance1944.3 has 0.7 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.4 has 14.6 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.4 has 0.7 for Writes Latency. 8/1/2012 4:02:25 AM -- Instance1944.4 has 0.7 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.5 has 14.7 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.5 has 0.7 for Writes Latency. 8/1/2012 4:02:25 AM -- Instance1944.5 has 0.7 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.6 has 14.6 for Reads Latency. 41

8/1/2012 4:02:25 AM -- Instance1944.6 has 0.7 for Writes Latency. 8/1/2012 4:02:25 AM -- Instance1944.6 has 0.7 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.7 has 14.7 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.7 has 0.7 for Writes Latency. 8/1/2012 4:02:25 AM -- Instance1944.7 has 0.7 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.8 has 14.5 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.8 has 0.7 for Writes Latency. 8/1/2012 4:02:25 AM -- Instance1944.8 has 0.7 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.9 has 14.6 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.9 has 0.7 for Writes Latency. 8/1/2012 4:02:25 AM -- Instance1944.9 has 0.7 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.10 has 14.5 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.10 has 0.7 for Writes Latency. 8/1/2012 4:02:25 AM -- Instance1944.10 has 0.7 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.11 has 14.7 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.11 has 0.7 for Writes Latency. 8/1/2012 4:02:25 AM -- Instance1944.11 has 0.7 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.12 has 14.6 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.12 has 0.7 for Writes Latency. 8/1/2012 4:02:25 AM -- Instance1944.12 has 0.7 for Reads Latency. 8/1/2012 4:02:25 AM -- Test has 0 Maximum Page Fault Stalls/sec. 8/1/2012 4:02:25 AM -- The test has 0 Page Fault Stalls/sec samples higher than 0. 8/1/2012 4:02:25 AM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R10_3GB_mbox_2000 Users\Stress Test\Performance_2012_7_31_3_58_6.xml has 5742 samples queried. 42

Stress Test Checksums Result: CB10 Checksum Statistics - All Seen pages Bad pages Correctable pages Wrong page-number pages File length / seconds taken C:\dbluns\0A_P1_db1\Jetstress001001.edb 9287970 0 0 0 290249 MB/10032 sec C:\dbluns\0A_P1_db2\Jetstress002001.edb 9287202 0 0 0 290225 MB/9669 sec C:\dbluns\0A_P1_db3\Jetstress003001.edb 9286946 0 0 0 290217 MB/10000 sec C:\dbluns\0A_P1_db4\Jetstress004001.edb 9286690 0 0 0 290209 MB/9642 sec C:\dbluns\0A_P1_db5\Jetstress005001.edb 9286690 0 0 0 290209 MB/10003 sec C:\dbluns\0A_P1_db6\Jetstress006001.edb 9287970 0 0 0 290249 MB/9637 sec C:\dbluns\0C_P2_db7\Jetstress007001.edb 9286690 0 0 0 290209 MB/10000 sec C:\dbluns\0C_P2_db8\Jetstress008001.edb 9286946 0 0 0 290217 MB/9683 sec C:\dbluns\0C_P2_db9\Jetstress009001.edb 9288738 0 0 0 290273 MB/9980 sec C:\dbluns\0C_P2_db10\Jetstress010001.edb 9287714 0 0 0 290241 MB/9656 sec C:\dbluns\0C_P2_db11\Jetstress011001.edb 9287970 0 0 0 290249 MB/9981 sec C:\dbluns\0C_P2_db12\Jetstress012001.edb 9287714 0 0 0 290241 MB/9661 sec (Sum) 111449240 0 0 0 3482788 MB/10032 sec 43

Disk Subsystem Performance (of checksum) LogicalDisk Avg. Disk sec/read Avg. Disk sec/write Disk Reads/sec Disk Writes/sec Avg. Disk Bytes/Read C:\dbluns\0A_P1_db1 0.052 0.000 460.645 0.000 65536.000 C:\dbluns\0A_P1_db2 0.050 0.000 478.616 0.000 65536.000 C:\dbluns\0A_P1_db3 0.052 0.000 462.803 0.000 65536.000 C:\dbluns\0A_P1_db4 0.050 0.000 480.139 0.000 65536.000 C:\dbluns\0A_P1_db5 0.052 0.000 463.284 0.000 65536.000 C:\dbluns\0A_P1_db6 0.050 0.000 480.430 0.000 65536.000 C:\dbluns\0C_P2_db7 0.052 0.000 462.763 0.000 65536.000 C:\dbluns\0C_P2_db8 0.050 0.000 477.580 0.000 65536.000 C:\dbluns\0C_P2_db9 0.052 0.000 463.861 0.000 65536.000 C:\dbluns\0C_P2_db10 0.050 0.000 479.462 0.000 65536.000 C:\dbluns\0C_P2_db11 0.052 0.000 463.752 0.000 65536.000 C:\dbluns\0C_P2_db12 0.050 0.000 479.036 0.000 65536.000 Memory System Performance (of checksum) Counter Minimum Maximum % Processor Time 1.823 1.081 2.560 Available MBytes 61119.368 61106.000 61142.000 Free System Page Table Entries 33555793.500 33555792.000 33555795.000 Transition Pages RePurposed/sec 0.000 0.000 0.000 Pool Nonpaged Bytes 86844753.246 86401024.000 87220224.000 Pool Paged Bytes 136839388.743 136835072.000 136867840.000 Test Log7/31/2012 3:57:41 AM -- Jetstress testing begins... 7/31/2012 3:57:41 AM -- Preparing for testing... 7/31/2012 3:57:53 AM -- Attaching databases... 7/31/2012 3:57:53 AM -- Preparations for testing are complete. 7/31/2012 3:57:53 AM -- Starting transaction dispatch.. 7/31/2012 3:57:53 AM -- cache settings: (minimum: 384.0 MB, maximum: 3.0 GB) 44

7/31/2012 3:57:53 AM -- flush thresholds: (start: 30.7 MB, stop: 61.4 MB) 7/31/2012 3:58:06 AM -- read latency thresholds: (average: 20 msec/read, maximum: 100 msec/read). 7/31/2012 3:58:06 AM -- Log write latency thresholds: (average: 10 msec/write, maximum: 100 msec/write). 7/31/2012 3:58:17 AM -- Operation mix: Sessions 5, Inserts 40%, Deletes 20%, Replaces 5%, Reads 35%, Lazy Commits 70%. 7/31/2012 3:58:17 AM -- Performance logging started (interval: 15000 ms). 7/31/2012 3:58:17 AM -- Attaining prerequisites: 7/31/2012 4:01:24 AM -- \MSExchange (JetstressWin)\ Cache Size, Last: 2912432000.0 (lower bound: 2899103000.0, upper bound: none) 8/1/2012 4:01:25 AM -- Performance logging has ended. 8/1/2012 4:01:25 AM -- JetInterop batch transaction stats: 344324, 344657, 344257, 344292, 344054, 344168, 343302, 343818, 342984, 343580, 344640 and 344732. 8/1/2012 4:01:25 AM -- Dispatching transactions ends. 8/1/2012 4:01:25 AM -- Shutting down databases... 8/1/2012 4:01:32 AM -- Instance1944.1 (complete), Instance1944.2 (complete), Instance1944.3 (complete), Instance1944.4 (complete), Instance1944.5 (complete), Instance1944.6 (complete), Instance1944.7 (complete), Instance1944.8 (complete), Instance1944.9 (complete), Instance1944.10 (complete), Instance1944.11 (complete) and Instance1944.12 (complete) 8/1/2012 4:01:32 AM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R10_3GB_mbox_2000 Users\Stress Test\Performance_2012_7_31_3_58_6.blg has 5755 samples. 8/1/2012 4:01:32 AM -- Creating test report... 8/1/2012 4:02:25 AM -- Instance1944.1 has 16.3 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.1 has 0.7 for Writes Latency. 8/1/2012 4:02:25 AM -- Instance1944.1 has 0.7 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.2 has 14.6 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.2 has 0.7 for Writes Latency. 8/1/2012 4:02:25 AM -- Instance1944.2 has 0.7 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.3 has 14.8 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.3 has 0.7 for Writes Latency. 8/1/2012 4:02:25 AM -- Instance1944.3 has 0.7 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.4 has 14.6 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.4 has 0.7 for Writes Latency. 8/1/2012 4:02:25 AM -- Instance1944.4 has 0.7 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.5 has 14.7 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.5 has 0.7 for Writes Latency. 8/1/2012 4:02:25 AM -- Instance1944.5 has 0.7 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.6 has 14.6 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.6 has 0.7 for Writes Latency. 8/1/2012 4:02:25 AM -- Instance1944.6 has 0.7 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.7 has 14.7 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.7 has 0.7 for Writes Latency. 8/1/2012 4:02:25 AM -- Instance1944.7 has 0.7 for Reads Latency. 45

8/1/2012 4:02:25 AM -- Instance1944.8 has 14.5 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.8 has 0.7 for Writes Latency. 8/1/2012 4:02:25 AM -- Instance1944.8 has 0.7 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.9 has 14.6 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.9 has 0.7 for Writes Latency. 8/1/2012 4:02:25 AM -- Instance1944.9 has 0.7 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.10 has 14.5 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.10 has 0.7 for Writes Latency. 8/1/2012 4:02:25 AM -- Instance1944.10 has 0.7 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.11 has 14.7 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.11 has 0.7 for Writes Latency. 8/1/2012 4:02:25 AM -- Instance1944.11 has 0.7 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.12 has 14.6 for Reads Latency. 8/1/2012 4:02:25 AM -- Instance1944.12 has 0.7 for Writes Latency. 8/1/2012 4:02:25 AM -- Instance1944.12 has 0.7 for Reads Latency. 8/1/2012 4:02:25 AM -- Test has 0 Maximum Page Fault Stalls/sec. 8/1/2012 4:02:25 AM -- The test has 0 Page Fault Stalls/sec samples higher than 0. 8/1/2012 4:02:25 AM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R10_3GB_mbox_2000 Users\Stress Test\Performance_2012_7_31_3_58_6.xml has 5742 samples queried. 8/1/2012 4:02:25 AM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R10_3GB_mbox_2000 Users\Stress Test\Performance_2012_7_31_3_58_6.html was saved. 8/1/2012 4:02:26 AM -- Performance logging started (interval: 30000 ms). 8/1/2012 4:02:26 AM -- Verifying database checksums... 8/1/2012 6:49:39 AM -- C:\dbluns\0A_P1_db1 (100% processed), C:\dbluns\0A_P1_db2 (100% processed), C:\dbluns\0A_P1_db3 (100% processed), C:\dbluns\0A_P1_db4 (100% processed), C:\dbluns\0A_P1_db5 (100% processed), C:\dbluns\0A_P1_db6 (100% processed), C:\dbluns\0C_P2_db7 (100% processed), C:\dbluns\0C_P2_db8 (100% processed), C:\dbluns\0C_P2_db9 (100% processed), C:\dbluns\0C_P2_db10 (100% processed), C:\dbluns\0C_P2_db11 (100% processed) and C:\dbluns\0C_P2_db12 (100% processed) 8/1/2012 6:49:39 AM -- Performance logging has ended. 8/1/2012 6:49:39 AM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R10_3GB_mbox_2000 Users\Stress Test\DBChecksum_2012_8_1_4_2_25.blg has 334 samples. 46

Backup Test Result: CB10 Backup Statistics - All Instance Size (MBytes) Elapsed Backup Time MBytes Transferred/sec Instance1944.1 290241.09 01:34:35 51.14 Instance1944.2 290217.09 01:22:43 58.47 Instance1944.3 290209.09 01:20:33 60.05 Instance1944.4 290201.09 01:26:08 56.15 Instance1944.5 290201.09 01:21:46 59.15 Instance1944.6 290241.09 01:25:05 56.85 Instance1944.7 290201.09 01:24:44 57.07 Instance1944.8 290209.09 01:30:12 53.62 Instance1944.9 290265.09 01:23:35 57.88 Instance1944.10 290233.09 01:29:43 53.91 Instance1944.11 290241.09 01:23:21 58.04 Instance1944.12 290233.09 01:30:47 53.28 Jetstress System Parameters Thread Count Minimum Cache Maximum Cache 5 (per database) 384.0 MB 3072.0 MB Insert Operations 40% Delete Operations 20% Replace Operations 5% Read Operations 35% Lazy Commits 70% 47

Transactional Performance MSExchange ==> Instances Reads Latency (msec) Writes Latency (msec) Reads/sec Writes/sec Reads Bytes Writes Bytes Reads Latency (msec) Writes Latency (msec) Reads/sec Writes/sec Reads Bytes Writes Bytes Instance1944.1 15.333 0.000 199.809 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 Instance1944.2 6.787 0.000 233.778 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 Instance1944.3 6.594 0.000 240.074 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 Instance1944.4 7.651 0.000 225.074 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 Instance1944.5 6.661 0.000 236.993 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 Instance1944.6 7.313 0.000 226.162 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 Instance1944.7 7.516 0.000 227.886 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 Instance1944.8 8.871 0.000 214.018 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 Instance1944.9 6.951 0.000 231.196 0.000 262144.029 0.000 0.000 0.000 0.000 0.000 0.000 0.000 Instance1944.10 8.645 0.000 214.434 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 Instance1944.11 6.986 0.000 232.030 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 Instance1944.12 9.696 0.000 211.967 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 Host System Performance Counter Minimum Maximum % Processor Time 1.536 0.736 2.109 Available MBytes 61116.080 61025.000 61130.000 Free System Page Table Entries 33555793.915 33555793.000 33555795.000 Transition Pages RePurposed/sec 0.000 0.000 0.000 Pool Nonpaged Bytes 86169687.149 85917696.000 86568960.000 Pool Paged Bytes 145240042.213 137703424.000 185982976.000 Page Fault Stalls/sec 0.000 0.000 0.000 49

Test Log8/1/2012 9:05:47 PM -- Jetstress testing begins... 8/1/2012 9:05:47 PM -- Preparing for testing... 8/1/2012 9:05:59 PM -- Attaching databases... 8/1/2012 9:05:59 PM -- Preparations for testing are complete. 8/1/2012 9:06:17 PM -- Performance logging started (interval: 30000 ms). 8/1/2012 9:06:17 PM -- Backing up databases... 8/1/2012 10:40:52 PM -- Performance logging has ended. 8/1/2012 10:40:52 PM -- Instance1944.1 (100% processed), Instance1944.2 (100% processed), Instance1944.3 (100% processed), Instance1944.4 (100% processed), Instance1944.5 (100% processed), Instance1944.6 (100% processed), Instance1944.7 (100% processed), Instance1944.8 (100% processed), Instance1944.9 (100% processed), Instance1944.10 (100% processed), Instance1944.11 (100% processed) and Instance1944.12 (100% processed) 8/1/2012 10:40:52 PM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R10_3GB_mbox_2000 Users\ Backup\Backup_2012_8_1_21_5_59.blg has 188 samples. 8/1/2012 10:40:52 PM -- Creating test report... 50

Soft Recovery Test Result: CB10 Soft-Recovery Statistics - All Instance Log files replayed Elapsed seconds Instance1944.1 501 1508.7952982 Instance1944.2 501 1448.6458578 Instance1944.3 502 1453.4061301 Instance1944.4 511 1472.2022052 Instance1944.5 503 1468.9450188 Instance1944.6 504 1453.1561158 Instance1944.7 510 1473.4542768 Instance1944.8 508 1471.4501621 Instance1944.9 502 1451.9040442 Instance1944.10 506 1465.4348181 Instance1944.11 501 1451.9040442 Instance1944.12 506 1467.9429615 51

Total Performance MSExchange ==> Instances Reads Latency (msec) Writes Latency (msec) Reads/sec Writes/sec Reads Bytes Writes Bytes Reads Latency (msec) Writes Latency (msec) Reads/sec Writes/sec Reads Bytes Writes Bytes Instance1944.1 12.892 0.854 364.839 1.988 63834.610 32592.300 7.368 0.000 2.982 0.000 231253.334 0.000 Instance1944.2 12.328 0.897 388.713 2.071 61925.046 32768.000 7.140 0.000 3.106 0.000 232469.428 0.000 Instance1944.3 12.407 0.914 381.163 2.069 62236.863 32676.724 7.121 0.000 3.104 0.000 231868.506 0.000 Instance1944.4 12.373 0.863 387.769 2.082 61397.043 32677.978 6.865 0.001 3.123 0.002 231898.135 1.407 Instance1944.5 12.280 0.903 388.335 2.051 61842.945 32768.000 7.181 0.000 3.076 0.000 232564.669 0.000 Instance1944.6 12.230 0.887 387.989 2.078 62683.186 32768.000 5.967 0.000 3.116 0.000 232516.373 0.000 Instance1944.7 12.246 0.906 389.334 2.074 62573.432 32677.978 6.918 0.000 3.110 0.000 231901.787 0.000 Instance1944.8 12.229 0.855 386.879 2.070 62634.880 32677.978 6.868 0.005 3.104 0.002 231872.760 1.407 Instance1944.9 12.234 0.905 389.681 2.073 62475.493 32768.000 7.083 0.004 3.110 0.002 232525.941 1.426 Instance1944.10 12.180 0.884 392.876 2.069 62196.089 32677.481 6.957 0.000 3.103 0.000 231766.466 0.000 Instance1944.11 12.309 0.882 386.363 2.069 62611.052 32768.000 7.293 0.001 3.104 0.002 232569.097 1.426 Instance1944.12 12.239 0.855 391.049 2.063 62418.155 32768.000 6.900 0.000 3.094 0.000 232497.057 0.000 Host System Performance Counter Minimum Maximum % Processor Time 2.062 0.000 5.723 Available MBytes 58032.235 57953.000 60689.000 Free System Page Table Entries 33555282.989 33555281.000 33555283.000 Transition Pages RePurposed/sec 0.000 0.000 0.000 Pool Nonpaged Bytes 86807415.102 86433792.000 87453696.000 Pool Paged Bytes 140126076.578 140103680.000 140161024.000 Page Fault Stalls/sec 0.000 0.000 0.000 Test Log8/1/2012 11:16:37 PM -- Jetstress testing begins... 55

8/1/2012 11:16:37 PM -- Preparing for testing... 8/1/2012 11:16:49 PM -- Attaching databases... 8/1/2012 11:16:49 PM -- Preparations for testing are complete. 8/1/2012 11:16:49 PM -- Starting transaction dispatch.. 8/1/2012 11:16:49 PM -- cache settings: (minimum: 384.0 MB, maximum: 3.0 GB) 8/1/2012 11:16:49 PM -- flush thresholds: (start: 30.7 MB, stop: 61.4 MB) 8/1/2012 11:17:02 PM -- read latency thresholds: (average: 20 msec/read, maximum: 100 msec/read). 8/1/2012 11:17:02 PM -- Log write latency thresholds: (average: 10 msec/write, maximum: 100 msec/write). 8/1/2012 11:17:08 PM -- Operation mix: Sessions 5, Inserts 40%, Deletes 20%, Replaces 5%, Reads 35%, Lazy Commits 70%. 8/1/2012 11:17:08 PM -- Performance logging started (interval: 15000 ms). 8/1/2012 11:17:08 PM -- Generating log files... 8/2/2012 12:45:47 AM -- C:\logluns\0A_P1_log1 (100.2% generated), C:\logluns\0A_P1_log2 (100.2% generated), C:\logluns\0A_P1_log3 (100.4% generated), C:\logluns\0A_P1_log4 (102.2% generated), C:\logluns\0A_P1_log5 (100.6% generated), C:\logluns\0A_P1_log6 (100.8% generated), C:\logluns\0C_P2_log7 (102.0% generated), C:\logluns\0C_P2_log8 (101.6% generated), C:\logluns\0C_P2_log9 (100.4% generated), C:\logluns\0C_P2_log10 (101.2% generated), C:\logluns\0C_P2_log11 (100.2% generated) and C:\logluns\0C_P2_log12 (101.2% generated) 8/2/2012 12:45:47 AM -- Performance logging has ended. 8/2/2012 12:45:47 AM -- JetInterop batch transaction stats: 22025, 22039, 22154, 22356, 22209, 22229, 22419, 22360, 22228, 22344, 22171 and 22195. 8/2/2012 12:45:47 AM -- Dispatching transactions ends. 8/2/2012 12:45:47 AM -- Shutting down databases... 8/2/2012 12:45:52 AM -- Instance1944.1 (complete), Instance1944.2 (complete), Instance1944.3 (complete), Instance1944.4 (complete), Instance1944.5 (complete), Instance1944.6 (complete), Instance1944.7 (complete), Instance1944.8 (complete), Instance1944.9 (complete), Instance1944.10 (complete), Instance1944.11 (complete) and Instance1944.12 (complete) 8/2/2012 12:45:52 AM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R10_3GB_mbox_2000 Users\Soft Recovery\Performance_2012_8_1_23_17_2.blg has 353 samples. 8/2/2012 12:45:52 AM -- Creating test report... 8/2/2012 12:45:54 AM -- Instance1944.1 has 19.8 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.1 has 0.6 for Writes Latency. 8/2/2012 12:45:54 AM -- Instance1944.1 has 0.6 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.2 has 18.1 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.2 has 0.6 for Writes Latency. 8/2/2012 12:45:54 AM -- Instance1944.2 has 0.6 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.3 has 18.1 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.3 has 0.6 for Writes Latency. 8/2/2012 12:45:54 AM -- Instance1944.3 has 0.6 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.4 has 18.1 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.4 has 0.6 for Writes Latency. 8/2/2012 12:45:54 AM -- Instance1944.4 has 0.6 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.5 has 18.0 for Reads Latency. 56

8/2/2012 12:45:54 AM -- Instance1944.5 has 0.6 for Writes Latency. 8/2/2012 12:45:54 AM -- Instance1944.5 has 0.6 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.6 has 18.1 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.6 has 0.6 for Writes Latency. 8/2/2012 12:45:54 AM -- Instance1944.6 has 0.6 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.7 has 18.1 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.7 has 0.6 for Writes Latency. 8/2/2012 12:45:54 AM -- Instance1944.7 has 0.6 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.8 has 18.0 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.8 has 0.6 for Writes Latency. 8/2/2012 12:45:54 AM -- Instance1944.8 has 0.6 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.9 has 18.0 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.9 has 0.6 for Writes Latency. 8/2/2012 12:45:54 AM -- Instance1944.9 has 0.6 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.10 has 18.1 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.10 has 0.6 for Writes Latency. 8/2/2012 12:45:54 AM -- Instance1944.10 has 0.6 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.11 has 18.0 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.11 has 0.6 for Writes Latency. 8/2/2012 12:45:54 AM -- Instance1944.11 has 0.6 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.12 has 18.1 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.12 has 0.6 for Writes Latency. 8/2/2012 12:45:54 AM -- Instance1944.12 has 0.6 for Reads Latency. 8/2/2012 12:45:54 AM -- Test has 0 Maximum Page Fault Stalls/sec. 8/2/2012 12:45:54 AM -- The test has 0 Page Fault Stalls/sec samples higher than 0. 8/2/2012 12:45:54 AM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R10_3GB_mbox_2000 Users\Soft Recovery\Performance_2012_8_1_23_17_2.xml has 352 samples queried. 8/2/2012 12:45:54 AM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R10_3GB_mbox_2000 Users\Soft Recovery\Performance_2012_8_1_23_17_2.html was saved. 8/2/2012 2:12:35 AM -- Performance logging started (interval: 4000 ms). 8/2/2012 2:12:35 AM -- Recovering databases... 8/2/2012 2:37:43 AM -- Performance logging has ended. 8/2/2012 2:37:43 AM -- Instance1944.1 (1508.7952982), Instance1944.2 (1448.6458578), Instance1944.3 (1453.4061301), Instance1944.4 (1472.2022052), Instance1944.5 (1468.9450188), Instance1944.6 (1453.1561158), Instance1944.7 (1473.4542768), Instance1944.8 (1471.4501621), Instance1944.9 (1451.9040442), Instance1944.10 (1465.4348181), Instance1944.11 (1451.9040442) and Instance1944.12 (1467.9429615) 8/2/2012 2:37:44 AM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R10_3GB_mbox_2000 Users\Soft Recovery\SoftRecovery_2012_8_2_2_12_29.blg has 374 samples. 8/2/2012 2:37:44 AM -- Creating test report... 57

Soft Recovery Test Performance Result: CB10 Test Summary Overall Test Result Machine Name Pass CB10 Test Description Test Start Time Test End Time Collection Start Time Collection End Time 8/1/2012 11:16:37 PM 8/2/2012 12:45:52 AM 8/1/2012 11:17:23 PM 8/2/2012 12:45:34 AM Jetstress Version 14.01.0225.017 ESE Version 14.01.0218.012 Operating System Windows Server 2008 R2 Enterprise Service Pack 1 (6.1.7601.65536) Performance Log C:\HUS110_PE108_C1B1_SAS7K_ESRP_R10_3GB_mbox_2000 Users\Soft Recovery\Performance_2012_8_1_23_17_2.blg Sizing and Throughput Achieved Transactional per Second 1446.076 Capacity Percentage 100% Throughput Percentage 100% Initial Size (bytes) 3651968696320 Final Size (bytes) 3655802290176 Files (Count) 12 58

Jetstress System Parameters Thread Count Minimum Cache Maximum Cache 5 (per database) 384.0 MB 3072.0 MB Insert Operations 40% Delete Operations 20% Replace Operations 5% Read Operations 35% Lazy Commits 70% 59

Transactional Performance MSExchange ==> Instances Reads Latency (msec) Writes Latency (msec) Reads/sec Writes/sec Reads Bytes Writes Bytes Reads Latency (msec) Writes Latency (msec) Reads/sec Writes/sec Reads Bytes Writes Bytes Instance1944.1 19.847 4.614 65.330 53.669 32768.000 35147.429 0.000 0.590 0.000 46.015 0.000 4539.699 Instance1944.2 18.099 4.717 65.827 53.994 32768.000 35188.616 0.000 0.581 0.000 45.954 0.000 4544.236 Instance1944.3 18.066 4.442 65.086 53.454 32768.000 35229.220 0.000 0.580 0.000 45.682 0.000 4578.271 Instance1944.4 18.076 4.534 66.621 54.955 32768.000 35141.488 0.000 0.580 0.000 46.603 0.000 4572.116 Instance1944.5 17.987 4.085 66.425 54.746 32768.000 35154.110 0.000 0.587 0.000 46.356 0.000 4523.558 Instance1944.6 18.066 4.277 65.850 54.011 32768.000 35206.136 0.000 0.585 0.000 46.382 0.000 4527.480 Instance1944.7 18.052 4.285 66.858 55.113 32768.000 35164.703 0.000 0.573 0.000 47.054 0.000 4524.345 Instance1944.8 18.049 4.515 66.287 54.687 32768.000 35217.029 0.000 0.573 0.000 46.552 0.000 4552.830 Instance1944.9 18.039 4.438 65.769 54.237 32768.000 35175.331 0.000 0.568 0.000 46.238 0.000 4531.796 Instance1944.10 18.055 4.719 66.656 55.027 32768.000 35140.828 0.000 0.580 0.000 46.499 0.000 4532.736 Instance1944.11 18.011 4.831 65.761 53.994 32768.000 35145.027 0.000 0.574 0.000 46.276 0.000 4521.067 Instance1944.12 18.078 5.039 66.717 55.000 32768.000 35142.475 0.000 0.582 0.000 46.663 0.000 4527.807 Host System Performance Counter Minimum Maximum % Processor Time 2.259 0.946 3.528 Available MBytes 58025.487 57972.000 60523.000 Free System Page Table Entries 33555793.975 33555791.000 33555795.000 Transition Pages RePurposed/sec 0.000 0.000 0.000 Pool Nonpaged Bytes 86544998.980 86237184.000 87343104.000 Pool Paged Bytes 138341170.040 138326016.000 138403840.000 Page Fault Stalls/sec 0.000 0.000 0.000 Test Log8/1/2012 11:16:37 PM -- Jetstress testing begins... 61

8/1/2012 11:16:37 PM -- Preparing for testing... 8/1/2012 11:16:49 PM -- Attaching databases... 8/1/2012 11:16:49 PM -- Preparations for testing are complete. 8/1/2012 11:16:49 PM -- Starting transaction dispatch.. 8/1/2012 11:16:49 PM -- cache settings: (minimum: 384.0 MB, maximum: 3.0 GB) 8/1/2012 11:16:49 PM -- flush thresholds: (start: 30.7 MB, stop: 61.4 MB) 8/1/2012 11:17:02 PM -- read latency thresholds: (average: 20 msec/read, maximum: 100 msec/read). 8/1/2012 11:17:02 PM -- Log write latency thresholds: (average: 10 msec/write, maximum: 100 msec/write). 8/1/2012 11:17:08 PM -- Operation mix: Sessions 5, Inserts 40%, Deletes 20%, Replaces 5%, Reads 35%, Lazy Commits 70%. 8/1/2012 11:17:08 PM -- Performance logging started (interval: 15000 ms). 8/1/2012 11:17:08 PM -- Generating log files... 8/2/2012 12:45:47 AM -- C:\logluns\0A_P1_log1 (100.2% generated), C:\logluns\0A_P1_log2 (100.2% generated), C:\logluns\0A_P1_log3 (100.4% generated), C:\logluns\0A_P1_log4 (102.2% generated), C:\logluns\0A_P1_log5 (100.6% generated), C:\logluns\0A_P1_log6 (100.8% generated), C:\logluns\0C_P2_log7 (102.0% generated), C:\logluns\0C_P2_log8 (101.6% generated), C:\logluns\0C_P2_log9 (100.4% generated), C:\logluns\0C_P2_log10 (101.2% generated), C:\logluns\0C_P2_log11 (100.2% generated) and C:\logluns\0C_P2_log12 (101.2% generated) 8/2/2012 12:45:47 AM -- Performance logging has ended. 8/2/2012 12:45:47 AM -- JetInterop batch transaction stats: 22025, 22039, 22154, 22356, 22209, 22229, 22419, 22360, 22228, 22344, 22171 and 22195. 8/2/2012 12:45:47 AM -- Dispatching transactions ends. 8/2/2012 12:45:47 AM -- Shutting down databases... 8/2/2012 12:45:52 AM -- Instance1944.1 (complete), Instance1944.2 (complete), Instance1944.3 (complete), Instance1944.4 (complete), Instance1944.5 (complete), Instance1944.6 (complete), Instance1944.7 (complete), Instance1944.8 (complete), Instance1944.9 (complete), Instance1944.10 (complete), Instance1944.11 (complete) and Instance1944.12 (complete) 8/2/2012 12:45:52 AM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R10_3GB_mbox_2000 Users\Soft Recovery\Performance_2012_8_1_23_17_2.blg has 353 samples. 8/2/2012 12:45:52 AM -- Creating test report... 8/2/2012 12:45:54 AM -- Instance1944.1 has 19.8 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.1 has 0.6 for Writes Latency. 8/2/2012 12:45:54 AM -- Instance1944.1 has 0.6 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.2 has 18.1 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.2 has 0.6 for Writes Latency. 8/2/2012 12:45:54 AM -- Instance1944.2 has 0.6 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.3 has 18.1 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.3 has 0.6 for Writes Latency. 8/2/2012 12:45:54 AM -- Instance1944.3 has 0.6 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.4 has 18.1 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.4 has 0.6 for Writes Latency. 8/2/2012 12:45:54 AM -- Instance1944.4 has 0.6 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.5 has 18.0 for Reads Latency. 62

8/2/2012 12:45:54 AM -- Instance1944.5 has 0.6 for Writes Latency. 8/2/2012 12:45:54 AM -- Instance1944.5 has 0.6 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.6 has 18.1 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.6 has 0.6 for Writes Latency. 8/2/2012 12:45:54 AM -- Instance1944.6 has 0.6 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.7 has 18.1 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.7 has 0.6 for Writes Latency. 8/2/2012 12:45:54 AM -- Instance1944.7 has 0.6 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.8 has 18.0 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.8 has 0.6 for Writes Latency. 8/2/2012 12:45:54 AM -- Instance1944.8 has 0.6 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.9 has 18.0 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.9 has 0.6 for Writes Latency. 8/2/2012 12:45:54 AM -- Instance1944.9 has 0.6 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.10 has 18.1 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.10 has 0.6 for Writes Latency. 8/2/2012 12:45:54 AM -- Instance1944.10 has 0.6 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.11 has 18.0 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.11 has 0.6 for Writes Latency. 8/2/2012 12:45:54 AM -- Instance1944.11 has 0.6 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.12 has 18.1 for Reads Latency. 8/2/2012 12:45:54 AM -- Instance1944.12 has 0.6 for Writes Latency. 8/2/2012 12:45:54 AM -- Instance1944.12 has 0.6 for Reads Latency. 8/2/2012 12:45:54 AM -- Test has 0 Maximum Page Fault Stalls/sec. 8/2/2012 12:45:54 AM -- The test has 0 Page Fault Stalls/sec samples higher than 0. 8/2/2012 12:45:54 AM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R10_3GB_mbox_2000 Users\Soft Recovery\Performance_2012_8_1_23_17_2.xml has 352 samples queried. 63

Hitachi Data Systems Corporation 2012. All rights reserved. HITACHI is a trademark or registered trademark of Hitachi, Ltd. Microsoft, Exchange 2010, and Exchange Server 2010 are trademarks or registered trademarks of Microsoft Corporation. All other trademarks, service marks, and company names are properties of their respective owners.. Notice: This document is for informational purposes only, and does not set forth any warranty, expressed or implied, concerning any equipment or service offered or to be offered by Hitachi Data Systems Corporation. Hitachi Data Systems Corporation 2012. All Rights Reserved. ESRP-080-00 July-August 2012 Corporate Headquarters Regional Contact Information 2845 Lafayette Street, Americas: +1 408 970 1000 or info@hds.com Santa Clara, California 95050-2639 USA Europe, Middle East and Africa: +44 (0) 1753 618000 or info.emea@hds.com www.hds.com Asia Pacific: +852 3189 7900 or hds.marketing.apac@hds.com 64