HP D2600 disk enclosure and HP Smart Array P411 2,000 user 4 GB mailbox resiliency Exchange 2010 storage solution

Transcription

1 Technical white paper HP D2600 disk enclosure and HP Smart Array P411 2,000 user 4 GB mailbox resiliency Exchange 2010 storage solution Table of contents Overview 2 Disclaimer 2 Features of the tested solution 2 HP D2000 disk enclosure family 2 Solution description 3 Storage configuration 4 Targeted customer profile 6 Tested deployment 6 Best practices 8 Test results summary 8 Conclusion 10 Appendix A Test reports 11 2 hour test hour test 13 backup test 15 Soft recovery test 16 For more information 18

2 Overview This solution brief provides information on an HP D2600 disk enclosure and HP Smart Array P411 storage solution for Microsoft Exchange Server 2010 (Exchange), based on the Microsoft Exchange Solution Review Program (ESRP) Storage Program. The ESRP Storage Program was developed by Microsoft Corporation to provide a common storage testing framework for vendors to provide information on their storage solutions for Microsoft Exchange Server software. For more details on the Microsoft ESRP V3.0 Storage Program, please see: Tested with: ESRP Storage Version 3.0 Test Date: June 2012 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. Features of the tested solution This solution implements the Availability Group (DAG) mailbox resiliency features in Exchange Server The DAG architecture allows two or more mailbox servers (up to 16) to be grouped together for increased database availability. Mailbox servers participating in the DAG manage mailbox database replications and configuration of database copies. DAG members also monitor database operations and in the event of a database, server, storage or network failure, can initiate an automatic database-level recovery, by activating a (passive) database copy on another server. This solution brief describes a tested configuration for deploying Microsoft Exchange Server 2010 (Exchange) in a 2,000 user mailbox resiliency environment. The performance results and best practices outlined in this document provide tested guidelines for configuring Exchange using the HP D2600 disk enclosure, HP Smart Array P411 controller and ProLiant DL360 G7 servers in a direct attached storage (DAS) configuration. For this solution, a single DAG was designed for supporting 2,000 mailboxes. The mailboxes were 4 GB in size and evenly distributed across 6 active databases. To provide mailbox resiliency, there are two copies of each database (active and passive). The active and passive database copies are hosted on separate server and storage configurations. With no server failures, each server hosts 3 active databases. With one of the servers offline (due to hardware failure, maintenance, power outage, etc.), the other server would host 6 active databases. This solution was tested with all active mailbox databases on one server, simulating the worst case scenario. The HP D2000 disk enclosure family offers affordable, modular and flexible storage, as detailed below. HP D2000 disk enclosure family Manage your small and midrange business growing storage needs by deploying the HP D2000 disk enclosures, the next generation 6Gb SAS low-cost, flexible, and tiered external storage system. The HP D2000 disk enclosures are ideal for small application environments in small and medium businesses, remote offices and departmental locations. The 6Gb SAS enclosures Large Form Factor (LFF) D2600 with 12 drive bays and Small Form Factor (SFF) D2700 with 25 drive bays offer modular solutions to simplify capacity expansion of HP ProLiant and Integrity server environments to external storage without having to make the full move to SAN or NAS. HP MSA storage (SFF only) can also be expanded with the D2700. This allows you to buy what is needed today and purchase additional capacity as data storage needs grow. 2

3 Affordable storage HP D2000 disk enclosures double the transfer rate of current 3Gb solutions, adding crucial bandwidth. The HP D2000 disk enclosures modular platform allows customers to purchase based on current need and future growth, no hidden management charges. Ability to add enterprise-class dual-port SAS drives as the need and budget dictates Affordable redundancy and reliability, reducing or eliminating single points of failure within the storage network. Flexible and scalable Flexibility to mix and match SAS and SATA drives in the same enclosure. Extends benefit of tiered storage to direct attach customers. Solid State drives supported in the D2700. The D2600 LFF can grow up to 96 drives. Up to four Large Form Factor (LFF) enclosures can be connected together from a single controller port. The D2700 SFF can grow up to 200 drives. Up to four Small Form Factor (SFF) enclosures can be connected together from a single controller port. Easy to manage The HP D2000 disk enclosures use familiar HP ProLiant management tools including HP Systems Insight Manager and the HP Array Configuration Utility (ACU) software. The HP D2000 disk enclosures are compatible with selected HP Smart Array SAS controllers. Little IT expertise is required. Solution description This solution brief provides tested best practices to help administrators implement the Exchange deployment, with the following criteria: 2,000 users total, with (2) mailbox servers 0.24 IOPS per user (0.2 with additional 20% headroom included) 4 GB tested mailbox size Availability Group (DAG) deployment with 2 copies of each database in the DAG 6 databases total on each server (3 active and 3 passive) during normal operations background maintenance (DBM) configured during testing Storage in this solution is deployed as RAID 1 pairs. See the Storage configuration section for more information. HP has developed the HP Sizer for Microsoft Exchange Server 2010 to assist customers with proper server and storage sizing for their Exchange Server 2010 deployments. The algorithms developed and implemented in this tool are based upon extensive testing of Exchange Server 2010 server roles and technologies, HP s deep experience with Microsoft Exchange, and intricate knowledge of server CPU, memory and subsystems. This tool is free to download and use, and is designed to simplify configuration across a broad range of deployments. For more information, please visit: hp.com/solutions/microsoft/exchange2010/sizer 3

