Hitachi Unified Storage 110 Dynamically Provisioned 10,400 Mailbox Exchange 2010 Mailbox Resiliency Storage Solution

1 Hitachi Unified Storage 110 Dynamically Provisioned 10,400 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 A RAID 5 Drive Failure and Rebuild... 21 Appendix B Test Reports... 22 Performance Test Result: CB10... 22 Performance Test Checksums Result: CB10... 33 Stress Test Result: CB10... 38 Stress Test Checksums Result: CB10... 48 Backup Test Result: CB10... 53 Soft Recovery Test Result: CB10... 58 Soft Recovery Test Performance Result: CB10... 67 2

Hitachi Unified Storage 110 Dynamically Provisioned 10,400 Mailbox Exchange 2010 Mailbox Resiliency Storage Solution 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 Systems best 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 10,400 users and four servers. This testing used Hitachi Unified Storage 110 with Hitachi Dynamic Provisioning in a two-pool RAID-5 (8D+1P) (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.46GHz 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 twenty database copies and two servers. The test configuration was capable of supporting 10,400 users with a 0.12 IOPS per user profile and user mailbox size of 1 GB. A Hitachi Unified Storage 110 with the following was used for these tests: 117 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, Hitachi Unified Storage 110 is fully capable of being used as the core underlying storage platform for high-performance 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 Hitachi 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 that make 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 server blades (one simulated) that host active mailboxes in twenty databases. To target the 10,400-user resiliency solution, a Hitachi Unified Storage 110 storage system was configured with 117 disks (maximum 120). Four servers (one per DAG) were used, with each server configured with 2,600 mailboxes. There were 20 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 6

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 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-5 (8D+1P) group. There were 117 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-5(8+1) HDP Pool Disk Layout Unit 4 RG10 RG11 RG12 S S S Unit 3 RG8 RG9 RG10 Unit 2 RG5 RG6 RG7 Unit 1 RG2 RG3 RG4 RG5 Unit 0 RG0 RG1 RG2 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 11 RAID-5 (8D+1P) groups and the log pool was created from 2 RAID-5 (8D+1P) groups. From the database pool, 80 DP-VOLs (each specified to have a 1,920 GB size limit) were created for 80 databases (twenty per server). From the log pool, 80 DP-VOLs (each specified to have a size limit of 192 GB) were created for 80 logs (twenty per server). 7

Table 2 outlines the port layout for the primary storage and servers. An identical configuration would be deployed on the replicated storage and servers for this solution. Table 2. Hitachi Unified Storage 110 Ports to Server Layout 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-10 0-9 0C s 11-20 10-19 1A s 21-30 20-29 1C s 31-40 30-39 0B s 41-50 40-49 0B s 51-60 50-59 1B s 61-70 60-69 1D s 71-80 70-79 8

Table 4 outlines the port layout with the log 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 4. Hitachi Unified Storage 110 Ports to Log DP-VOL Layout Port Log Log DP-VOLs 0A log 81-90 80-89 0C log 91-100 90-99 1A log 101-110 100-109 1C log 111-120 110-119 0B log 121-130 120-129 0B log 131-140 130-139 1B log 141-150 140-149 1D log 151-160 150-159 Table 5 provides the detailed specifications for the storage configuration which uses RAID-5 (8D+1P) groups and 2TB 7K 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-9 1920 RAID-5 s 1-10 1 0C/1C 10-19 1920 RAID-5 s 11-20 CB11 1 1A/0A 20-29 1920 RAID-5 s 21-30 1 1C/0C 30-39 1920 RAID-5 s 31-40 CB12 1 0B/1B 40-49 1920 RAID-5 s 41-50 1 0D/1D 50-59 1920 RAID-5 s 51-60 CB13 1 1B/0B 60-69 1920 RAID-5 s 61-70 1 1D/0D 70-79 1920 RAID-5 s 71-80 CB10 0 0A/1A 80-89 192 RAID-5 log 81-90 0 0C/1C 90-99 192 RAID-5 log 91-100 CB11 0 1A/0A 100-109 192 RAID-5 log 101-110 0 1C/0C 110-119 192 RAID-5 log 111-120 CB12 0 0B/1B 120-129 192 RAID-5 log 121-130 0 0D/1D 130-139 192 RAID-5 log 131-140 CB13 0 1B/0B 140-149 192 RAID-5 log 141-150 0 1D/0D 150-159 192 RAID-5 log 151-160 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 10,400 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.1 IOPS per user (0.12 tested for 20 percent growth) 1 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 10,400 Number of database availability groups (DAGs) 4 Number of servers per DAG 2 (1 simulated) Number of active mailboxes per server 2,600 Number of databases per host 20 Number of copies per database 2 Number of mailboxes per database 130 Simulated profile: s per second per mailbox (IOPS, include 20% headroom) 0.12 LU size Log LU siz Total database size for performance testing 1920 GB 192 GB 10,400 GB % storage capacity used by Exchange database** 6.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 117 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 99 (dynamic provisioning pool) Total raw storage capacity (GB) 198,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-5 (8D+1P) at storage level 155,760 GB Storage capacity utilization 78.7% capacity utilization 77.6% 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 18(dynamic provisioning pool) Total raw storage capacity (GB) 36,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-5 (8D+1P) at storage level 28,320 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 (1 Gb/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 8 Gb/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 117 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 99 (dynamic provisioning pool) total raw storage capacity (GB) 198,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-5 (8D+1P) at storage level 155,760 GB Storage capacity utilization 78.7% capacity utilization 77.6% 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 18 (dynamic provisioning pool) Total raw storage capacity (GB) 36,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-5 (8D+1P) at storage level 28,320 GB 14

Best Practices Microsoft Exchange Server 2010 is a disk-intensive application. It presents two distinct workload patterns to the storage, with 32KB 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. The log LUs should be at least 10 percent of the size of the database LUs. 8. Hitachi Data Systems does not recommend using LU concatenation. 9. Hitachi Data Systems recommends implementing Mailbox Resiliency using the Exchange Server 2010 Availability Group feature. 10. Ensure that each DAG maintains at least two database copies to provide high availability. 11. Isolate active databases and their replicated copies in separate dynamic provisioning pools or ensure that they are located on a separate Hitachi Unified Storage110. 12. Use fewer, larger LUs for Exchange 2010 databases (up to 2TB) with Background Maintenance (24x7) enabled. 13. 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. 14. 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. 15

15. 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 490 Disk Reads Per Second 288 Disk Writes Per Second 201 Disk Read Latency (ms) 11.1 Disk Write Latency (ms) 1.3 Transaction Log Log Disk Writes Per Second 191 Log Disk Write Latency (ms) 0.8 17

Table 17. Individual Server Metrics for Exchange Server (CB11) Disk Transfers Per Second 491 Disk Reads Per Second 289 Disk Writes Per Second 202 Disk Read Latency (ms) 10.9 Disk Write Latency (ms) 1.3 Transaction Log Log Disk Writes Per Second 192 Log Disk Write Latency (ms) 0.8 Table 18. Individual Server Metrics for Exchange Server (CB12) Disk Transfers Per Second 488 Disk Reads Per Second 287 Disk Writes Per Second 201 Disk Read Latency (ms) 10.8 Disk Write Latency (ms) 1.3 Transaction Log Log Disk Writes Per Second 191 Log Disk Write Latency (ms) 0.8 Table 19. Individual Server Metrics for Exchange Server (CB13) Disk Transfers Per Second 492 Disk Reads Per Second 289 Disk Writes Per Second 202 Disk Read Latency (ms) 10.8 Disk Write Latency (ms) 1.3 Transaction Log Log Disk Writes Per Second 192 Log Disk Write Latency (ms) 0.8 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 1960.69 Disk Reads Per Second 1154.27 Disk Writes Per Second 806.42 Disk Read Latency (ms) 10.92 Disk Write Latency (ms) 1.32 Transaction Log Log Disk Writes Per Second 765.18 Log Disk Write Latency (ms) 0.78 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 19.66 MB Read Per Second Total Per Server 393.26 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) 4.42335 19

Conclusion This document details a tested and robust Exchange Server 2010 Resiliency solution capable of supporting 10,400 users with a 0.12 IOPS per user profile and user mailbox size of 1 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 117 2TB 7K RPM SAS disks in a RAID-5 (8D+1P) 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 10,400 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 A RAID 5 Drive Failure and Rebuild These ESRP tests used RAID-5 (8D+1P) rather than RAID-6 (8D+2P) or RAID-10 (for example, 4D+4D). RAID-5 is a more capacity-efficient RAID level than the others. It loses only 12.5 percent of the usable capacity when using 8D+1P. This compares to 20 percent for (8D+2P) or 50 percent for (4D+4D). One downside with the use of parity RAID-5 instead of mirrored and striped RAID-10 is that the internal disk write penalty for host writes is higher. RAID-5 volumes require four physical disk s (2 reads, 2 writes) on the backend for every host write. In comparison, RAID-10 requires two physical s (2 writes) and RAID-6 requires six physical s (3 reads, 3 writes) for each host write. The other downside is the rebuild time for the RAID group after a sudden disk failure. Hitachi Unified Storage 100 family storage systems continually scans the storage system looking for soft fails, because an excessive soft fail count is a predictor of a hard failure in the future. If the number of soft fails exceeds the user-set failure threshold in a 24-hour period, the Hitachi Unified Storage 100 family storage system does the following, in order: 1. Executes a disk-to-disk copy to a global hot spare to avoid a RAID-5 (or RAID-6) volume rebuild. 2. Switches to using the spare disk and marks the source disk as failed. 3. Alerts person responsible for storage system maintenance to replace the disk. If a hard fail of a disk in a RAID volume does occur, the following happens: If using RAID-10, the contents of the good disk are mirrored onto a spare disk. These hot spares are user-defined in several disk enclosures on a storage system. If using RAID-5 or RAID-6, all disks in the RAID group must be read to recreate the missing data or parity that was located on the failed disk onto the spare disk. This rebuild mode is called corrective copy. An associated array setting called [Drive] Restore Options determines how aggressive the rebuild operation is while there are still ongoing host s. This setting has three levels: aggressive, moderate, and background (extremely slow). Lab tests were conducted on a Hitachi Unified Storage 110 volume using RAID-5 (8D+1P) on 900 GB 10K SAS disks with an aggressive restore option setting. A corrective copy operation took about 5 hours to complete with a 25% host load with a random (70% reads, 30% writes) host workload on the four LUs from that RAID group. When there was a sustained 90% host workload (of the same type) to the four LUNs from that RAID group, the rebuild time increased to about 26 hours. The IOPS performance on the four LUNs from that RAID group was only slightly reduced in both cases. 21

Appendix B 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 8/24/2012 1:12:53 AM 8/24/2012 3:44:35 AM 8/24/2012 1:26:59 AM 8/24/2012 3:26:48 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_R5_1GB_mbox_2600 Users\Performance Test\Performance_2012_8_24_1_13_38.blg Sizing and Throughput Achieved Transactional per Second 489.813 Target Transactional per Second 312 Initial Size (bytes) 10748303769600 Final Size (bytes) 10750384144384 Files (Count) 20 22

Jetstress System Parameters Thread Count Minimum Cache Maximum Cache 3 (per database) 640.0 MB 5120.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 23

Configuration Instance5488.1 Instance5488.2 Instance5488.3 Instance5488.4 Instance5488.5 Instance5488.6 Instance5488.7 Instance5488.8 Instance5488.9 Instance5488.10 Instance5488.11 Instance5488.12 Instance5488.13 Instance5488.14 Instance5488.15 Instance5488.16 Instance5488.17 Instance5488.18 Log path: C:\logluns\log1 : C:\dbluns\db1\Jetstress001001.edb Log path: C:\logluns\log2 : C:\dbluns\db2\Jetstress002001.edb Log path: C:\logluns\log3 : C:\dbluns\db3\Jetstress003001.edb Log path: C:\logluns\log4 : C:\dbluns\db4\Jetstress004001.edb Log path: C:\logluns\log5 : C:\dbluns\db5\Jetstress005001.edb Log path: C:\logluns\log6 : C:\dbluns\db6\Jetstress006001.edb Log path: C:\logluns\log7 : C:\dbluns\db7\Jetstress007001.edb Log path: C:\logluns\log8 : C:\dbluns\db8\Jetstress008001.edb Log path: C:\logluns\log9 : C:\dbluns\db9\Jetstress009001.edb Log path: C:\logluns\log10 : C:\dbluns\db10\Jetstress010001.edb Log path: C:\logluns\log11 : C:\dbluns\db11\Jetstress011001.edb Log path: C:\logluns\log12 : C:\dbluns\db12\Jetstress012001.edb Log path: C:\logluns\log13 : C:\dbluns\db13\Jetstress013001.edb Log path: C:\logluns\log14 : C:\dbluns\db14\Jetstress014001.edb Log path: C:\logluns\log15 : C:\dbluns\db15\Jetstress015001.edb Log path: C:\logluns\log16 : C:\dbluns\db16\Jetstress016001.edb Log path: C:\logluns\log17 : C:\dbluns\db17\Jetstress017001.edb Log path: C:\logluns\log18 24

: C:\dbluns\db18\Jetstress018001.edb Instance5488.19 Instance5488.20 Log path: C:\logluns\log19 : C:\dbluns\db19\Jetstress019001.edb Log path: C:\logluns\log20 : C:\dbluns\db20\Jetstress020001.edb 25

Transactional Performance MSExchange ==> Instances Reads Latency (msec) Writes Latency (msec) Reads/sec Writes/sec Reads Bytes Writes Bytes Log Reads Latency (msec) Log Writes Latency (msec) Log Reads/sec Log Writes/sec Log Reads Bytes Log Writes Bytes Instance5488.1 15.495 1.470 14.360 10.076 36305.909 37120.907 0.000 0.735 0.000 9.517 0.000 4643.093 Instance5488.2 10.858 1.495 14.808 10.502 37654.575 37195.714 0.000 0.772 0.000 9.912 0.000 4676.016 Instance5488.3 10.433 1.424 14.113 9.732 37614.657 37165.251 0.000 0.807 0.000 9.356 0.000 4480.427 Instance5488.4 11.044 1.420 14.547 10.141 37317.834 36950.127 0.000 0.719 0.000 9.719 0.000 4481.508 Instance5488.5 10.656 1.379 14.336 9.867 37722.228 37203.478 0.000 0.741 0.000 9.435 0.000 4585.438 Instance5488.6 10.818 1.397 14.297 10.003 38063.919 37136.894 0.000 0.777 0.000 9.389 0.000 4685.973 Instance5488.7 11.171 1.307 14.464 10.167 39149.347 37113.689 0.000 0.758 0.000 9.611 0.000 4576.272 Instance5488.8 11.040 1.331 14.345 10.063 37411.303 37141.837 0.000 0.778 0.000 9.646 0.000 4683.351 Instance5488.9 10.885 1.261 14.433 10.040 37682.045 37023.231 0.000 0.780 0.000 9.551 0.000 4554.886 Instance5488.10 10.740 1.273 14.469 10.065 38132.410 37192.960 0.000 0.739 0.000 9.483 0.000 4592.795 Instance5488.11 10.870 1.340 14.346 9.906 37108.085 37197.752 0.000 0.749 0.000 9.351 0.000 4609.329 Instance5488.12 10.879 1.365 14.320 10.082 37749.139 37188.616 0.000 0.726 0.000 9.524 0.000 4576.843 Instance5488.13 10.822 1.280 14.192 9.903 37718.422 37323.400 0.000 0.761 0.000 9.250 0.000 4698.883 Instance5488.14 10.417 1.256 14.261 9.834 37899.316 37125.788 0.000 0.759 0.000 9.402 0.000 4636.277 Instance5488.15 11.132 1.237 14.468 10.017 37405.019 37100.686 0.000 0.734 0.000 9.476 0.000 4567.092 Instance5488.16 10.621 1.251 14.610 10.299 37959.004 36968.295 0.000 0.731 0.000 9.685 0.000 4477.333 Instance5488.17 10.811 1.193 14.571 10.281 37863.615 37343.813 0.000 0.751 0.000 9.598 0.000 4650.981 Instance5488.18 10.607 1.233 14.326 9.953 37374.143 37224.041 0.000 0.765 0.000 9.492 0.000 4639.481 Instance5488.19 11.134 1.164 14.727 10.215 37141.516 37070.902 0.000 0.724 0.000 9.724 0.000 4534.791 Instance5488.20 10.845 1.198 14.500 10.174 37134.008 37036.961 0.000 0.714 0.000 9.667 0.000 4564.235 26

Background Maintenance Performance MSExchange ==> Instances Maintenance IO Reads/sec Maintenance IO Reads Bytes Instance5488.1 32.935 261394.426 Instance5488.2 38.508 261277.811 Instance5488.3 38.839 261403.548 Instance5488.4 38.156 261345.415 Instance5488.5 38.449 261404.657 Instance5488.6 38.178 261415.785 Instance5488.7 37.951 259633.241 Instance5488.8 37.904 261281.372 Instance5488.9 38.072 261353.803 Instance5488.10 38.465 261340.374 Instance5488.11 38.167 261431.442 Instance5488.12 38.185 261278.796 Instance5488.13 38.245 261307.773 Instance5488.14 38.811 261352.776 Instance5488.15 37.981 261323.811 Instance5488.16 38.687 261305.415 Instance5488.17 38.270 261333.333 Instance5488.18 38.699 261319.501 Instance5488.19 37.859 261270.353 Instance5488.20 38.206 261269.252 27

Log Replication Performance MSExchange ==> Instances Log Reads/sec Log Reads Bytes Instance5488.1 0.178 69377.673 Instance5488.2 0.183 71805.873 Instance5488.3 0.169 66297.000 Instance5488.4 0.176 68829.819 Instance5488.5 0.172 66934.797 Instance5488.6 0.174 67911.948 Instance5488.7 0.173 69129.868 Instance5488.8 0.179 70340.147 Instance5488.9 0.172 67408.696 Instance5488.10 0.172 67003.399 Instance5488.11 0.172 66934.797 Instance5488.12 0.174 67911.948 Instance5488.13 0.172 67816.650 Instance5488.14 0.172 66934.797 Instance5488.15 0.173 67423.373 Instance5488.16 0.173 67423.373 Instance5488.17 0.179 70340.147 Instance5488.18 0.176 69777.616 Instance5488.19 0.177 68957.699 Instance5488.20 0.176 68400.523 28

Total Performance MSExchange ==> Instances Reads Latency (msec) Writes Latency (msec) Reads/sec Writes/sec Reads Bytes Writes Bytes Log Reads Latency (msec) Log Writes Latency (msec) Log Reads/sec Log Writes/sec Log Reads Bytes Log Writes Bytes Instance5488.1 15.495 1.470 47.294 10.076 193051.944 37120.907 3.069 0.735 0.178 9.517 69377.673 4643.093 Instance5488.2 10.858 1.495 53.316 10.502 199167.217 37195.714 3.747 0.772 0.183 9.912 71805.873 4676.016 Instance5488.3 10.433 1.424 52.952 9.732 201757.138 37165.251 3.410 0.807 0.169 9.356 66297.000 4480.427 Instance5488.4 11.044 1.420 52.703 10.141 199508.493 36950.127 3.266 0.719 0.176 9.719 68829.819 4481.508 Instance5488.5 10.656 1.379 52.786 9.867 200654.169 37203.478 3.253 0.741 0.172 9.435 66934.797 4585.438 Instance5488.6 10.818 1.397 52.475 10.003 200564.341 37136.894 3.374 0.777 0.174 9.389 67911.948 4685.973 Instance5488.7 11.171 1.307 52.415 10.167 198788.501 37113.689 3.991 0.758 0.173 9.611 69129.868 4576.272 Instance5488.8 11.040 1.331 52.249 10.063 199817.882 37141.837 3.744 0.778 0.179 9.646 70340.147 4683.351 Instance5488.9 10.885 1.261 52.505 10.040 199870.769 37023.231 3.403 0.780 0.172 9.551 67408.696 4554.886 Instance5488.10 10.740 1.273 52.935 10.065 200328.021 37192.960 3.367 0.739 0.172 9.483 67003.399 4592.795 Instance5488.11 10.870 1.340 52.513 9.906 200150.566 37197.752 3.083 0.749 0.172 9.351 66934.797 4609.329 Instance5488.12 10.879 1.365 52.504 10.082 200314.455 37188.616 3.473 0.726 0.174 9.524 67911.948 4576.843 Instance5488.13 10.822 1.280 52.436 9.903 200793.953 37323.400 3.666 0.761 0.172 9.250 67816.650 4698.883 Instance5488.14 10.417 1.256 53.073 9.834 201307.534 37125.788 3.254 0.759 0.172 9.402 66934.797 4636.277 Instance5488.15 11.132 1.237 52.449 10.017 199556.588 37100.686 3.496 0.734 0.173 9.476 67423.373 4567.092 Instance5488.16 10.621 1.251 53.297 10.299 200080.852 36968.295 3.542 0.731 0.173 9.685 67423.373 4477.333 Instance5488.17 10.811 1.193 52.841 10.281 199710.621 37343.813 3.507 0.751 0.179 9.598 70340.147 4650.981 Instance5488.18 10.607 1.233 53.025 9.953 200816.691 37224.041 3.572 0.765 0.176 9.492 69777.616 4639.481 Instance5488.19 11.134 1.164 52.585 10.215 198502.996 37070.902 3.961 0.724 0.177 9.724 68957.699 4534.791 Instance5488.20 10.845 1.198 52.707 10.174 199606.074 37036.961 3.657 0.714 0.176 9.667 68400.523 4564.235 29

Host System Performance Counter Minimum Maximum % Processor Time 1.511 0.000 2.936 Available MBytes 55973.658 55855.000 56462.000 Free System Page Table Entries 33555414.597 33555187.000 33555795.000 Transition Pages RePurposed/sec 0.000 0.000 0.000 Pool Nonpaged Bytes 92662159.296 92565504.000 93323264.000 Pool Paged Bytes 158935070.055 148660224.000 197251072.000 Page Fault Stalls/sec 0.000 0.000 0.000 Test Log8/24/2012 1:12:53 AM -- Jetstress testing begins... 8/24/2012 1:12:53 AM -- Preparing for testing... 8/24/2012 1:13:13 AM -- Attaching databases... 8/24/2012 1:13:13 AM -- Preparations for testing are complete. 8/24/2012 1:13:13 AM -- Starting transaction dispatch.. 8/24/2012 1:13:13 AM -- cache settings: (minimum: 640.0 MB, maximum: 5.0 GB) 8/24/2012 1:13:13 AM -- flush thresholds: (start: 51.2 MB, stop: 102.4 MB) 8/24/2012 1:13:38 AM -- read latency thresholds: (average: 20 msec/read, maximum: 100 msec/read). 8/24/2012 1:13:38 AM -- Log write latency thresholds: (average: 10 msec/write, maximum: 100 msec/write). 8/24/2012 1:13:55 AM -- Operation mix: Sessions 3, Inserts 40%, Deletes 20%, Replaces 5%, Reads 35%, Lazy Commits 70%. 8/24/2012 1:13:55 AM -- Performance logging started (interval: 15000 ms). 8/24/2012 1:13:55 AM -- Attaining prerequisites: 8/24/2012 1:26:59 AM -- \MSExchange (JetstressWin)\ Cache Size, Last: 4849402000.0 (lower bound: 4831838000.0, upper bound: none) 8/24/2012 3:26:59 AM -- Performance logging has ended. 8/24/2012 3:42:13 AM -- JetInterop batch transaction stats: 7538, 7605, 7392, 7549, 7428, 7479, 7547, 7438, 7351, 7470, 7321, 7469, 7391, 7435, 7534, 7589, 7499, 7434, 7522 and 7530. 8/24/2012 3:42:14 AM -- Dispatching transactions ends. 8/24/2012 3:42:14 AM -- Shutting down databases... 8/24/2012 3:44:35 AM -- Instance5488.1 (complete), Instance5488.2 (complete), Instance5488.3 (complete), Instance5488.4 (complete), Instance5488.5 (complete), Instance5488.6 (complete), Instance5488.7 (complete), Instance5488.8 (complete), Instance5488.9 (complete), Instance5488.10 (complete), Instance5488.11 (complete), Instance5488.12 (complete), Instance5488.13 (complete), Instance5488.14 (complete), Instance5488.15 (complete), Instance5488.16 (complete), Instance5488.17 (complete), Instance5488.18 (complete), Instance5488.19 (complete) and Instance5488.20 (complete) 8/24/2012 3:44:35 AM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R5_1GB_mbox_2600 Users\Performance Test\Performance_2012_8_24_1_13_38.blg has 529 samples. 8/24/2012 3:44:35 AM -- Creating test report... 30

8/24/2012 3:44:45 AM -- Instance5488.1 has 15.5 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.1 has 0.7 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.1 has 0.7 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.2 has 10.9 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.2 has 0.8 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.2 has 0.8 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.3 has 10.4 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.3 has 0.8 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.3 has 0.8 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.4 has 11.0 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.4 has 0.7 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.4 has 0.7 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.5 has 10.7 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.5 has 0.7 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.5 has 0.7 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.6 has 10.8 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.6 has 0.8 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.6 has 0.8 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.7 has 11.2 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.7 has 0.8 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.7 has 0.8 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.8 has 11.0 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.8 has 0.8 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.8 has 0.8 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.9 has 10.9 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.9 has 0.8 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.9 has 0.8 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.10 has 10.7 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.10 has 0.7 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.10 has 0.7 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.11 has 10.9 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.11 has 0.7 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.11 has 0.7 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.12 has 10.9 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.12 has 0.7 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.12 has 0.7 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.13 has 10.8 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.13 has 0.8 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.13 has 0.8 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.14 has 10.4 for Reads Latency. 31

8/24/2012 3:44:45 AM -- Instance5488.14 has 0.8 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.14 has 0.8 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.15 has 11.1 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.15 has 0.7 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.15 has 0.7 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.16 has 10.6 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.16 has 0.7 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.16 has 0.7 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.17 has 10.8 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.17 has 0.8 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.17 has 0.8 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.18 has 10.6 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.18 has 0.8 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.18 has 0.8 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.19 has 11.1 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.19 has 0.7 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.19 has 0.7 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.20 has 10.8 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.20 has 0.7 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.20 has 0.7 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Test has 0 Maximum Page Fault Stalls/sec. 8/24/2012 3:44:45 AM -- The test has 0 Page Fault Stalls/sec samples higher than 0. 8/24/2012 3:44:45 AM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R5_1GB_mbox_2600 Users\Performance Test\Performance_2012_8_24_1_13_38.xml has 476 samples queried. 32

Performance Test Checksums Result: CB10 Checksum Statistics - All Seen pages Bad pages Correctable pages Wrong page-number pages File length / seconds taken C:\dbluns\db1\Jetstress001001.edb 16404002 0 0 0 512625 MB/31178 sec C:\dbluns\db2\Jetstress002001.edb 16404002 0 0 0 512625 MB/30820 sec C:\dbluns\db3\Jetstress003001.edb 16403746 0 0 0 512617 MB/31108 sec C:\dbluns\db4\Jetstress004001.edb 16403746 0 0 0 512617 MB/30793 sec C:\dbluns\db5\Jetstress005001.edb 16403746 0 0 0 512617 MB/31084 sec C:\dbluns\db6\Jetstress006001.edb 16403746 0 0 0 512617 MB/30796 sec C:\dbluns\db7\Jetstress007001.edb 16403746 0 0 0 512617 MB/31139 sec C:\dbluns\db8\Jetstress008001.edb 16403746 0 0 0 512617 MB/30804 sec C:\dbluns\db9\Jetstress009001.edb 16403746 0 0 0 512617 MB/31113 sec C:\dbluns\db10\Jetstress010001.edb 16403490 0 0 0 512609 MB/30789 sec C:\dbluns\db11\Jetstress011001.edb 16403490 0 0 0 512609 MB/31158 sec C:\dbluns\db12\Jetstress012001.edb 16403746 0 0 0 512617 MB/30814 sec C:\dbluns\db13\Jetstress013001.edb 16403746 0 0 0 512617 MB/31117 sec C:\dbluns\db14\Jetstress014001.edb 16403746 0 0 0 512617 MB/30782 sec C:\dbluns\db15\Jetstress015001.edb 16404002 0 0 0 512625 MB/31051 sec C:\dbluns\db16\Jetstress016001.edb 16404002 0 0 0 512625 MB/30742 sec C:\dbluns\db17\Jetstress017001.edb 16404002 0 0 0 512625 MB/31119 sec C:\dbluns\db18\Jetstress018001.edb 16403490 0 0 0 512609 MB/30778 sec C:\dbluns\db19\Jetstress019001.edb 16403746 0 0 0 512617 MB/31095 sec C:\dbluns\db20\Jetstress020001.edb 16404002 0 0 0 512625 MB/30763 sec (Sum) 328075688 0 0 0 10252365 MB/31178 sec 33

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\db1 0.059 0.000 261.992 0.000 65536.000 C:\dbluns\db2 0.058 0.000 265.329 0.000 65536.000 C:\dbluns\db3 0.058 0.000 263.624 0.000 65536.000 C:\dbluns\db4 0.058 0.000 266.307 0.000 65536.000 C:\dbluns\db5 0.058 0.000 263.841 0.000 65536.000 C:\dbluns\db6 0.058 0.000 266.240 0.000 65536.000 C:\dbluns\db7 0.058 0.000 263.269 0.000 65536.000 C:\dbluns\db8 0.058 0.000 266.161 0.000 65536.000 C:\dbluns\db9 0.058 0.000 263.561 0.000 65536.000 C:\dbluns\db10 0.058 0.000 266.362 0.000 65536.000 C:\dbluns\db11 0.058 0.000 262.527 0.000 65536.000 C:\dbluns\db12 0.058 0.000 265.739 0.000 65536.000 C:\dbluns\db13 0.058 0.000 263.468 0.000 65536.000 C:\dbluns\db14 0.058 0.000 266.299 0.000 65536.000 C:\dbluns\db15 0.058 0.000 264.121 0.000 65536.000 C:\dbluns\db16 0.058 0.000 266.781 0.000 65536.000 C:\dbluns\db17 0.058 0.000 263.422 0.000 65536.000 C:\dbluns\db18 0.058 0.000 266.410 0.000 65536.000 C:\dbluns\db19 0.058 0.000 263.715 0.000 65536.000 C:\dbluns\db20 0.058 0.000 266.561 0.000 65536.000 34

Memory System Performance (of checksum) Counter Minimum Maximum % Processor Time 1.757 0.917 2.758 Available MBytes 61266.327 61236.000 61292.000 Free System Page Table Entries 33555411.334 33555279.000 33555795.000 Transition Pages RePurposed/sec 0.000 0.000 0.000 Pool Nonpaged Bytes 93269550.366 92893184.000 94457856.000 Pool Paged Bytes 149442962.497 149401600.000 150335488.000 Test Log8/24/2012 1:12:53 AM -- Jetstress testing begins... 8/24/2012 1:12:53 AM -- Preparing for testing... 8/24/2012 1:13:13 AM -- Attaching databases... 8/24/2012 1:13:13 AM -- Preparations for testing are complete. 8/24/2012 1:13:13 AM -- Starting transaction dispatch.. 8/24/2012 1:13:13 AM -- cache settings: (minimum: 640.0 MB, maximum: 5.0 GB) 8/24/2012 1:13:13 AM -- flush thresholds: (start: 51.2 MB, stop: 102.4 MB) 8/24/2012 1:13:38 AM -- read latency thresholds: (average: 20 msec/read, maximum: 100 msec/read). 8/24/2012 1:13:38 AM -- Log write latency thresholds: (average: 10 msec/write, maximum: 100 msec/write). 8/24/2012 1:13:55 AM -- Operation mix: Sessions 3, Inserts 40%, Deletes 20%, Replaces 5%, Reads 35%, Lazy Commits 70%. 8/24/2012 1:13:55 AM -- Performance logging started (interval: 15000 ms). 8/24/2012 1:13:55 AM -- Attaining prerequisites: 8/24/2012 1:26:59 AM -- \MSExchange (JetstressWin)\ Cache Size, Last: 4849402000.0 (lower bound: 4831838000.0, upper bound: none) 8/24/2012 3:26:59 AM -- Performance logging has ended. 8/24/2012 3:42:13 AM -- JetInterop batch transaction stats: 7538, 7605, 7392, 7549, 7428, 7479, 7547, 7438, 7351, 7470, 7321, 7469, 7391, 7435, 7534, 7589, 7499, 7434, 7522 and 7530. 8/24/2012 3:42:14 AM -- Dispatching transactions ends. 8/24/2012 3:42:14 AM -- Shutting down databases... 8/24/2012 3:44:35 AM -- Instance5488.1 (complete), Instance5488.2 (complete), Instance5488.3 (complete), Instance5488.4 (complete), Instance5488.5 (complete), Instance5488.6 (complete), Instance5488.7 (complete), Instance5488.8 (complete), Instance5488.9 (complete), Instance5488.10 (complete), Instance5488.11 (complete), Instance5488.12 (complete), Instance5488.13 (complete), Instance5488.14 (complete), Instance5488.15 (complete), Instance5488.16 (complete), Instance5488.17 (complete), Instance5488.18 (complete), Instance5488.19 (complete) and Instance5488.20 (complete) 8/24/2012 3:44:35 AM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R5_1GB_mbox_2600 Users\Performance Test\Performance_2012_8_24_1_13_38.blg has 529 samples. 8/24/2012 3:44:35 AM -- Creating test report... 8/24/2012 3:44:45 AM -- Instance5488.1 has 15.5 for Reads Latency. 35

8/24/2012 3:44:45 AM -- Instance5488.1 has 0.7 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.1 has 0.7 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.2 has 10.9 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.2 has 0.8 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.2 has 0.8 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.3 has 10.4 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.3 has 0.8 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.3 has 0.8 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.4 has 11.0 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.4 has 0.7 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.4 has 0.7 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.5 has 10.7 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.5 has 0.7 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.5 has 0.7 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.6 has 10.8 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.6 has 0.8 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.6 has 0.8 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.7 has 11.2 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.7 has 0.8 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.7 has 0.8 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.8 has 11.0 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.8 has 0.8 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.8 has 0.8 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.9 has 10.9 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.9 has 0.8 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.9 has 0.8 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.10 has 10.7 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.10 has 0.7 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.10 has 0.7 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.11 has 10.9 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.11 has 0.7 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.11 has 0.7 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.12 has 10.9 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.12 has 0.7 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.12 has 0.7 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.13 has 10.8 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.13 has 0.8 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.13 has 0.8 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.14 has 10.4 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.14 has 0.8 for Log Writes Latency. 36

8/24/2012 3:44:45 AM -- Instance5488.14 has 0.8 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.15 has 11.1 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.15 has 0.7 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.15 has 0.7 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.16 has 10.6 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.16 has 0.7 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.16 has 0.7 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.17 has 10.8 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.17 has 0.8 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.17 has 0.8 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.18 has 10.6 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.18 has 0.8 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.18 has 0.8 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.19 has 11.1 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.19 has 0.7 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.19 has 0.7 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.20 has 10.8 for Reads Latency. 8/24/2012 3:44:45 AM -- Instance5488.20 has 0.7 for Log Writes Latency. 8/24/2012 3:44:45 AM -- Instance5488.20 has 0.7 for Log Reads Latency. 8/24/2012 3:44:45 AM -- Test has 0 Maximum Page Fault Stalls/sec. 8/24/2012 3:44:45 AM -- The test has 0 Page Fault Stalls/sec samples higher than 0. 8/24/2012 3:44:45 AM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R5_1GB_mbox_2600 Users\Performance Test\Performance_2012_8_24_1_13_38.xml has 476 samples queried. 8/24/2012 3:44:46 AM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R5_1GB_mbox_2600 Users\Performance Test\Performance_2012_8_24_1_13_38.html was saved. 8/24/2012 3:44:47 AM -- Performance logging started (interval: 30000 ms). 8/24/2012 3:44:47 AM -- Verifying database checksums... 8/24/2012 12:24:25 PM -- C:\dbluns\db1 (100% processed), C:\dbluns\db2 (100% processed), C:\dbluns\db3 (100% processed), C:\dbluns\db4 (100% processed), C:\dbluns\db5 (100% processed), C:\dbluns\db6 (100% processed), C:\dbluns\db7 (100% processed), C:\dbluns\db8 (100% processed), C:\dbluns\db9 (100% processed), C:\dbluns\db10 (100% processed), C:\dbluns\db11 (100% processed), C:\dbluns\db12 (100% processed), C:\dbluns\db13 (100% processed), C:\dbluns\db14 (100% processed), C:\dbluns\db15 (100% processed), C:\dbluns\db16 (100% processed), C:\dbluns\db17 (100% processed), C:\dbluns\db18 (100% processed), C:\dbluns\db19 (100% processed) and C:\dbluns\db20 (100% processed) 8/24/2012 12:24:25 PM -- Performance logging has ended. 8/24/2012 12:24:25 PM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R5_1GB_mbox_2600 Users\Performance Test\DBChecksum_2012_8_24_3_44_46.blg has 1038 samples. 37

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 8/24/2012 5:03:51 PM 8/25/2012 6:33:09 PM 8/24/2012 5:17:52 PM 8/25/2012 5:17:45 PM 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_R5_1GB_mbox_2600 Users\Stress Test\Performance_2012_8_24_17_4_36.blg Sizing and Throughput Achieved Transactional per Second 492.206 Target Transactional per Second 312 Initial Size (bytes) 10750384144384 Final Size (bytes) 10771389218816 Files (Count) 20 38

Jetstress System Parameters Thread Count Minimum Cache Maximum Cache 3 (per database) 640.0 MB 5120.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 Configuration Instance5488.1 Instance5488.2 Instance5488.3 Instance5488.4 Instance5488.5 Instance5488.6 Instance5488.7 Instance5488.8 Instance5488.9 Instance5488.10 Log path: C:\logluns\log1 : C:\dbluns\db1\Jetstress001001.edb Log path: C:\logluns\log2 : C:\dbluns\db2\Jetstress002001.edb Log path: C:\logluns\log3 : C:\dbluns\db3\Jetstress003001.edb Log path: C:\logluns\log4 : C:\dbluns\db4\Jetstress004001.edb Log path: C:\logluns\log5 : C:\dbluns\db5\Jetstress005001.edb Log path: C:\logluns\log6 : C:\dbluns\db6\Jetstress006001.edb Log path: C:\logluns\log7 : C:\dbluns\db7\Jetstress007001.edb Log path: C:\logluns\log8 : C:\dbluns\db8\Jetstress008001.edb Log path: C:\logluns\log9 : C:\dbluns\db9\Jetstress009001.edb Log path: C:\logluns\log10 39

: C:\dbluns\db10\Jetstress010001.edb Instance5488.11 Instance5488.12 Instance5488.13 Instance5488.14 Instance5488.15 Instance5488.16 Instance5488.17 Instance5488.18 Instance5488.19 Instance5488.20 Log path: C:\logluns\log11 : C:\dbluns\db11\Jetstress011001.edb Log path: C:\logluns\log12 : C:\dbluns\db12\Jetstress012001.edb Log path: C:\logluns\log13 : C:\dbluns\db13\Jetstress013001.edb Log path: C:\logluns\log14 : C:\dbluns\db14\Jetstress014001.edb Log path: C:\logluns\log15 : C:\dbluns\db15\Jetstress015001.edb Log path: C:\logluns\log16 : C:\dbluns\db16\Jetstress016001.edb Log path: C:\logluns\log17 : C:\dbluns\db17\Jetstress017001.edb Log path: C:\logluns\log18 : C:\dbluns\db18\Jetstress018001.edb Log path: C:\logluns\log19 : C:\dbluns\db19\Jetstress019001.edb Log path: C:\logluns\log20 : C:\dbluns\db20\Jetstress020001.edb 40

Transactional Performance MSExchange ==> Instances Reads Latency (msec) Writes Latency (msec) Reads/sec Writes/sec Reads Bytes Writes Bytes Log Reads Latency (msec) Log Writes Latency (msec) Log Reads/sec Log Writes/sec Log Reads Bytes Log Writes Bytes Instance5488.1 13.402 1.494 14.415 10.135 36534.023 36607.975 0.000 0.730 0.000 9.323 0.000 4574.931 Instance5488.2 10.864 1.436 14.539 10.252 37672.599 36643.755 0.000 0.767 0.000 9.438 0.000 4603.047 Instance5488.3 10.894 1.445 14.372 10.111 37715.291 36646.273 0.000 0.731 0.000 9.339 0.000 4582.852 Instance5488.4 10.895 1.407 14.391 10.127 37429.279 36622.953 0.000 0.764 0.000 9.311 0.000 4622.529 Instance5488.5 10.857 1.414 14.409 10.142 37323.320 36642.353 0.000 0.719 0.000 9.376 0.000 4580.193 Instance5488.6 10.794 1.364 14.433 10.152 37728.583 36593.594 0.000 0.763 0.000 9.356 0.000 4578.146 Instance5488.7 10.817 1.358 14.443 10.179 37748.092 36632.594 0.000 0.722 0.000 9.346 0.000 4613.814 Instance5488.8 10.830 1.309 14.515 10.231 37592.840 36614.580 0.000 0.772 0.000 9.417 0.000 4581.040 Instance5488.9 10.826 1.283 14.509 10.208 37752.722 36641.027 0.000 0.738 0.000 9.383 0.000 4600.120 Instance5488.10 10.768 1.243 14.410 10.159 37680.628 36649.916 0.000 0.770 0.000 9.375 0.000 4607.643 Instance5488.11 10.910 1.369 14.458 10.173 37724.070 36614.476 0.000 0.738 0.000 9.340 0.000 4588.663 Instance5488.12 10.762 1.314 14.335 10.076 37846.119 36627.104 0.000 0.741 0.000 9.247 0.000 4605.994 Instance5488.13 10.853 1.321 14.355 10.102 37732.397 36557.702 0.000 0.742 0.000 9.321 0.000 4595.974 Instance5488.14 10.878 1.269 14.545 10.254 37628.974 36623.241 0.000 0.753 0.000 9.414 0.000 4584.066 Instance5488.15 11.072 1.274 14.433 10.168 37598.697 36637.982 0.000 0.744 0.000 9.359 0.000 4590.675 Instance5488.16 10.833 1.217 14.499 10.221 37708.080 36588.887 0.000 0.753 0.000 9.400 0.000 4573.650 Instance5488.17 10.880 1.219 14.431 10.162 37618.009 36612.073 0.000 0.735 0.000 9.367 0.000 4587.631 Instance5488.18 10.821 1.187 14.406 10.126 37429.201 36637.790 0.000 0.747 0.000 9.353 0.000 4568.842 Instance5488.19 10.966 1.195 14.512 10.235 37589.559 36599.883 0.000 0.728 0.000 9.389 0.000 4572.480 Instance5488.20 10.765 1.161 14.426 10.158 37572.433 36649.826 0.000 0.754 0.000 9.352 0.000 4592.704 41

Background Maintenance Performance MSExchange ==> Instances Maintenance IO Reads/sec Maintenance IO Reads Bytes Instance5488.1 35.534 261308.471 Instance5488.2 38.354 261319.851 Instance5488.3 38.287 261313.470 Instance5488.4 38.374 261310.774 Instance5488.5 38.370 261307.087 Instance5488.6 38.415 261317.786 Instance5488.7 38.407 261319.003 Instance5488.8 38.353 261292.517 Instance5488.9 38.357 261315.117 Instance5488.10 38.464 261328.870 Instance5488.11 38.257 261314.473 Instance5488.12 38.481 261323.294 Instance5488.13 38.322 261326.694 Instance5488.14 38.383 261296.232 Instance5488.15 38.092 261326.021 Instance5488.16 38.413 261303.544 Instance5488.17 38.295 261316.567 Instance5488.18 38.420 261302.746 Instance5488.19 38.106 261301.862 Instance5488.20 38.440 261283.585 42

Log Replication Performance MSExchange ==> Instances Log Reads/sec Log Reads Bytes Instance5488.1 0.170 66613.408 Instance5488.2 0.173 67542.759 Instance5488.3 0.170 66596.644 Instance5488.4 0.171 66751.502 Instance5488.5 0.172 66990.203 Instance5488.6 0.171 67072.465 Instance5488.7 0.171 66755.758 Instance5488.8 0.172 67260.105 Instance5488.9 0.172 67234.574 Instance5488.10 0.172 67049.886 Instance5488.11 0.171 66900.580 Instance5488.12 0.170 66342.495 Instance5488.13 0.170 66729.784 Instance5488.14 0.172 67385.729 Instance5488.15 0.171 66716.780 Instance5488.16 0.171 67050.992 Instance5488.17 0.171 67035.807 Instance5488.18 0.171 66800.753 Instance5488.19 0.172 67335.235 Instance5488.20 0.171 66825.782 43

Total Performance MSExchange ==> Instances Reads Latency (msec) Writes Latency (msec) Reads/sec Writes/sec Reads Bytes Writes Bytes Log Reads Latency (msec) Log Writes Latency (msec) Log Reads/sec Log Writes/sec Log Reads Bytes Log Writes Bytes Instance5488.1 13.402 1.494 49.949 10.135 196438.828 36607.975 3.669 0.730 0.170 9.323 66613.408 4574.931 Instance5488.2 10.864 1.436 52.892 10.252 199845.113 36643.755 3.719 0.767 0.173 9.438 67542.759 4603.047 Instance5488.3 10.894 1.445 52.659 10.111 200286.753 36646.273 3.511 0.731 0.170 9.339 66596.644 4582.852 Instance5488.4 10.895 1.407 52.765 10.127 200250.740 36622.953 3.719 0.764 0.171 9.311 66751.502 4622.529 Instance5488.5 10.857 1.414 52.779 10.142 200158.036 36642.353 3.614 0.719 0.172 9.376 66990.203 4580.193 Instance5488.6 10.794 1.364 52.848 10.152 200255.514 36593.594 3.925 0.763 0.171 9.356 67072.465 4578.146 Instance5488.7 10.817 1.358 52.850 10.179 200221.607 36632.594 3.463 0.722 0.171 9.346 66755.758 4613.814 Instance5488.8 10.830 1.309 52.868 10.231 199874.754 36614.580 3.819 0.772 0.172 9.417 67260.105 4581.040 Instance5488.9 10.826 1.283 52.865 10.208 199958.913 36641.027 3.620 0.738 0.172 9.383 67234.574 4600.120 Instance5488.10 10.768 1.243 52.874 10.159 200376.433 36649.916 3.350 0.770 0.172 9.375 67049.886 4607.643 Instance5488.11 10.910 1.369 52.716 10.173 199990.515 36614.476 3.667 0.738 0.171 9.340 66900.580 4588.663 Instance5488.12 10.762 1.314 52.816 10.076 200669.651 36627.104 3.424 0.741 0.170 9.247 66342.495 4605.994 Instance5488.13 10.853 1.321 52.676 10.102 200395.468 36557.702 3.654 0.742 0.170 9.321 66729.784 4595.974 Instance5488.14 10.878 1.269 52.929 10.254 199830.547 36623.241 3.891 0.753 0.172 9.414 67385.729 4584.066 Instance5488.15 11.072 1.274 52.525 10.168 199848.725 36637.982 3.625 0.744 0.171 9.359 66716.780 4590.675 Instance5488.16 10.833 1.217 52.912 10.221 200033.014 36588.887 3.638 0.753 0.171 9.400 67050.992 4573.650 Instance5488.17 10.880 1.219 52.726 10.162 200091.293 36612.073 3.698 0.735 0.171 9.367 67035.807 4587.631 Instance5488.18 10.821 1.187 52.826 10.126 200250.828 36637.790 3.566 0.747 0.171 9.353 66800.753 4568.842 Instance5488.19 10.966 1.195 52.618 10.235 199601.806 36599.883 3.593 0.728 0.172 9.389 67335.235 4572.480 Instance5488.20 10.765 1.161 52.866 10.158 200237.046 36649.826 3.560 0.754 0.171 9.352 66825.782 4592.704 44

Host System Performance Counter Minimum Maximum % Processor Time 1.470 0.000 3.342 Available MBytes 55884.932 55777.000 56472.000 Free System Page Table Entries 33555373.656 33555278.000 33555795.000 Transition Pages RePurposed/sec 0.000 0.000 0.000 Pool Nonpaged Bytes 92607924.357 92577792.000 92721152.000 Pool Paged Bytes 150296892.863 149504000.000 152424448.000 Page Fault Stalls/sec 0.000 0.000 0.000 Test Log8/24/2012 5:03:51 PM -- Jetstress testing begins... 8/24/2012 5:03:51 PM -- Preparing for testing... 8/24/2012 5:04:11 PM -- Attaching databases... 8/24/2012 5:04:11 PM -- Preparations for testing are complete. 8/24/2012 5:04:11 PM -- Starting transaction dispatch.. 8/24/2012 5:04:11 PM -- cache settings: (minimum: 640.0 MB, maximum: 5.0 GB) 8/24/2012 5:04:11 PM -- flush thresholds: (start: 51.2 MB, stop: 102.4 MB) 8/24/2012 5:04:36 PM -- read latency thresholds: (average: 20 msec/read, maximum: 100 msec/read). 8/24/2012 5:04:36 PM -- Log write latency thresholds: (average: 10 msec/write, maximum: 100 msec/write). 8/24/2012 5:04:52 PM -- Operation mix: Sessions 3, Inserts 40%, Deletes 20%, Replaces 5%, Reads 35%, Lazy Commits 70%. 8/24/2012 5:04:52 PM -- Performance logging started (interval: 15000 ms). 8/24/2012 5:04:52 PM -- Attaining prerequisites: 8/24/2012 5:17:52 PM -- \MSExchange (JetstressWin)\ Cache Size, Last: 4845699000.0 (lower bound: 4831838000.0, upper bound: none) 8/25/2012 5:17:52 PM -- Performance logging has ended. 8/25/2012 6:31:10 PM -- JetInterop batch transaction stats: 74860, 75592, 74802, 75032, 74976, 75175, 75170, 75359, 75429, 75492, 75318, 74829, 74739, 75657, 75068, 75293, 74888, 74847, 75445 and 75323. 8/25/2012 6:31:11 PM -- Dispatching transactions ends. 8/25/2012 6:31:11 PM -- Shutting down databases... 8/25/2012 6:33:09 PM -- Instance5488.1 (complete), Instance5488.2 (complete), Instance5488.3 (complete), Instance5488.4 (complete), Instance5488.5 (complete), Instance5488.6 (complete), Instance5488.7 (complete), Instance5488.8 (complete), Instance5488.9 (complete), Instance5488.10 (complete), Instance5488.11 (complete), Instance5488.12 (complete), Instance5488.13 (complete), Instance5488.14 (complete), Instance5488.15 (complete), Instance5488.16 (complete), Instance5488.17 (complete), Instance5488.18 (complete), Instance5488.19 (complete) and Instance5488.20 (complete) 8/25/2012 6:33:09 PM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R5_1GB_mbox_2600 Users\Stress Test\Performance_2012_8_24_17_4_36.blg has 5784 samples. 8/25/2012 6:33:09 PM -- Creating test report... 45

8/25/2012 6:35:01 PM -- Instance5488.1 has 13.4 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.1 has 0.7 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.1 has 0.7 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.2 has 10.9 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.2 has 0.8 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.2 has 0.8 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.3 has 10.9 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.3 has 0.7 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.3 has 0.7 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.4 has 10.9 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.4 has 0.8 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.4 has 0.8 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.5 has 10.9 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.5 has 0.7 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.5 has 0.7 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.6 has 10.8 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.6 has 0.8 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.6 has 0.8 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.7 has 10.8 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.7 has 0.7 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.7 has 0.7 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.8 has 10.8 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.8 has 0.8 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.8 has 0.8 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.9 has 10.8 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.9 has 0.7 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.9 has 0.7 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.10 has 10.8 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.10 has 0.8 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.10 has 0.8 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.11 has 10.9 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.11 has 0.7 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.11 has 0.7 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.12 has 10.8 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.12 has 0.7 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.12 has 0.7 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.13 has 10.9 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.13 has 0.7 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.13 has 0.7 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.14 has 10.9 for Reads Latency. 46

8/25/2012 6:35:01 PM -- Instance5488.14 has 0.8 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.14 has 0.8 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.15 has 11.1 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.15 has 0.7 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.15 has 0.7 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.16 has 10.8 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.16 has 0.8 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.16 has 0.8 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.17 has 10.9 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.17 has 0.7 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.17 has 0.7 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.18 has 10.8 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.18 has 0.7 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.18 has 0.7 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.19 has 11.0 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.19 has 0.7 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.19 has 0.7 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.20 has 10.8 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.20 has 0.8 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.20 has 0.8 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Test has 0 Maximum Page Fault Stalls/sec. 8/25/2012 6:35:01 PM -- The test has 0 Page Fault Stalls/sec samples higher than 0. 8/25/2012 6:35:01 PM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R5_1GB_mbox_2600 Users\Stress Test\Performance_2012_8_24_17_4_36.xml has 5732 samples queried. 47

Stress Test Checksums Result: CB10 Checksum Statistics - All Seen pages Bad pages Correctable pages Wrong page-number pages File length / seconds taken C:\dbluns\db1\Jetstress001001.edb 16435746 0 0 0 513617 MB/31151 sec C:\dbluns\db2\Jetstress002001.edb 16436258 0 0 0 513633 MB/30756 sec C:\dbluns\db3\Jetstress003001.edb 16435490 0 0 0 513609 MB/31037 sec C:\dbluns\db4\Jetstress004001.edb 16435746 0 0 0 513617 MB/30702 sec C:\dbluns\db5\Jetstress005001.edb 16435746 0 0 0 513617 MB/31016 sec C:\dbluns\db6\Jetstress006001.edb 16435746 0 0 0 513617 MB/30714 sec C:\dbluns\db7\Jetstress007001.edb 16435746 0 0 0 513617 MB/31079 sec C:\dbluns\db8\Jetstress008001.edb 16436258 0 0 0 513633 MB/30746 sec C:\dbluns\db9\Jetstress009001.edb 16435746 0 0 0 513617 MB/31069 sec C:\dbluns\db10\Jetstress010001.edb 16435746 0 0 0 513617 MB/30658 sec C:\dbluns\db11\Jetstress011001.edb 16435490 0 0 0 513609 MB/31109 sec C:\dbluns\db12\Jetstress012001.edb 16435746 0 0 0 513617 MB/30736 sec C:\dbluns\db13\Jetstress013001.edb 16435746 0 0 0 513617 MB/30988 sec C:\dbluns\db14\Jetstress014001.edb 16436002 0 0 0 513625 MB/30692 sec C:\dbluns\db15\Jetstress015001.edb 16436002 0 0 0 513625 MB/30999 sec C:\dbluns\db16\Jetstress016001.edb 16436002 0 0 0 513625 MB/30587 sec C:\dbluns\db17\Jetstress017001.edb 16436002 0 0 0 513625 MB/31041 sec C:\dbluns\db18\Jetstress018001.edb 16435490 0 0 0 513609 MB/30726 sec C:\dbluns\db19\Jetstress019001.edb 16435746 0 0 0 513617 MB/31071 sec C:\dbluns\db20\Jetstress020001.edb 16436258 0 0 0 513633 MB/30675 sec (Sum) 328716712 0 0 0 10272397 MB/31152 sec 48

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\db1 0.059 0.000 262.182 0.000 65536.000 C:\dbluns\db2 0.058 0.000 266.418 0.000 65536.000 C:\dbluns\db3 0.058 0.000 264.167 0.000 65536.000 C:\dbluns\db4 0.058 0.000 267.057 0.000 65536.000 C:\dbluns\db5 0.058 0.000 264.391 0.000 65536.000 C:\dbluns\db6 0.058 0.000 266.976 0.000 65536.000 C:\dbluns\db7 0.058 0.000 263.794 0.000 65536.000 C:\dbluns\db8 0.058 0.000 266.777 0.000 65536.000 C:\dbluns\db9 0.058 0.000 263.909 0.000 65536.000 C:\dbluns\db10 0.057 0.000 267.417 0.000 65536.000 C:\dbluns\db11 0.058 0.000 263.354 0.000 65536.000 C:\dbluns\db12 0.058 0.000 266.585 0.000 65536.000 C:\dbluns\db13 0.058 0.000 264.574 0.000 65536.000 C:\dbluns\db14 0.058 0.000 267.174 0.000 65536.000 C:\dbluns\db15 0.058 0.000 264.531 0.000 65536.000 C:\dbluns\db16 0.057 0.000 268.054 0.000 65536.000 C:\dbluns\db17 0.058 0.000 264.198 0.000 65536.000 C:\dbluns\db18 0.058 0.000 266.846 0.000 65536.000 C:\dbluns\db19 0.058 0.000 263.936 0.000 65536.000 C:\dbluns\db20 0.057 0.000 267.380 0.000 65536.000 49

Memory System Performance (of checksum) Counter Minimum Maximum % Processor Time 1.754 0.769 2.660 Available MBytes 61049.862 61034.000 61078.000 Free System Page Table Entries 33555559.646 33555279.000 33555795.000 Transition Pages RePurposed/sec 0.000 0.000 0.000 Pool Nonpaged Bytes 93282726.635 92856320.000 94453760.000 Pool Paged Bytes 158929211.988 158412800.000 160088064.000 Test Log8/24/2012 5:03:51 PM -- Jetstress testing begins... 8/24/2012 5:03:51 PM -- Preparing for testing... 8/24/2012 5:04:11 PM -- Attaching databases... 8/24/2012 5:04:11 PM -- Preparations for testing are complete. 8/24/2012 5:04:11 PM -- Starting transaction dispatch.. 8/24/2012 5:04:11 PM -- cache settings: (minimum: 640.0 MB, maximum: 5.0 GB) 8/24/2012 5:04:11 PM -- flush thresholds: (start: 51.2 MB, stop: 102.4 MB) 8/24/2012 5:04:36 PM -- read latency thresholds: (average: 20 msec/read, maximum: 100 msec/read). 8/24/2012 5:04:36 PM -- Log write latency thresholds: (average: 10 msec/write, maximum: 100 msec/write). 8/24/2012 5:04:52 PM -- Operation mix: Sessions 3, Inserts 40%, Deletes 20%, Replaces 5%, Reads 35%, Lazy Commits 70%. 8/24/2012 5:04:52 PM -- Performance logging started (interval: 15000 ms). 8/24/2012 5:04:52 PM -- Attaining prerequisites: 8/24/2012 5:17:52 PM -- \MSExchange (JetstressWin)\ Cache Size, Last: 4845699000.0 (lower bound: 4831838000.0, upper bound: none) 8/25/2012 5:17:52 PM -- Performance logging has ended. 8/25/2012 6:31:10 PM -- JetInterop batch transaction stats: 74860, 75592, 74802, 75032, 74976, 75175, 75170, 75359, 75429, 75492, 75318, 74829, 74739, 75657, 75068, 75293, 74888, 74847, 75445 and 75323. 8/25/2012 6:31:11 PM -- Dispatching transactions ends. 8/25/2012 6:31:11 PM -- Shutting down databases... 8/25/2012 6:33:09 PM -- Instance5488.1 (complete), Instance5488.2 (complete), Instance5488.3 (complete), Instance5488.4 (complete), Instance5488.5 (complete), Instance5488.6 (complete), Instance5488.7 (complete), Instance5488.8 (complete), Instance5488.9 (complete), Instance5488.10 (complete), Instance5488.11 (complete), Instance5488.12 (complete), Instance5488.13 (complete), Instance5488.14 (complete), Instance5488.15 (complete), Instance5488.16 (complete), Instance5488.17 (complete), Instance5488.18 (complete), Instance5488.19 (complete) and Instance5488.20 (complete) 8/25/2012 6:33:09 PM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R5_1GB_mbox_2600 Users\Stress Test\Performance_2012_8_24_17_4_36.blg has 5784 samples. 8/25/2012 6:33:09 PM -- Creating test report... 8/25/2012 6:35:01 PM -- Instance5488.1 has 13.4 for Reads Latency. 50

8/25/2012 6:35:01 PM -- Instance5488.1 has 0.7 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.1 has 0.7 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.2 has 10.9 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.2 has 0.8 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.2 has 0.8 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.3 has 10.9 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.3 has 0.7 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.3 has 0.7 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.4 has 10.9 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.4 has 0.8 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.4 has 0.8 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.5 has 10.9 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.5 has 0.7 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.5 has 0.7 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.6 has 10.8 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.6 has 0.8 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.6 has 0.8 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.7 has 10.8 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.7 has 0.7 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.7 has 0.7 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.8 has 10.8 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.8 has 0.8 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.8 has 0.8 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.9 has 10.8 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.9 has 0.7 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.9 has 0.7 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.10 has 10.8 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.10 has 0.8 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.10 has 0.8 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.11 has 10.9 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.11 has 0.7 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.11 has 0.7 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.12 has 10.8 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.12 has 0.7 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.12 has 0.7 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.13 has 10.9 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.13 has 0.7 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.13 has 0.7 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.14 has 10.9 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.14 has 0.8 for Log Writes Latency. 51

8/25/2012 6:35:01 PM -- Instance5488.14 has 0.8 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.15 has 11.1 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.15 has 0.7 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.15 has 0.7 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.16 has 10.8 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.16 has 0.8 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.16 has 0.8 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.17 has 10.9 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.17 has 0.7 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.17 has 0.7 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.18 has 10.8 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.18 has 0.7 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.18 has 0.7 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.19 has 11.0 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.19 has 0.7 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.19 has 0.7 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.20 has 10.8 for Reads Latency. 8/25/2012 6:35:01 PM -- Instance5488.20 has 0.8 for Log Writes Latency. 8/25/2012 6:35:01 PM -- Instance5488.20 has 0.8 for Log Reads Latency. 8/25/2012 6:35:01 PM -- Test has 0 Maximum Page Fault Stalls/sec. 8/25/2012 6:35:01 PM -- The test has 0 Page Fault Stalls/sec samples higher than 0. 8/25/2012 6:35:01 PM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R5_1GB_mbox_2600 Users\Stress Test\Performance_2012_8_24_17_4_36.xml has 5732 samples queried. 8/25/2012 6:35:01 PM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R5_1GB_mbox_2600 Users\Stress Test\Performance_2012_8_24_17_4_36.html was saved. 8/25/2012 6:35:02 PM -- Performance logging started (interval: 30000 ms). 8/25/2012 6:35:02 PM -- Verifying database checksums... 8/26/2012 3:14:14 AM -- C:\dbluns\db1 (100% processed), C:\dbluns\db2 (100% processed), C:\dbluns\db3 (100% processed), C:\dbluns\db4 (100% processed), C:\dbluns\db5 (100% processed), C:\dbluns\db6 (100% processed), C:\dbluns\db7 (100% processed), C:\dbluns\db8 (100% processed), C:\dbluns\db9 (100% processed), C:\dbluns\db10 (100% processed), C:\dbluns\db11 (100% processed), C:\dbluns\db12 (100% processed), C:\dbluns\db13 (100% processed), C:\dbluns\db14 (100% processed), C:\dbluns\db15 (100% processed), C:\dbluns\db16 (100% processed), C:\dbluns\db17 (100% processed), C:\dbluns\db18 (100% processed), C:\dbluns\db19 (100% processed) and C:\dbluns\db20 (100% processed) 8/26/2012 3:14:14 AM -- Performance logging has ended. 8/26/2012 3:14:14 AM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R5_1GB_mbox_2600 Users\Stress Test\DBChecksum_2012_8_25_18_35_1.blg has 1037 samples. 52

Backup Test Result: CB10 Backup Statistics - All Instance Size (MBytes) Elapsed Backup Time MBytes Transferred/sec Instance5488.1 513609.09 07:47:08 18.32 Instance5488.2 513625.09 06:57:58 20.48 Instance5488.3 513601.09 07:17:54 19.55 Instance5488.4 513609.09 07:02:35 20.26 Instance5488.5 513609.09 07:16:50 19.60 Instance5488.6 513609.09 07:01:33 20.31 Instance5488.7 513609.09 07:22:10 19.36 Instance5488.8 513625.09 06:58:20 20.46 Instance5488.9 513609.09 07:14:05 19.72 Instance5488.10 513609.09 06:58:45 20.44 Instance5488.11 513601.09 07:21:07 19.41 Instance5488.12 513609.09 06:58:29 20.45 Instance5488.13 513609.09 07:31:15 18.97 Instance5488.14 513617.09 07:01:02 20.33 Instance5488.15 513617.09 07:17:28 19.57 Instance5488.16 513617.09 07:20:11 19.45 Instance5488.17 513617.09 07:16:30 19.61 Instance5488.18 513601.09 07:22:22 19.35 Instance5488.19 513609.09 07:15:31 19.65 Instance5488.20 513625.09 06:59:32 20.40 53

Jetstress System Parameters Thread Count Minimum Cache Maximum Cache 3 (per database) 640.0 MB 5120.0 MB Insert Operations 40% Delete Operations 20% Replace Operations 5% Read Operations 35% Lazy Commits 70% Configuration Instance5488.1 Instance5488.2 Instance5488.3 Instance5488.4 Instance5488.5 Instance5488.6 Instance5488.7 Instance5488.8 Instance5488.9 Instance5488.10 Instance5488.11 Log path: C:\logluns\log1 : C:\dbluns\db1\Jetstress001001.edb Log path: C:\logluns\log2 : C:\dbluns\db2\Jetstress002001.edb Log path: C:\logluns\log3 : C:\dbluns\db3\Jetstress003001.edb Log path: C:\logluns\log4 : C:\dbluns\db4\Jetstress004001.edb Log path: C:\logluns\log5 : C:\dbluns\db5\Jetstress005001.edb Log path: C:\logluns\log6 : C:\dbluns\db6\Jetstress006001.edb Log path: C:\logluns\log7 : C:\dbluns\db7\Jetstress007001.edb Log path: C:\logluns\log8 : C:\dbluns\db8\Jetstress008001.edb Log path: C:\logluns\log9 : C:\dbluns\db9\Jetstress009001.edb Log path: C:\logluns\log10 : C:\dbluns\db10\Jetstress010001.edb Log path: C:\logluns\log11 : C:\dbluns\db11\Jetstress011001.edb 54

Instance5488.12 Instance5488.13 Instance5488.14 Instance5488.15 Instance5488.16 Instance5488.17 Instance5488.18 Instance5488.19 Instance5488.20 Log path: C:\logluns\log12 : C:\dbluns\db12\Jetstress012001.edb Log path: C:\logluns\log13 : C:\dbluns\db13\Jetstress013001.edb Log path: C:\logluns\log14 : C:\dbluns\db14\Jetstress014001.edb Log path: C:\logluns\log15 : C:\dbluns\db15\Jetstress015001.edb Log path: C:\logluns\log16 : C:\dbluns\db16\Jetstress016001.edb Log path: C:\logluns\log17 : C:\dbluns\db17\Jetstress017001.edb Log path: C:\logluns\log18 : C:\dbluns\db18\Jetstress018001.edb Log path: C:\logluns\log19 : C:\dbluns\db19\Jetstress019001.edb Log path: C:\logluns\log20 : C:\dbluns\db20\Jetstress020001.edb 55

Transactional Performance MSExchange ==> Instances Reads Latency (msec) Writes Latency (msec) Reads/sec Writes/sec Reads Bytes Writes Bytes Log Reads Latency (msec) Log Writes Latency (msec) Log Reads/sec Log Writes/sec Log Reads Bytes Log Writes Bytes Instance5488.1 374.752 0.000 72.110 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 Instance5488.2 180.077 0.000 81.142 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 Instance5488.3 189.792 0.000 78.087 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 Instance5488.4 176.831 0.000 80.905 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 Instance5488.5 190.366 0.000 78.249 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 Instance5488.6 183.462 0.000 80.723 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 Instance5488.7 201.298 0.000 77.246 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 Instance5488.8 181.247 0.000 81.622 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 Instance5488.9 189.372 0.000 78.079 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 Instance5488.10 178.300 0.000 81.430 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 Instance5488.11 199.633 0.000 77.194 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 Instance5488.12 180.143 0.000 81.263 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 Instance5488.13 229.557 0.000 75.694 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 Instance5488.14 176.619 0.000 81.254 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 Instance5488.15 189.260 0.000 78.065 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 Instance5488.16 214.856 0.000 77.763 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 Instance5488.17 190.863 0.000 77.838 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 Instance5488.18 222.722 0.000 77.135 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 Instance5488.19 187.175 0.000 78.119 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 Instance5488.20 179.666 0.000 80.992 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 56

Host System Performance Counter Minimum Maximum % Processor Time 1.122 0.000 2.649 Available MBytes 61049.624 61033.000 61053.000 Free System Page Table Entries 33555400.462 33555279.000 33555795.000 Transition Pages RePurposed/sec 0.000 0.000 0.000 Pool Nonpaged Bytes 92685505.373 92667904.000 92770304.000 Pool Paged Bytes 159258404.258 159068160.000 161017856.000 Page Fault Stalls/sec 0.000 0.000 0.000 Test Log8/26/2012 9:49:35 AM -- Jetstress testing begins... 8/26/2012 9:49:35 AM -- Preparing for testing... 8/26/2012 9:49:55 AM -- Attaching databases... 8/26/2012 9:49:55 AM -- Preparations for testing are complete. 8/26/2012 9:50:23 AM -- Performance logging started (interval: 30000 ms). 8/26/2012 9:50:23 AM -- Backing up databases... 8/26/2012 5:37:32 PM -- Performance logging has ended. 8/26/2012 5:37:32 PM -- Instance5488.1 (100% processed), Instance5488.2 (100% processed), Instance5488.3 (100% processed), Instance5488.4 (100% processed), Instance5488.5 (100% processed), Instance5488.6 (100% processed), Instance5488.7 (100% processed), Instance5488.8 (100% processed), Instance5488.9 (100% processed), Instance5488.10 (100% processed), Instance5488.11 (100% processed), Instance5488.12 (100% processed), Instance5488.13 (100% processed), Instance5488.14 (100% processed), Instance5488.15 (100% processed), Instance5488.16 (100% processed), Instance5488.17 (100% processed), Instance5488.18 (100% processed), Instance5488.19 (100% processed) and Instance5488.20 (100% processed) 8/26/2012 5:37:32 PM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R5_1GB_mbox_2600 Users\ Backup\Backup_2012_8_26_9_49_55.blg has 932 samples. 8/26/2012 5:37:32 PM -- Creating test report... 57

Soft Recovery Test Result: CB10 Soft-Recovery Statistics - All Instance Log files replayed Elapsed seconds Instance5488.1 512 2312.5312692 Instance5488.2 513 2236.282908 Instance5488.3 510 2342.6249905 Instance5488.4 507 2305.0048387 Instance5488.5 507 2237.0369512 Instance5488.6 512 2259.1082136 Instance5488.7 523 2263.1214431 Instance5488.8 510 2238.5400371 Instance5488.9 510 2232.2706785 Instance5488.10 501 2228.7564775 Instance5488.11 518 2254.5919553 Instance5488.12 509 2227.2533916 Instance5488.13 506 2254.0919267 Instance5488.14 504 2337.8597179 Instance5488.15 502 2289.2079352 Instance5488.16 509 2232.2706785 Instance5488.17 506 2205.686158 Instance5488.18 511 2229.009492 Instance5488.19 516 2234.026779 Instance5488.20 510 2218.4758895 58

Configuration Instance5488.1 Instance5488.2 Instance5488.3 Instance5488.4 Instance5488.5 Instance5488.6 Instance5488.7 Instance5488.8 Instance5488.9 Instance5488.10 Instance5488.11 Instance5488.12 Instance5488.13 Instance5488.14 Instance5488.15 Instance5488.16 Instance5488.17 Instance5488.18 Log path: C:\logluns\log1 : C:\dbluns\db1\Jetstress001001.edb Log path: C:\logluns\log2 : C:\dbluns\db2\Jetstress002001.edb Log path: C:\logluns\log3 : C:\dbluns\db3\Jetstress003001.edb Log path: C:\logluns\log4 : C:\dbluns\db4\Jetstress004001.edb Log path: C:\logluns\log5 : C:\dbluns\db5\Jetstress005001.edb Log path: C:\logluns\log6 : C:\dbluns\db6\Jetstress006001.edb Log path: C:\logluns\log7 : C:\dbluns\db7\Jetstress007001.edb Log path: C:\logluns\log8 : C:\dbluns\db8\Jetstress008001.edb Log path: C:\logluns\log9 : C:\dbluns\db9\Jetstress009001.edb Log path: C:\logluns\log10 : C:\dbluns\db10\Jetstress010001.edb Log path: C:\logluns\log11 : C:\dbluns\db11\Jetstress011001.edb Log path: C:\logluns\log12 : C:\dbluns\db12\Jetstress012001.edb Log path: C:\logluns\log13 : C:\dbluns\db13\Jetstress013001.edb Log path: C:\logluns\log14 : C:\dbluns\db14\Jetstress014001.edb Log path: C:\logluns\log15 : C:\dbluns\db15\Jetstress015001.edb Log path: C:\logluns\log16 : C:\dbluns\db16\Jetstress016001.edb Log path: C:\logluns\log17 : C:\dbluns\db17\Jetstress017001.edb Log path: C:\logluns\log18 59

: C:\dbluns\db18\Jetstress018001.edb Instance5488.19 Instance5488.20 Log path: C:\logluns\log19 : C:\dbluns\db19\Jetstress019001.edb Log path: C:\logluns\log20 : C:\dbluns\db20\Jetstress020001.edb 60

Transactional Performance MSExchange ==> Instances Reads Latency (msec) Writes Latency (msec) Reads/sec Writes/sec Reads Bytes Writes Bytes Log Reads Latency (msec) Log Writes Latency (msec) Log Reads/sec Log Writes/sec Log Reads Bytes Log Writes Bytes Instance5488.1 29.834 0.671 118.893 1.322 41105.352 27594.105 4.611 0.000 1.985 0.000 195460.622 0.000 Instance5488.2 29.105 0.717 121.124 1.375 39750.339 29497.147 5.580 0.001 2.062 0.001 208391.616 0.929 Instance5488.3 29.886 0.638 116.230 1.298 42904.450 26521.068 4.390 0.000 1.947 0.000 187365.639 0.000 Instance5488.4 29.577 0.665 117.270 1.313 41301.523 27806.648 5.317 0.000 1.970 0.000 196789.423 0.000 Instance5488.5 29.108 0.695 121.496 1.356 39684.178 28961.917 4.629 0.000 2.034 0.000 204221.019 0.000 Instance5488.6 28.867 0.710 120.767 1.357 40387.369 28944.086 5.671 0.001 2.036 0.001 205352.306 0.919 Instance5488.7 28.646 0.758 122.132 1.384 40300.551 29185.835 4.617 0.001 2.076 0.001 205691.078 0.918 Instance5488.8 29.144 0.731 121.518 1.364 40131.179 29265.623 5.509 0.001 2.047 0.001 207187.007 0.928 Instance5488.9 28.890 0.722 121.272 1.367 39709.941 29074.153 4.663 0.000 2.050 0.000 204979.941 0.000 Instance5488.10 29.317 0.708 120.955 1.345 39922.801 29007.738 5.494 0.000 2.017 0.000 205006.558 0.000 Instance5488.11 28.933 0.703 120.998 1.376 40012.887 29114.014 4.608 0.001 2.064 0.001 205315.380 0.921 Instance5488.12 29.182 0.710 121.494 1.369 40089.722 29306.171 5.773 0.001 2.054 0.001 207519.308 0.933 Instance5488.13 29.090 0.706 121.349 1.345 40234.466 28937.209 4.738 0.001 2.020 0.006 205477.254 0.921 Instance5488.14 29.847 0.639 114.352 1.287 42954.372 26339.556 4.936 0.000 1.931 0.000 186443.417 0.000 Instance5488.15 29.869 0.656 115.256 1.309 41322.727 27364.766 4.503 0.000 1.964 0.000 193231.163 0.000 Instance5488.16 28.415 0.703 120.679 1.364 39894.851 28954.996 5.448 0.000 2.046 0.000 204869.956 0.000 Instance5488.17 28.983 0.677 122.513 1.373 40204.759 28905.842 4.944 0.000 2.060 0.000 204961.528 0.000 Instance5488.18 29.410 0.701 120.871 1.374 39940.626 29127.111 5.629 0.001 2.062 0.001 206561.321 0.933 Instance5488.19 29.138 0.705 121.284 1.383 39702.974 29669.935 4.847 0.000 2.074 0.000 209786.415 0.000 Instance5488.20 28.813 0.703 120.071 1.377 39952.013 29233.609 5.444 0.000 2.065 0.001 206350.826 0.936 61

Background Maintenance Performance MSExchange ==> Instances Maintenance IO Reads/sec Maintenance IO Reads Bytes Instance5488.1 29.959 261541.031 Instance5488.2 29.864 261474.554 Instance5488.3 29.452 261566.299 Instance5488.4 29.538 261494.420 Instance5488.5 30.116 261352.765 Instance5488.6 30.387 261472.569 Instance5488.7 30.703 261553.854 Instance5488.8 29.676 261455.058 Instance5488.9 30.764 261595.717 Instance5488.10 29.500 261439.663 Instance5488.11 30.086 261484.042 Instance5488.12 29.313 261480.456 Instance5488.13 29.903 261340.317 Instance5488.14 29.621 261548.310 Instance5488.15 29.117 261538.718 Instance5488.16 32.034 261551.754 Instance5488.17 30.364 261395.574 Instance5488.18 28.798 261416.275 Instance5488.19 29.620 261370.135 Instance5488.20 30.602 261520.891 62

Total Performance MSExchange ==> Instances Reads Latency (msec) Writes Latency (msec) Reads/sec Writes/sec Reads Bytes Writes Bytes Log Reads Latency (msec) Log Writes Latency (msec) Log Reads/sec Log Writes/sec Log Reads Bytes Log Writes Bytes Instance5488.1 29.834 0.671 148.852 1.322 85472.000 27594.105 4.611 0.000 1.985 0.000 195460.622 0.000 Instance5488.2 29.105 0.717 150.988 1.375 83605.593 29497.147 5.580 0.001 2.062 0.001 208391.616 0.929 Instance5488.3 29.886 0.638 145.682 1.298 87109.903 26521.068 4.390 0.000 1.947 0.000 187365.639 0.000 Instance5488.4 29.577 0.665 146.808 1.313 85604.165 27806.648 5.317 0.000 1.970 0.000 196789.423 0.000 Instance5488.5 29.108 0.695 151.611 1.356 83716.015 28961.917 4.629 0.000 2.034 0.000 204221.019 0.000 Instance5488.6 28.867 0.710 151.154 1.357 84832.780 28944.086 5.671 0.001 2.036 0.001 205352.306 0.919 Instance5488.7 28.646 0.758 152.836 1.384 84748.289 29185.835 4.617 0.001 2.076 0.001 205691.078 0.918 Instance5488.8 29.144 0.731 151.194 1.364 83571.738 29265.623 5.509 0.001 2.047 0.001 207187.007 0.928 Instance5488.9 28.890 0.722 152.036 1.367 84607.992 29074.153 4.663 0.000 2.050 0.000 204979.941 0.000 Instance5488.10 29.317 0.708 150.455 1.345 83356.100 29007.738 5.494 0.000 2.017 0.000 205006.558 0.000 Instance5488.11 28.933 0.703 151.084 1.376 84115.335 29114.014 4.608 0.001 2.064 0.001 205315.380 0.921 Instance5488.12 29.182 0.710 150.807 1.369 83121.874 29306.171 5.773 0.001 2.054 0.001 207519.308 0.933 Instance5488.13 29.090 0.706 151.252 1.345 83947.476 28937.209 4.738 0.001 2.020 0.006 205477.254 0.921 Instance5488.14 29.847 0.639 143.973 1.287 87928.490 26339.556 4.936 0.000 1.931 0.000 186443.417 0.000 Instance5488.15 29.869 0.656 144.373 1.309 85735.264 27364.766 4.503 0.000 1.964 0.000 193231.163 0.000 Instance5488.16 28.415 0.703 152.713 1.364 86391.007 28954.996 5.448 0.000 2.046 0.000 204869.956 0.000 Instance5488.17 28.983 0.677 152.877 1.373 84137.024 28905.842 4.944 0.000 2.060 0.000 204961.528 0.000 Instance5488.18 29.410 0.701 149.669 1.374 82554.943 29127.111 5.629 0.001 2.062 0.001 206561.321 0.933 Instance5488.19 29.138 0.705 150.904 1.383 83212.923 29669.935 4.847 0.000 2.074 0.000 209786.415 0.000 Instance5488.20 28.813 0.703 150.672 1.377 84952.786 29233.609 5.444 0.000 2.065 0.001 206350.826 0.936 63

Host System Performance Counter Minimum Maximum % Processor Time 1.816 0.000 8.288 Available MBytes 55886.818 55748.000 60327.000 Free System Page Table Entries 33555285.644 33555281.000 33555795.000 Transition Pages RePurposed/sec 0.000 0.000 0.000 Pool Nonpaged Bytes 93651099.903 93388800.000 94351360.000 Pool Paged Bytes 161939293.010 161845248.000 161996800.000 Page Fault Stalls/sec 0.000 0.000 0.000 Test Log8/26/2012 8:41:30 PM -- Jetstress testing begins... 8/26/2012 8:41:30 PM -- Preparing for testing... 8/26/2012 8:41:51 PM -- Attaching databases... 8/26/2012 8:41:51 PM -- Preparations for testing are complete. 8/26/2012 8:41:51 PM -- Starting transaction dispatch.. 8/26/2012 8:41:51 PM -- cache settings: (minimum: 640.0 MB, maximum: 5.0 GB) 8/26/2012 8:41:51 PM -- flush thresholds: (start: 51.2 MB, stop: 102.4 MB) 8/26/2012 8:42:14 PM -- read latency thresholds: (average: 20 msec/read, maximum: 100 msec/read). 8/26/2012 8:42:14 PM -- Log write latency thresholds: (average: 10 msec/write, maximum: 100 msec/write). 8/26/2012 8:42:22 PM -- Operation mix: Sessions 3, Inserts 40%, Deletes 20%, Replaces 5%, Reads 35%, Lazy Commits 70%. 8/26/2012 8:42:22 PM -- Performance logging started (interval: 15000 ms). 8/26/2012 8:42:22 PM -- Generating log files... 8/27/2012 3:03:22 AM -- C:\logluns\log1 (102.4% generated), C:\logluns\log2 (102.6% generated), C:\logluns\log3 (102.0% generated), C:\logluns\log4 (101.2% generated), C:\logluns\log5 (101.4% generated), C:\logluns\log6 (102.4% generated), C:\logluns\log7 (104.6% generated), C:\logluns\log8 (102.0% generated), C:\logluns\log9 (102.0% generated), C:\logluns\log10 (100.2% generated), C:\logluns\log11 (103.6% generated), C:\logluns\log12 (101.8% generated), C:\logluns\log13 (101.2% generated), C:\logluns\log14 (100.8% generated), C:\logluns\log15 (100.4% generated), C:\logluns\log16 (101.8% generated), C:\logluns\log17 (101.2% generated), C:\logluns\log18 (102.2% generated), C:\logluns\log19 (103.2% generated) and C:\logluns\log20 (102.0% generated) 8/27/2012 3:03:23 AM -- Performance logging has ended. 8/27/2012 3:03:23 AM -- JetInterop batch transaction stats: 22556, 22276, 22168, 22011, 22150, 22250, 22513, 22087, 22121, 22043, 22394, 22054, 22184, 22096, 21728, 21972, 22161, 22045, 22221 and 21966. 8/27/2012 3:03:23 AM -- Dispatching transactions ends. 8/27/2012 3:03:23 AM -- Shutting down databases... 8/27/2012 3:03:59 AM -- Instance5488.1 (complete), Instance5488.2 (complete), Instance5488.3 (complete), Instance5488.4 (complete), Instance5488.5 (complete), Instance5488.6 (complete), Instance5488.7 (complete), Instance5488.8 (complete), Instance5488.9 (complete), Instance5488.10 (complete), Instance5488.11 (complete), Instance5488.12 (complete), Instance5488.13 (complete), Instance5488.14 (complete), Instance5488.15 (complete), Instance5488.16 (complete), Instance5488.17 (complete), 64

Instance5488.18 (complete), Instance5488.19 (complete) and Instance5488.20 (complete) 8/27/2012 3:03:59 AM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R5_1GB_mbox_2600 Users\Soft Recovery\Performance_2012_8_26_20_42_14.blg has 1519 samples. 8/27/2012 3:03:59 AM -- Creating test report... 8/27/2012 3:04:13 AM -- Instance5488.1 has 22.2 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.1 has 0.7 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.1 has 0.7 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.2 has 19.7 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.2 has 0.6 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.2 has 0.6 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.3 has 19.9 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.3 has 0.7 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.3 has 0.7 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.4 has 19.9 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.4 has 0.6 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.4 has 0.6 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.5 has 19.7 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.5 has 0.7 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.5 has 0.7 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.6 has 19.6 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.6 has 0.6 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.6 has 0.6 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.7 has 19.6 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.7 has 0.7 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.7 has 0.7 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.8 has 19.7 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.8 has 0.7 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.8 has 0.7 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.9 has 19.5 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.9 has 0.7 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.9 has 0.7 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.10 has 19.8 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.10 has 0.6 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.10 has 0.6 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.11 has 19.7 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.11 has 0.6 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.11 has 0.6 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.12 has 19.6 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.12 has 0.6 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.12 has 0.6 for Log Reads Latency. 65

8/27/2012 3:04:13 AM -- Instance5488.13 has 19.7 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.13 has 0.6 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.13 has 0.6 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.14 has 19.8 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.14 has 0.6 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.14 has 0.6 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.15 has 19.7 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.15 has 0.6 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.15 has 0.6 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.16 has 19.7 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.16 has 0.6 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.16 has 0.6 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.17 has 19.7 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.17 has 0.6 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.17 has 0.6 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.18 has 19.5 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.18 has 0.6 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.18 has 0.6 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.19 has 19.6 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.19 has 0.7 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.19 has 0.7 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.20 has 19.7 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.20 has 0.6 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.20 has 0.6 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Test has 0 Maximum Page Fault Stalls/sec. 8/27/2012 3:04:13 AM -- The test has 0 Page Fault Stalls/sec samples higher than 0. 8/27/2012 3:04:13 AM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R5_1GB_mbox_2600 Users\Soft Recovery\Performance_2012_8_26_20_42_14.xml has 1518 samples queried. 8/27/2012 3:04:13 AM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R5_1GB_mbox_2600 Users\Soft Recovery\Performance_2012_8_26_20_42_14.html was saved. 8/27/2012 3:07:59 AM -- Performance logging started (interval: 4000 ms). 8/27/2012 3:07:59 AM -- Recovering databases... 8/27/2012 3:47:01 AM -- Performance logging has ended. 8/27/2012 3:47:01 AM -- Instance5488.1 (2312.5312692), Instance5488.2 (2236.282908), Instance5488.3 (2342.6249905), Instance5488.4 (2305.0048387), Instance5488.5 (2237.0369512), Instance5488.6 (2259.1082136), Instance5488.7 (2263.1214431), Instance5488.8 (2238.5400371), Instance5488.9 (2232.2706785), Instance5488.10 (2228.7564775), Instance5488.11 (2254.5919553), Instance5488.12 (2227.2533916), Instance5488.13 (2254.0919267), Instance5488.14 (2337.8597179), Instance5488.15 (2289.2079352), Instance5488.16 (2232.2706785), Instance5488.17 (2205.686158), Instance5488.18 (2229.009492), Instance5488.19 (2234.026779) and Instance5488.20 (2218.4758895) 8/27/2012 3:47:02 AM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R5_1GB_mbox_2600 Users\Soft 66

Recovery\SoftRecovery_2012_8_27_3_7_50.blg has 578 samples. 8/27/2012 3:47:02 AM -- Creating test report... Soft Recovery Test Performance Result: CB10 Test Summary Overall Test Result Machine Name Fail CB10 Test Description Test Start Time Test End Time Collection Start Time Collection End Time 8/26/2012 8:41:30 PM 8/27/2012 3:03:59 AM 8/26/2012 8:42:37 PM 8/27/2012 3:03:20 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_R5_1GB_mbox_2600 Users\Soft Recovery\Performance_2012_8_26_20_42_14.blg Test Issues Fail The process has average database read latencies higher than 20.000 msec. Sizing and Throughput Achieved Transactional per Second 586.654 Capacity Percentage 100% Throughput Percentage 100% Initial Size (bytes) 10771389218816 Final Size (bytes) 10777580011520 Files (Count) 20 67

Jetstress System Parameters Thread Count Minimum Cache Maximum Cache 3 (per database) 640.0 MB 5120.0 MB Insert Operations 40% Delete Operations 20% Replace Operations 5% Read Operations 35% Lazy Commits 70% Configuration Instance5488.1 Instance5488.2 Instance5488.3 Instance5488.4 Instance5488.5 Instance5488.6 Instance5488.7 Instance5488.8 Instance5488.9 Instance5488.10 Log path: C:\logluns\log1 : C:\dbluns\db1\Jetstress001001.edb Log path: C:\logluns\log2 : C:\dbluns\db2\Jetstress002001.edb Log path: C:\logluns\log3 : C:\dbluns\db3\Jetstress003001.edb Log path: C:\logluns\log4 : C:\dbluns\db4\Jetstress004001.edb Log path: C:\logluns\log5 : C:\dbluns\db5\Jetstress005001.edb Log path: C:\logluns\log6 : C:\dbluns\db6\Jetstress006001.edb Log path: C:\logluns\log7 : C:\dbluns\db7\Jetstress007001.edb Log path: C:\logluns\log8 : C:\dbluns\db8\Jetstress008001.edb Log path: C:\logluns\log9 : C:\dbluns\db9\Jetstress009001.edb Log path: C:\logluns\log10 : C:\dbluns\db10\Jetstress010001.edb 68

Instance5488.11 Instance5488.12 Instance5488.13 Instance5488.14 Instance5488.15 Instance5488.16 Instance5488.17 Instance5488.18 Instance5488.19 Instance5488.20 Log path: C:\logluns\log11 : C:\dbluns\db11\Jetstress011001.edb Log path: C:\logluns\log12 : C:\dbluns\db12\Jetstress012001.edb Log path: C:\logluns\log13 : C:\dbluns\db13\Jetstress013001.edb Log path: C:\logluns\log14 : C:\dbluns\db14\Jetstress014001.edb Log path: C:\logluns\log15 : C:\dbluns\db15\Jetstress015001.edb Log path: C:\logluns\log16 : C:\dbluns\db16\Jetstress016001.edb Log path: C:\logluns\log17 : C:\dbluns\db17\Jetstress017001.edb Log path: C:\logluns\log18 : C:\dbluns\db18\Jetstress018001.edb Log path: C:\logluns\log19 : C:\dbluns\db19\Jetstress019001.edb Log path: C:\logluns\log20 : C:\dbluns\db20\Jetstress020001.edb 69

Transactional Performance MSExchange ==> Instances Reads Latency (msec) Writes Latency (msec) Reads/sec Writes/sec Reads Bytes Writes Bytes Log Reads Latency (msec) Log Writes Latency (msec) Log Reads/sec Log Writes/sec Log Reads Bytes Log Writes Bytes Instance5488.1 22.206 4.882 17.548 12.226 32768.000 36251.788 0.000 0.665 0.000 11.101 0.000 4528.097 Instance5488.2 19.699 4.838 17.282 11.997 32768.000 36338.209 0.000 0.631 0.000 11.024 0.000 4546.719 Instance5488.3 19.908 4.764 17.508 12.118 32768.000 36265.583 0.000 0.682 0.000 11.012 0.000 4540.391 Instance5488.4 19.910 4.734 17.318 12.000 32768.000 36243.927 0.000 0.610 0.000 10.916 0.000 4531.959 Instance5488.5 19.665 4.661 17.359 12.061 32768.000 36270.869 0.000 0.652 0.000 10.929 0.000 4534.389 Instance5488.6 19.629 4.605 17.412 12.099 32768.000 36276.702 0.000 0.626 0.000 11.008 0.000 4551.830 Instance5488.7 19.619 4.461 17.557 12.254 32768.000 36200.161 0.000 0.666 0.000 11.209 0.000 4573.515 Instance5488.8 19.665 4.394 17.372 12.057 32768.000 36155.390 0.000 0.657 0.000 10.985 0.000 4545.309 Instance5488.9 19.527 4.160 17.305 11.996 32768.000 36290.301 0.000 0.654 0.000 10.954 0.000 4540.885 Instance5488.10 19.758 4.199 17.274 11.946 32768.000 36234.121 0.000 0.609 0.000 10.821 0.000 4538.861 Instance5488.11 19.685 4.535 17.394 12.107 32768.000 36285.788 0.000 0.650 0.000 11.103 0.000 4561.881 Instance5488.12 19.646 4.514 17.275 11.990 32768.000 36280.578 0.000 0.617 0.000 10.935 0.000 4557.968 Instance5488.13 19.704 4.396 17.496 12.131 32768.000 36145.275 0.000 0.649 0.000 10.921 0.000 4518.749 Instance5488.14 19.811 4.374 17.171 11.904 32746.414 36152.048 0.000 0.584 0.000 10.829 0.000 4528.602 Instance5488.15 19.677 4.346 16.977 11.701 32768.000 36279.864 0.000 0.630 0.000 10.739 0.000 4584.479 Instance5488.16 19.661 4.468 17.256 11.936 32768.000 36286.018 0.000 0.626 0.000 10.911 0.000 4563.247 Instance5488.17 19.727 4.576 17.291 12.018 32768.000 36140.538 0.000 0.642 0.000 10.856 0.000 4564.207 Instance5488.18 19.544 4.583 17.211 11.931 32768.000 36316.683 0.000 0.612 0.000 11.022 0.000 4608.314 Instance5488.19 19.553 4.710 17.304 12.012 32768.000 36365.169 0.000 0.670 0.000 10.960 0.000 4623.849 Instance5488.20 19.652 4.699 17.042 11.819 32768.000 36233.656 0.000 0.601 0.000 10.851 0.000 4633.973 70

Host System Performance Counter Minimum Maximum % Processor Time 1.217 0.000 3.503 Available MBytes 55865.491 55726.000 60584.000 Free System Page Table Entries 33555443.701 33555279.000 33555795.000 Transition Pages RePurposed/sec 0.000 0.000 0.000 Pool Nonpaged Bytes 92665156.255 92651520.000 92770304.000 Pool Paged Bytes 160411650.697 159830016.000 201351168.000 Page Fault Stalls/sec 0.000 0.000 0.000 Test Log8/26/2012 8:41:30 PM -- Jetstress testing begins... 8/26/2012 8:41:30 PM -- Preparing for testing... 8/26/2012 8:41:51 PM -- Attaching databases... 8/26/2012 8:41:51 PM -- Preparations for testing are complete. 8/26/2012 8:41:51 PM -- Starting transaction dispatch.. 8/26/2012 8:41:51 PM -- cache settings: (minimum: 640.0 MB, maximum: 5.0 GB) 8/26/2012 8:41:51 PM -- flush thresholds: (start: 51.2 MB, stop: 102.4 MB) 8/26/2012 8:42:14 PM -- read latency thresholds: (average: 20 msec/read, maximum: 100 msec/read). 8/26/2012 8:42:14 PM -- Log write latency thresholds: (average: 10 msec/write, maximum: 100 msec/write). 8/26/2012 8:42:22 PM -- Operation mix: Sessions 3, Inserts 40%, Deletes 20%, Replaces 5%, Reads 35%, Lazy Commits 70%. 8/26/2012 8:42:22 PM -- Performance logging started (interval: 15000 ms). 8/26/2012 8:42:22 PM -- Generating log files... 8/27/2012 3:03:22 AM -- C:\logluns\log1 (102.4% generated), C:\logluns\log2 (102.6% generated), C:\logluns\log3 (102.0% generated), C:\logluns\log4 (101.2% generated), C:\logluns\log5 (101.4% generated), C:\logluns\log6 (102.4% generated), C:\logluns\log7 (104.6% generated), C:\logluns\log8 (102.0% generated), C:\logluns\log9 (102.0% generated), C:\logluns\log10 (100.2% generated), C:\logluns\log11 (103.6% generated), C:\logluns\log12 (101.8% generated), C:\logluns\log13 (101.2% generated), C:\logluns\log14 (100.8% generated), C:\logluns\log15 (100.4% generated), C:\logluns\log16 (101.8% generated), C:\logluns\log17 (101.2% generated), C:\logluns\log18 (102.2% generated), C:\logluns\log19 (103.2% generated) and C:\logluns\log20 (102.0% generated) 8/27/2012 3:03:23 AM -- Performance logging has ended. 8/27/2012 3:03:23 AM -- JetInterop batch transaction stats: 22556, 22276, 22168, 22011, 22150, 22250, 22513, 22087, 22121, 22043, 22394, 22054, 22184, 22096, 21728, 21972, 22161, 22045, 22221 and 21966. 8/27/2012 3:03:23 AM -- Dispatching transactions ends. 8/27/2012 3:03:23 AM -- Shutting down databases... 8/27/2012 3:03:59 AM -- Instance5488.1 (complete), Instance5488.2 (complete), Instance5488.3 (complete), Instance5488.4 (complete), Instance5488.5 (complete), Instance5488.6 (complete), Instance5488.7 (complete), Instance5488.8 (complete), Instance5488.9 (complete), Instance5488.10 (complete), Instance5488.11 (complete), Instance5488.12 (complete), Instance5488.13 (complete), Instance5488.14 (complete), Instance5488.15 (complete), Instance5488.16 (complete), Instance5488.17 (complete), 71

Instance5488.18 (complete), Instance5488.19 (complete) and Instance5488.20 (complete) 8/27/2012 3:03:59 AM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R5_1GB_mbox_2600 Users\Soft Recovery\Performance_2012_8_26_20_42_14.blg has 1519 samples. 8/27/2012 3:03:59 AM -- Creating test report... 8/27/2012 3:04:13 AM -- Instance5488.1 has 22.2 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.1 has 0.7 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.1 has 0.7 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.2 has 19.7 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.2 has 0.6 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.2 has 0.6 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.3 has 19.9 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.3 has 0.7 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.3 has 0.7 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.4 has 19.9 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.4 has 0.6 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.4 has 0.6 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.5 has 19.7 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.5 has 0.7 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.5 has 0.7 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.6 has 19.6 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.6 has 0.6 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.6 has 0.6 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.7 has 19.6 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.7 has 0.7 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.7 has 0.7 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.8 has 19.7 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.8 has 0.7 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.8 has 0.7 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.9 has 19.5 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.9 has 0.7 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.9 has 0.7 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.10 has 19.8 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.10 has 0.6 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.10 has 0.6 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.11 has 19.7 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.11 has 0.6 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.11 has 0.6 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.12 has 19.6 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.12 has 0.6 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.12 has 0.6 for Log Reads Latency. 72

8/27/2012 3:04:13 AM -- Instance5488.13 has 19.7 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.13 has 0.6 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.13 has 0.6 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.14 has 19.8 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.14 has 0.6 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.14 has 0.6 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.15 has 19.7 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.15 has 0.6 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.15 has 0.6 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.16 has 19.7 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.16 has 0.6 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.16 has 0.6 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.17 has 19.7 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.17 has 0.6 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.17 has 0.6 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.18 has 19.5 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.18 has 0.6 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.18 has 0.6 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.19 has 19.6 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.19 has 0.7 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.19 has 0.7 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.20 has 19.7 for Reads Latency. 8/27/2012 3:04:13 AM -- Instance5488.20 has 0.6 for Log Writes Latency. 8/27/2012 3:04:13 AM -- Instance5488.20 has 0.6 for Log Reads Latency. 8/27/2012 3:04:13 AM -- Test has 0 Maximum Page Fault Stalls/sec. 8/27/2012 3:04:13 AM -- The test has 0 Page Fault Stalls/sec samples higher than 0. 8/27/2012 3:04:13 AM -- C:\HUS110_PE108_C1B1_SAS7K_ESRP_R5_1GB_mbox_2600 Users\Soft Recovery\Performance_2012_8_26_20_42_14.xml has 1518 samples queried. 73

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-085-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 74