4 Figure 1 below illustrates the tested solution hardware. Each server in this solution utilizes all (12) 3TB MDL SAS Disks for database, logs and content indexing all on the same volumes. Recovery space (often referred as the restore LUN) can be provided using drives within the server. Figure 1: Rack mounted view of the hardware used in this solution 1 6G DP 15k SAS 146 GB 5 1 6G DP 15k SAS 146 GB 2 6G DP 15k SAS 146 GB 3 6G DP 15k SAS 146 GB 8 4 UID SID HP ProLiant DL360 G7 HP StorageWorks D UID 1. Host (DL360 G7) 2. Storage (D2600) Storage configuration In this solution, the D2600 disk enclosure is attached to a Smart Array P411 controller and configured using the HP Array Configuration Utility (ACU). The Smart Array P411 controller manages RAID configuration and LUN ownership. For storage performance and redundancy, the D2600 and P411 are cabled as a dual-domain configuration. The dual-domain configuration uses two independent SAS data paths from the servers to the storage. The dual-domain communication path prevents disk from being interrupted in the event of a single data path failure. For more detail on implementing a dual-domain configuration with the D2600, please see: Figure 2 below illustrates the dual-domain configuration used in this solution. Figure 2: Dual-Domain Configuration 1 Smart Array P411 ilo UID PLC B 1200W 94% TOP PLC B 1200W 94% UID 2 3 PS 1 A Mfg P1 P2 UID Attention This module fits 3.5" large form factor drives only. PS 2 1 B 4 Mfg P1 P2 UID Attention This module fits 3.5" large form factor drives only Host (DL360 G7) 2. Storage (D2600) 3. Primary Path 4. Alternate Path The disk layout containing the mailbox databases and logs were created using RAID 1. Each RAID 1 disk group consisted of (2) 3 TB disks, for a total of (6) RAID groups. Since Exchange was configured for multiple database copies, the databases and logs resided on the same volumes. 4

5 Figures 3 and 4 below show how the active mailbox databases would be distributed during normal and failed operations in order to maintain production. This solution was tested will all active mailbox databases on one server, simulating the worst case scenario. Figure 3: Primary Data Center with (2) Member DAG Normal Operation Active MBX1 DAG1 MBX2 Passive DB1 DB2 DB3 DB4 DB5 DB6 DB1 DB2 DB3 DB4 DB5 DB6 Figure 4: Primary Data Center with (2) Member DAG MBX2 Offline Due to Fault Active MBX1 DAG1 MBX2 Passive DB1 DB2 DB3 DB4 DB5 DB6 DB1 DB2 DB3 DB4 DB5 DB6 5

6 Targeted customer profile This solution brief provides tested best practices to help administrators implement the Exchange deployment, with the following criteria: 2000 users total, with (2) active Exchange servers and two (2) database copies 0.24 IOPS per user (0.2 with additional 20% headroom) 4 GB tested mailbox size Availability Group (DAG) deployment with 2 copies of each database in the DAG 6 databases total on each server (3 active and 3 passive) during normal operations background maintenance (DBM) configured during testing Tested deployment The following table summarizes the testing environment. Simulated Exchange configuration Number of Exchange mailboxes simulated 2000 Number of Availability Groups (DAGs) 1 Number of mailbox servers/dag 2 Number of active mailboxes/server 1000 Number of databases/host 6 Number of copies/database 2 Number of mailboxes/database 167 Simulated profile: operations per second per mailbox (IOPS), includes 20% headroom maintenance (DBM) + Log LUN size Total database size for performance testing 0.24 Tested with 24/7 DBM enabled 3 TB 8.64 TB (6 databases * 1.44 TB) % storage capacity used by Exchange database 48% (8.64 TB / 18 TB) 6

7 Storage hardware Storage Connectivity Storage model and OS/firmware version Storage cache Number of storage controllers Number of storage ports Maximum bandwidth of storage connectivity to host Storage Controller Controller Cache Host server type SAS HP D2600 (0134 firmware) See below 1 per server Connected (2) 4x 6Gb SAS connectors 24 Gb per 4x SAS connector (2 in use for this solution) HP Smart Array P411 1 GB Flash-Backed Write Cache (25/75 read/write = default) HP ProLiant DL360 G7 Total number of disks tested in solution 12 Maximum number of spindles that can be hosted in the storage 96 (12 per D2600 x8) Storage software Smart Array P411 Driver Queue depth & target setting Multipathing Host OS Not applicable Not applicable Windows Server 2008 R2 Enterprise with SP1 ESE.dll file version Storage disk configuration (mailbox & log disks) Disk type, speed, and firmware revision Raw capacity per disk (TB) HP 3 TB 6Gb SAS 7.2k RPM LFF 3.5 MDL HDD (firmware: HPD3) 3 TB Number of physical disks in test 12 Total raw storage capacity (TB) Disk slice size (GB) RAID level Total formatted capacity (TB) 36 TB Not applicable RAID 1 (2 disks per RAID group) 18 TB Storage capacity utilization 50% capacity utilization 24% Formatted capacity / Total raw capacity Total size / Total raw capacity * Capacity of drives, and therefore the raw data capacity of the disk array, is based on 1K = 1000, not This means that 1 GB = 1,000,000,000 bytes, not (1,073,741,824 bytes) 7

8 Best practices Exchange Server is a disk-intensive application. For Exchange 2010 best practices on storage design from Microsoft, visit For Exchange Server solution guidance, visit HP at hp.com/solutions/microsoft/exchange. The best practices for this solution are: Drivers and Firmware Ensure firmware and drivers for all hardware are up to date. For more information, see: Physical Drive Write Cache Unlike controller-level cache, individual drive write caches are not protected. If the server loses power or if a hot plug drive is physically removed from the array during operations, unwritten data in the physical drives write caches will be lost. HP recommends Physical Drive Write Cache be disabled on the HP Smart Array P411 controller. For more information, see: Accelerator Ratio and Flash-Backed Write Cache (FBWC) HP recommends setting the Accelerator Ratio to 75 percent write cache and 25 percent read cache (battery-backed cache). 1 GB or more of Flash-Backed Write Cache (FBWC) is recommended. Dual Domain The HP Smart Array Advanced Pack is required to enable this feature. Dual domain creates redundant pathways for external drives from server to storage devices. The redundant paths created by these configurations reduce or eliminate single points of failure within the storage network. For more information on the Smart Array Advanced Pack, see: Jetstress 2010 Before installing Exchange Server 2010, test your storage solution with Jetstress to ensure it is configured properly and meets your requirements. For more information on Jetstress, see: Mailbox Copies This solution was tested with 2 copies of the Exchange mailbox database. When using a JBOD configuration without RAID storage protection, ensure that there are at least three copies for each Exchange mailbox database in the solution. RAID Level The disks used in this solution were configured as RAID 1 pairs with a RAID stripe size of 256 KB (256 KB or better is recommended). Provisioning of other RAID types are supported but not recommended for this Exchange Server solution. Test results summary This section provides a high-level summary of the test data from ESRP and links to the detailed HTML reports generated by the ESRP testing framework. Click on the underlined headings below to view the HTML report for each test. An HP ProLiant DL360 G7 server was used to drive the Jetstress load, and simulate the storage. For solutions that utilize a uniform building block style where each building block is independent and isolated, ESRP requires that only one of the building blocks be tested. In this case, a single unit was tested as the building block. However, for production deployments of this solution, 2 identical units are required. For site resiliency, a third copy could be added later. 8

9 Reliability One of the tests in the framework is designed to test reliability over a 24-hour test period. The goal is to verify that the storage can handle high load for a long period of time. Both log and database files will be analyzed for integrity after the stress test to ensure no database/log corruption. Below is an initial list of questions used to validate testing. Q. Were any errors reported in the saved event log file? A. No. There were no relevant errors reported in the event log for the storage reliability testing. Q. Were any errors reported during the database and log checksum process? A. No. There were no errors reported for the database and log checksum process. Storage performance results The Primary Storage performance testing is designed to exercise the storage with maximum sustainable Exchange type of for 2 hours. The test shows how long it takes the storage to respond to an under load. The data below is the sum of all logical disk s and the average of all the logical disk latency in the 2 hour test duration. This solution is designed around a 2 server DAG with a single server failure service level. It is important to understand not only the performance of the storage solution in normal operations with all servers hosting Exchange mailbox databases, but also with a single server failure where the remaining server is running all Exchange mailbox databases. The following table provides performance information for this scenario. Disk Transfers/sec 701 Disk /sec 438 Disk /sec 263 Disk Read (ms) Disk Write (ms) 0.84 Transaction Log Log Disk /sec 240 Log Disk Write (ms) 0.17 backup/recovery performance There are two test reports in this section. The first one is to measure the sequential read rate of the database files, and the second is to measure the recovery/replay performance (playing transaction logs into the database). One important characteristic of the default test is that these read rates and log replay rates are measured with all databases under concurrent or simultaneous load. This test case was also run with a single server failure where the remaining server is running all Exchange mailbox databases. read-only performance This test is to measure the maximum rate at which databases could be backed up via a Microsoft Volume Shadow Copy Service (VSS) aware backup application. The following table shows the average rate for a single database file and for the entire server. MB read/sec per database MB read/sec per server

10 Transaction log recovery / replay performance This test is to measure 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 1 MB in size. time to play one log file (sec) 3.61 Conclusion The information discussed in this solution brief highlights the tested performance results and configuration best practices for an Exchange Server solution supporting 2,000 Exchange users with 4 GB mailboxes. Testing was performed with an HP Smart Array P411 controller and D2600 disk enclosure with (12) 3 TB MDL SAS 7.2k RPM disks for the Exchange database storage and transaction logs. The testing demonstrated that the storage subsystem was capable of supporting both the IOPS needed to support 2,000 Exchange users as well as providing additional headroom. This document was developed by HP Storage, 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 and should be used as a guide. Each specific deployment should be tested to ensure that their solution performs to the requirements of their specific environment. The ESRP program is not designed to be a benchmarking program. The tests are not designed to measure the maximum throughput for a given solution. Rather, it is focused on producing recommendations from vendors for Exchange Server storage solutions. So the data presented in this document should not be used for direct comparisons among solutions. 10

11 Appendix A Test reports 2 hour test Test Summary Overall Test Result Machine Name Test Description Test Start Time Test End Time Pass D users, 0.24 IOPS, 4GB Mailbox, Thread Count=4 6/20/2012 2:14:39 PM 6/21/2012 7:58:02 AM Collection Start Time 6/20/2012 2:17:52 PM Collection End Time 6/20/2012 4:17:45 PM Jetstress Version ESE Version Operating System Windows Server 2008 R2 Enterprise Service Pack 1 ( ) Performance Log C:\Jetstress tests\2000 user 4 thread\performance_2012_6_20_14_14_52.blg Sizing and Throughput Achieved Transactional per Second Target Transactional per Second 480 Initial Size (bytes) Final Size (bytes) Files (Count) 6 Jetstress System Parameters Thread Count Minimum Cache Maximum Cache Insert Operations 40% Delete Operations 20% Replace Operations 5% Read Operations 35% Lazy Commits 70% Run Background Maintenance True Number of Copies per 2 4 (per database) MB MB Configuration Instance Log path: E:\dblg1 : E:\dblg1\Jetstress edb Instance Log path: F:\dblg2 : F:\dblg2\Jetstress edb Instance Log path: G:\dblg3 : G:\dblg3\Jetstress edb Instance Log path: H:\dblg4 : H:\dblg4\Jetstress edb Instance Log path: I:\dblg5 : I:\dblg5\Jetstress edb Instance Log path: J:\dblg6 : J:\dblg6\Jetstress edb Transactional Performance MSExchange ==> Instances /sec /sec Log Log Log Log /sec /sec Log Log Instance Instance Instance Instance Instance Instance Background Maintenance Performance MSExchange ==> Instances Maintenance IO /sec Maintenance IO Instance Instance Instance Instance Instance Instance

12 Log Replication Performance MSExchange ==> Instances Log /sec Log Instance Instance Instance Instance Instance Instance Total Performance MSExchange ==> Instances /sec /sec Log Log Log Log Log /sec /sec Log Instance Instance Instance Instance Instance Instance Host System Performance Counter Minimum Maximum % Processor Time Available M Free System Page Table Entries Transition Pages RePurposed/sec Pool Nonpaged Pool Paged Page Fault Stalls/sec Test Log6/20/2012 2:14:39 PM -- Jetstress testing begins... 6/20/2012 2:14:39 PM -- Preparing for testing... 6/20/2012 2:14:46 PM -- Attaching databases... 6/20/2012 2:14:46 PM -- Preparations for testing are complete. 6/20/2012 2:14:46 PM -- Starting transaction dispatch.. 6/20/2012 2:14:46 PM -- cache settings: (minimum: MB, maximum: 1.5 GB) 6/20/2012 2:14:46 PM -- flush thresholds: (start: 15.3 MB, stop: 30.7 MB) 6/20/2012 2:14:52 PM -- read latency thresholds: (average: 20 msec/read, maximum: 100 msec/read). 6/20/2012 2:14:52 PM -- Log write latency thresholds: (average: 10 msec/write, maximum: 100 msec/write). 6/20/2012 2:14:56 PM -- Operation mix: Sessions 4, Inserts 40%, Deletes 20%, Replaces 5%, 35%, Lazy Commits 70%. 6/20/2012 2:14:56 PM -- Performance logging started (interval: ms). 6/20/2012 2:14:56 PM -- Attaining prerequisites: 6/20/2012 2:17:52 PM -- \MSExchange (JetstressWin)\ Cache Size, Last: (lower bound: , upper bound: none) 6/20/2012 4:17:52 PM -- Performance logging has ended. 6/21/2012 7:58:00 AM -- JetInterop batch transaction stats: , , , , and /21/2012 7:58:00 AM -- Dispatching transactions ends. 6/21/2012 7:58:00 AM -- Shutting down databases... 6/21/2012 7:58:02 AM -- Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete) and Instance (complete) 6/21/2012 7:58:02 AM -- C:\Jetstress tests\2000 user 4 threads\performance_2012_6_20_14_14_52.blg has 491 samples. 6/21/2012 7:58:02 AM -- Creating test report... 6/21/2012 7:58:05 AM -- Instance has 19.2 for. 6/21/2012 7:58:05 AM -- Instance has 0.2 for Log. 6/21/2012 7:58:05 AM -- Instance has 0.2 for Log. 6/21/2012 7:58:05 AM -- Instance has 14.4 for. 6/21/2012 7:58:05 AM -- Instance has 0.2 for Log. 6/21/2012 7:58:05 AM -- Instance has 0.2 for Log. 6/21/2012 7:58:05 AM -- Instance has 14.1 for. 6/21/2012 7:58:05 AM -- Instance has 0.2 for Log. 6/21/2012 7:58:05 AM -- Instance has 0.2 for Log. 6/21/2012 7:58:05 AM -- Instance has 14.3 for. 6/21/2012 7:58:05 AM -- Instance has 0.2 for Log. 6/21/2012 7:58:05 AM -- Instance has 0.2 for Log. 6/21/2012 7:58:05 AM -- Instance has 14.0 for. 6/21/2012 7:58:05 AM -- Instance has 0.2 for Log. 6/21/2012 7:58:05 AM -- Instance has 0.2 for Log. 6/21/2012 7:58:05 AM -- Instance has 14.2 for. 6/21/2012 7:58:05 AM -- Instance has 0.2 for Log. 6/21/2012 7:58:05 AM -- Instance has 0.2 for Log. 6/21/2012 7:58:05 AM -- Test has 0 Maximum Page Fault Stalls/sec. 6/21/2012 7:58:05 AM -- The test has 0 Page Fault Stalls/sec samples higher than 0. 6/21/2012 7:58:05 AM -- C:\Jetstress tests\2000 user 4 threads\performance_2012_6_20_14_14_52.xml has 479 samples queried. 12

13 24 hour test Test Summary Overall Test Result Machine Name Test Description Test Start Time Test End Time Pass D Hour Stress Test 2000 users, 0.24 IOPS, 4GB Mailbox, TC=4 6/21/2012 3:49:15 AM 6/23/2012 7:57:59 PM Collection Start Time 6/21/2012 3:50:57 AM Collection End Time 6/22/2012 3:50:50 AM Jetstress Version ESE Version Operating System Windows Server 2008 R2 Enterprise Service Pack 1 ( ) Performance Log C:\Jetstress tests\2000 user 4 threads\performance_2012_6_21_8_54_11.blg Sizing and Throughput Achieved Transactional per Second Target Transactional per Second 480 Initial Size (bytes) Final Size (bytes) Files (Count) 6 Jetstress System Parameters Thread Count Minimum Cache Maximum Cache Insert Operations 40% Delete Operations 20% Replace Operations 5% Read Operations 35% Lazy Commits 70% Run Background Maintenance True Number of Copies per 2 4 (per database) MB MB Configuration Instance Log path: E:\dblg1 : E:\dblg1\Jetstress edb Instance Log path: F:\dblg2 : F:\dblg2\Jetstress edb Instance Log path: G:\dblg3 : G:\dblg3\Jetstress edb Instance Log path: H:\dblg4 : H:\dblg4\Jetstress edb Instance Log path: I:\dblg5 : I:\dblg5\Jetstress edb Instance Log path: J:\dblg6 : J:\dblg6\Jetstress edb Transactional Performance MSExchange ==> Instances /sec /sec Log Log Log /sec Log /sec Log Log Instance Instance Instance Instance Instance Instance Background Maintenance Performance MSExchange ==> Instances Maintenance IO /sec Maintenance IO Instance Instance Instance Instance Instance Instance

14 Log Replication Performance MSExchange ==> Instances Log /sec Log Instance Instance Instance Instance Instance Instance Total Performance MSExchange ==> Instances /sec /sec Log Log Log /sec Log /sec Log Log Instance Instance Instance Instance Instance Instance Host System Performance Counter Minimum Maximum % Processor Time Available M Free System Page Table Entries Transition Pages RePurposed/sec Pool Nonpaged Pool Paged Page Fault Stalls/sec Test Log6/3/2011 3:49:15 AM -- Jetstress testing begins... 6/21/2011 3:49:15 AM -- Preparing for testing... 6/21/2011 3:49:24 AM -- Attaching databases... 6/21/2011 3:49:24 AM -- Preparations for testing are complete. 6/21/2011 3:49:24 AM -- Starting transaction dispatch.. 6/21/2011 3:49:24 AM -- cache settings: (minimum: MB, maximum: 2.2 GB) 6/21/2011 3:49:24 AM -- flush thresholds: (start: 23.0 MB, stop: 46.1 MB) 6/21/2011 3:49:34 AM -- read latency thresholds: (average: 20 msec/read, maximum: 100 msec/read). 6/21/2011 3:49:34 AM -- Log write latency thresholds: (average: 10 msec/write, maximum: 100 msec/write). 6/21/2011 3:49:43 AM -- Operation mix: Sessions 8, Inserts 40%, Deletes 20%, Replaces 5%, 35%, Lazy Commits 70%. 6/21/2011 3:49:43 AM -- Performance logging started (interval: ms). 6/21/2011 3:49:43 AM -- Attaining prerequisites: 6/21/2011 3:50:57 AM -- \MSExchange (JetstressWin)\ Cache Size, Last: (lower bound: , upper bound: none) 6/22/2011 3:50:58 AM -- Performance logging has ended. 6/23/2011 7:57:48 PM -- JetInterop batch transaction stats: , , , , , , , and /23/2011 7:57:48 PM -- Dispatching transactions ends. 6/23/2011 7:57:48 PM -- Shutting down databases... 6/23/2011 7:57:59 PM -- Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete) and Instance (complete) 6/23/2012 7:57:59 PM -- C:\Jetstress tests\2000 user 4 threads\performance_2012_6_21_8_54_11.blg has 1715 samples. 6/23/2012 7:57:59 PM -- Creating test report... 6/23/2012 7:58:38 PM -- Instance has 19.4 for. 6/23/2012 7:58:38 PM -- Instance has 0.2 for Log. 6/23/2012 7:58:38 PM -- Instance has 0.2 for Log. 6/23/2012 7:58:38 PM -- Instance has 14.6 for. 6/23/2012 7:58:38 PM -- Instance has 0.2 for Log. 6/23/2012 7:58:38 PM -- Instance has 0.2 for Log. 6/23/2012 7:58:38 PM -- Instance has 14.6 for. 6/23/2012 7:58:38 PM -- Instance has 0.2 for Log. 6/23/2012 7:58:38 PM -- Instance has 0.2 for Log. 6/23/2012 7:58:38 PM -- Instance has 14.5 for. 6/23/2012 7:58:38 PM -- Instance has 0.2 for Log. 6/23/2012 7:58:38 PM -- Instance has 0.2 for Log. 6/23/2012 7:58:38 PM -- Instance has 14.4 for. 6/23/2012 7:58:38 PM -- Instance has 0.2 for Log. 6/23/2012 7:58:38 PM -- Instance has 0.2 for Log. 6/23/2012 7:58:38 PM -- Instance has 14.3 for. 6/23/2012 7:58:38 PM -- Instance has 0.2 for Log. 6/23/2012 7:58:38 PM -- Instance has 0.2 for Log. 6/23/2012 7:58:38 PM -- Test has 0 Maximum Page Fault Stalls/sec. 6/23/2012 7:58:38 PM -- The test has 0 Page Fault Stalls/sec samples higher than 0. 6/23/2012 7:58:38 PM -- C:\Jetstress tests\2000 user 4 threads \Performance_2012_6_21_8_54_11.xml has 1702 samples queried. 14

15 backup test Backup Statistics - All Instance Size (M) Elapsed Backup Time M Transferred/sec Instance :03: Instance :38: Instance :52: Instance :09: Instance :56: Instance :56: Jetstress System Parameters Thread Count 4 (per database) Minimum Cache MB Maximum Cache MB Insert Operations 40% Delete Operations 20% Replace Operations 5% Read Operations 35% Lazy Commits 70% Configuration Instance Log path: E:\dblg1 Backup path: E:\dblg1 : E:\dblg1\Jetstress edb Instance Log path: F:\dblg2 Backup path: F:\dblg2 : F:\dblg2\Jetstress edb Instance Log path: G:\dblg3 Backup path: G:\dblg3 : G:\dblg3\Jetstress edb Instance Log path: H:\dblg4 Backup path: H:\dblg4 : H:\dblg4\Jetstress edb Instance Log path: I:\dblg5 Backup path: I:\dblg5 : I:\dblg5\Jetstress edb Instance Log path: J:\dblg6 Backup path: J:\dblg6 : J:\dblg6\Jetstress edb Transactional Performance MSExchange ==> Instances /sec /sec Log Log Log /sec Log /sec Log Log Instance Instance Instance Instance Instance Instance Host System Performance Counter Minimum Maximum % Processor Time Available M Free System Page Table Entries Transition Pages RePurposed/sec Pool Nonpaged Pool Paged Page Fault Stalls/sec

16 Test Log6/22/2012 8:13:15 AM -- Jetstress testing begins... 6/22/2012 8:13:15 AM -- Preparing for testing... 6/22/2012 8:13:22 AM -- Attaching databases... 6/22/2012 8:13:22 AM -- Preparations for testing are complete. 6/22/2012 8:13:31 AM -- Performance logging started (interval: ms). 6/22/2012 8:13:31 AM -- Backing up databases... 6/22/2012 7:17:08 PM -- Performance logging has ended. 6/22/2012 7:17:08 PM -- Instance (100% processed), Instance (100% processed), Instance (100% processed), Instance (100% processed), Instance (100% processed) and Instance (100% processed) 6/22/2012 7:17:08 PM -- C:\Jetstress tests\db Backup test\backup_2012_6_22_8_13_22.blg has 1326 samples. 6/22/2012 7:17:08 PM -- Creating test report... Soft recovery test Soft-Recovery Statistics - All Instance Log files replayed Elapsed seconds Instance Instance Instance Instance Instance Instance Configuration Instance Log path: E:\dblg1 : E:\dblg1\Jetstress edb Instance Log path: F:\dblg2 : F:\dblg2\Jetstress edb Instance Log path: G:\dblg3 : G:\dblg3\Jetstress edb Instance Log path: H:\dblg4 : H:\dblg4\Jetstress edb Instance Log path: I:\dblg5 : I:\dblg5\Jetstress edb Instance Log path: J:\dblg6 : J:\dblg6\Jetstress edb Transactional Performance MSExchange ==> Instances /sec /sec Log Log Log /sec Log /sec Log Instance Instance Instance Instance Instance Instance Background Maintenance Performance MSExchange ==> Instances Maintenance IO /sec Maintenance IO Instance Instance Instance Instance Instance Instance Log 16

17 Total Performance MSExchange ==> Instances /sec /sec Log Log Log /sec Log /sec Log Instance Instance Instance Instance Instance Instance Host System Performance Counter Minimum Maximum % Processor Time Available M Free System Page Table Entries Transition Pages RePurposed/sec Pool Nonpaged Pool Paged Page Fault Stalls/sec Log Test Log6/28/2012 8:31:23 AM -- Jetstress testing begins... 6/28/2012 8:31:23 AM -- Preparing for testing... 6/28/2012 8:31:29 AM -- Attaching databases... 6/28/2012 8:31:29 AM -- Preparations for testing are complete. 6/28/2012 8:31:29 AM -- Starting transaction dispatch... 6/28/2012 8:31:29 AM -- cache settings: (minimum: MB, maximum: 1.5 GB) 6/28/2012 8:31:29 AM -- flush thresholds: (start: 15.3 MB, stop: 30.7 MB) 6/28/2012 8:31:36 AM -- read latency thresholds: (average: 20 msec/read, maximum: 100 msec/read). 6/28/2012 8:31:36 AM -- Log write latency thresholds: (average: 10 msec/write, maximum: 100 msec/write). 6/28/2012 8:31:39 AM -- Operation mix: Sessions 4, Inserts 40%, Deletes 20%, Replaces 5%, 35%, Lazy Commits 70%. 6/28/2012 8:31:39 AM -- Performance logging started (interval: ms). 6/28/2012 8:31:39 AM -- Generating log files... 6/28/ :15:47 AM -- E:\dblg1 (101.4% generated), F:\dblg2 (100.2% generated), G:\dblg3 (101.0% generated), H:\dblg4 (100.2% generated), I:\dblg5 (101.4% generated) and J:\dblg6 (100.4% generated) 6/28/ :15:47 AM -- Performance logging has ended. 6/28/ :15:47 AM -- JetInterop batch transaction stats: 21754, 21798, 21831, 21602, and /28/ :15:47 AM -- Dispatching transactions ends. 6/28/ :15:47 AM -- Shutting down databases... 6/28/ :15:48 AM -- Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete) and Instance (complete) 6/28/ :15:48 AM -- C:\Program Files\Exchange Jetstress\Performance_2012_6_28_8_31_36.blg has 416 samples. 6/28/ :15:48 AM -- Creating test report... 6/28/ :15:49 AM -- Instance has 18.2 for. 6/28/ :15:49 AM -- Instance has 0.2 for Log. 6/28/ :15:49 AM -- Instance has 0.2 for Log. 6/28/ :15:49 AM -- Instance has 15.6 for. 6/28/ :15:49 AM -- Instance has 0.2 for Log. 6/28/ :15:49 AM -- Instance has 0.2 for Log. 6/28/ :15:49 AM -- Instance has 16.4 for. 6/28/ :15:49 AM -- Instance has 0.2 for Log. 6/28/ :15:49 AM -- Instance has 0.2 for Log. 6/28/ :15:49 AM -- Instance has 16.5 for. 6/28/ :15:49 AM -- Instance has 0.2 for Log. 6/28/ :15:49 AM -- Instance has 0.2 for Log. 6/28/ :15:49 AM -- Instance has 16.4 for. 6/28/ :15:49 AM -- Instance has 0.2 for Log. 6/28/ :15:49 AM -- Instance has 0.2 for Log. 6/28/ :15:49 AM -- Instance has 16.3 for. 6/28/ :15:49 AM -- Instance has 0.2 for Log. 6/28/ :15:49 AM -- Instance has 0.2 for Log. 6/28/ :15:49 AM -- Test has 0 Maximum Page Fault Stalls/sec. 6/28/ :15:49 AM -- The test has 0 Page Fault Stalls/sec samples higher than 0. 6/28/ :15:49 AM -- C:\Program Files\Exchange Jetstress\Performance_2012_6_28_8_31_36.xml has 415 samples queried. 6/28/ :15:49 AM -- C:\Program Files\Exchange Jetstress\Performance_2012_6_28_8_31_36.html was saved. 6/28/ :16:02 AM -- Performance logging started (interval: 4000 ms). 6/28/ :16:02 AM -- Recovering databases... 6/28/ :48:08 AM -- Performance logging has ended. 6/28/ :48:08 AM -- Instance ( ), Instance ( ), Instance ( ), Instance ( ), Instance ( ) and Instance ( ) 6/28/ :48:08 AM -- C:\Program Files\Exchange Jetstress\SoftRecovery_2012_6_28_11_15_59.blg has 480 samples. 6/28/ :48:08 AM -- Creating test report... 17

18 For more information QuickSpecs for HP D2000 disk enclosures: QuickSpecs for HP Smart Array P411 controller: To read more about HP solutions for Exchange, including best practices and additional testing of HP server and storage products with Exchange, see: hp.com/solutions/exchange For general information on Exchange sizing and best practices, there are several white papers and planning tools that are free to download from: hp.com/solutions/activeanswers/exchange For more information on Jetstress and the process and requirements for validating an Exchange storage solution, see: To help us improve our documents, please provide feedback at hp.com/solutions/feedback. Get connected hp.com/go/getconnected Current HP driver, support, and security alerts delivered directly to your desktop Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omiss ions contained herein. Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. 18 4AA4-3116ENW, Created September 2012; Updated September 2012, Rev. 1