NetApp FAS Mailbox Exchange 2010 Mailbox Resiliency Storage Solution

Transcription

1 NetApp FAS Mailbox Exchange 2010 Mailbox Resiliency Storage Solution Tested with: ESRP Storage Version 3.0 Tested Date: May 8, 2010

2 Content Overview... 3 Disclaimer... 3 Features... 3 Solution Description... 5 Targeted Customer Profile... 8 Tested Deployment... 8 Simulated Exchange Configuration... 8 Storage Hardware... 9 Storage Software... 9 Storage Disk Configuration (Mailbox Store Disks) Storage Disk Configuration (Transactional Log Disks Utilizing Same Disks as Mailbox Store Database) Best Practices Mailbox Resiliency Backup strategy Contact for Additional Information Test Result Summary Reliability Storage Performance Results Database Backup/Recovery Performance Database Read-only Performance Transaction Log Recovery/Replay Performance Conclusion Appendix A Test Results Hour Stress/Reliability Test Results Hour Performance Test Results Database Backup Test Results Soft Recovery Test Results

3 Overview This document provides information on a NetApp FAS3140 Fibre Channel Exchange 2010 Mailbox Resiliency storage solution based on the Microsoft Exchange Solution Reviewed Program (ESRP) Storage program*. For any questions or comments regarding the contents of this document, see Contact for Additional Information. *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 details on the Microsoft ESRP Storage program, please click 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 NetApp 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 NetApp, and NetApp cannot guarantee the accuracy of any information presented after the date of publication. Features This document describes the testing of a 12,000 mailbox resiliency (2-copy) database availability group (DAG) configuration for Exchange Server 2010 with a NetApp FAS3140 storage system. The FAS3140 is a member of NetApp s industry-leading FAS3100 midrange product family. Leveraging NetApp s Unified Storage Architecture and inherent storage efficiency features, the FAS3140 is a highly available system that can handle diverse needs SAN and NAS, primary and secondary storage. Compared to the previous generation FAS3040 midrange controller, the FAS3140 provides mid-sized and large enterprises with a significant performance increase, higher I/O scalability, and a 25% increase in storage capacity The FAS3140 comes in a 6U form factor with dual independent hot swappable controllers and dual hot swappable power supplies. Storage options include external SAS shelves with either SAS or SATA disks and FC shelves with either FC or SATA disks for a total maximum disk count of 420 drives. The FAS3140 system is simple to deploy and manage. It ships with a wealth of integrated data protection and management software based on Data ONTAP to help increase storage utilization and the efficiency of your system and storage administrators, such as: 3

4 Thin provisioning helps avoid the costly over provisioning and timeconsuming reconfiguration that is typical with other storage solutions. Deduplication enables you to store only one copy of each unique data object, substantially reducing capacity requirements. For the purposes of this tested Exchange deployment, various NetApp best practice recommendations for an Exchange deployment were followed. The FAS3140 being tested used standard NetApp features such as Snapshot, RAID-DP, FlexVol flexible volumes, and SnapDrive. The tested deployment includes disk space allocated for backing up and restoring Exchange databases and logs using NetApp Snapshot technology. Snapshot technology provides in-place, logical backups of an entire Exchange environment, usually in seconds, regardless of whether the data being backed up is several megabytes or hundreds of terabytes. Additionally, NetApp Snapshot technology causes virtually no loss of performance following Snapshot creation and use going forward. The performance results listed in this report were produced with two NetApp Snapshot copies in place on the tested storage systems. RAID-DP is a high performance implementation of RAID 6 that provides double parity across the disk subsystem and protects against the failure of up to two disks per RAID group. Calculations have shown double parity RAID offers over 160 times the protection against data loss than RAID 10 and almost 4000 times the protection against data loss than RAID 5. The performance results listed in this report were produced with RAID-DP enabled. FlexVol volumes enable the creation of logical storage volumes across a large pool of disk drives known as an aggregate. FlexVol volumes provide three core advantages for workloads such as Microsoft Exchange: 1. Using FlexVol volumes, the capacity and performance bandwidth of a large collection of fast drives can be made available to all volumes. Even very small FlexVol volumes have the performance benefit of a very large number of drives. 2. A large number of volumes may be created, all with independent Snapshot copy schedules, mirroring events, etc. 3. All FlexVol volumes can be managed independently, while receiving the maximum I/O benefit of a much larger pool of drives SnapDrive for Windows offers a rich set of capabilities that virtualizes and enhances storage management for Microsoft Windows environments. SnapDrive is tightly integrated with NTFS to provide a layer of abstraction between application data and physical storage associated with that data. 4

5 For this ESRP testing environment, NetApp SnapManager for Microsoft Exchange (SME) was not required. SnapManager for Exchange is an Exchange software backup and recovery management solution that integrates NetApp Snapshot backups with Microsoft Exchange Server via the Microsoft standard and approved Volume Shadow Copy Services (VSS) snapshot interface. NetApp highly recommends SnapManager for Exchange as a part of a production Exchange deployment. For this ESRP testing environment, two DAGs (each containing 2 mailbox servers) were used. The detailed DAG architecture is specified in the next section. Solution Description This section outlines the Exchange 2010 mailbox resiliency solution NetApp implemented to run the ESRP tests. Storage: A pair of FAS3140 storage controllers o A Flash Cache Module (256GB) per controller Data ONTAP SATA disk shelves, 1 TB 7.2K RPM drives Link to FAS3140 Windows Server Catalog listing: 68ef-2f36-d c10f398d&bCatID=1511 Switches: A pair of Brocade Gbps FC switch Figure 1 depicts the DAG architecture and the topology of the Exchange 2010 mailbox resiliency solution using the NetApp FAS3140 storage system. The FAS3140 consists of two storage controllers: fas and fas The first Exchange data copy (active copy) is on fas The second Exchange data copy (passive copy) is on fas

6 Figure 1) Topology and DAG architecture of the FAS3140 mailbox resiliency ESRP testing. Only the primary copy storage is described below. The secondary copy storage (shown gray in Figure 1) is configured identically (from the host on down to the spindle including brand, model, firmware, drivers, etc.). The fas storage controller was configured with four aggregates for Exchange 2010 databases and log files. Four FlexVol flexible volumes were created on each aggregate, three for databases and one for log files, for a total of sixteen flexible volumes. Sixteen LUNs were then created (one LUN per flexible volume). Among them, twelve LUNs for database and four LUNs for log files. The details about the placement of aggregates, volumes, and LUNs are enumerated in the table following. 6

7 For Mailbox Resiliency configuration, databases and log files can be placed on the same set of disk drives (see Therefore, the log files for DB11, DB12 and DB13 are located on LOG1; the log files for DB14, DB15 and DB16 are located on LOG2; and so on. Controller Name fas Aggregate Volume LUN db11_fv DB11 aggr1 db12_fv DB12 db13_fv DB13 log1_fv LOG1 db14_fv DB14 aggr2 db15_fv DB15 db16_fv DB16 log2_fv LOG2 db21_fv DB21 aggr3 db22_fv DB22 db23_fv DB23 log3_fv LOG3 db24_fv DB24 aggr4 db25_fv DB25 db26_fv DB26 log4_fv LOG4 RAID Type Number of Data Drives Number of Parity Drives RAID-DP 14 2 RAID-DP 14 2 RAID-DP 14 2 RAID-DP 14 2 Number of LUNs 3 x 2.08TB + 1x 100GB 3 x 2.08TB + 1x 100GB 3 x 2.08TB + 1x 100GB 3 x 2.08TB + 1x 100GB The DAG configuration is as follows: Four mailbox servers: , , and mailboxes per database Twelve active databases total: o DB11 to DB16 hosted by o DB21 to DB26 hosted by Twelve passive databases total (shown in gray in Figure 1): hosted by and All passive databases are on separate aggregates and on the separate but identical storage controller: fas Using NetApp RAID-DP Two copies of databases 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. Other factors which affect the server scalability are: server processor utilization, server physical and virtual memory limitations, 7

8 resource requirements for other applications, directory and network service latencies, network infrastructure limitations, replication and recovery requirements, and client usage profiles. All these factors are beyond the scope for ESRP-Storage. Therefore, the number of mailboxes hosted per server as part of the tested configuration may not necessarily be viable for some customer deployments. For more information on identifying and addressing performance bottlenecks in an Exchange system, please refer to Microsoft's Troubleshooting Microsoft Exchange Server Performance, available at Targeted Customer Profile This solution is designed for a mid to large-sized Enterprise Exchange environment. The target customer would typically be one looking for a scalable, reliable, high-performance, and highly available Exchange storage solution. The solution tested is designed for: 12,000 mailboxes 4 servers (2 tested) IOPS (0.120 tested for additional 20% headroom) 2000 MB mailboxes 24 x 7 background database maintenance enabled Maintaining ample controller headroom available for storage infrastructure activities such as data replication and disk reconstructs Allocating space for backups and restores of Exchange databases via NetApp Snapshot technology Mailbox Resiliency (2-copy) Tested Deployment The following tables summarize the testing environment: Simulated Exchange Configuration Number of Exchange mailboxes 12,000 simulated Number of Database Availability 2 Groups (DAGs) Number of servers/dag 2 8

9 Number of active mailboxes/server 6,000 Number of databases/host 6 (12 total) Number of copies/database 2 Number of mailboxes/database 1,000 Simulated profile: I/O s per second per mailbox (IOPS, include 20% IOPs per mailbox (0.10 IOPs plus 20% headroom added) headroom) Database LUN size 2.08 TB Log LUN size 100 GB Total database size for performance 23,438 GB testing % storage capacity used by 92% Exchange database** **Storage performance characteristics change based on the percentage utilization of the individual disks. Tests that use a small percentage of the storage (~25%) may exhibit reduced throughput if the storage capacity utilization is significantly increased beyond what is tested in this paper. Storage Hardware Storage Connectivity (Fiber Channel, SAS, SATA, iscsi) Storage model and OS/firmware revision Storage cache Number of storage controllers Number of storage ports Maximum bandwidth of storage connectivity to host Switch type/model/firmware revision HBA model and firmware Number of HBA s/host Host server type Total number of disks tested in solution Maximum number of spindles can be hosted in the storage Fibre Channel SAN FAS3140 Data ONTAP GB, plus 256GB Flash Cache 2 (1 tested) 8 (4 tested) 32 Gbps (8 x 4 Gb/sec per port) Brocade 4100 FC Switch, v6.1.1b Emulex LP11002, v2.72a2 2 per host IBM x3650, 4 x 3.6 GHz CPU, 18 GB RAM Storage Software HBA driver STOR miniport v HBA QueueTarget Setting N/A HBA QueueDepth Setting 254 Multi-Pathing Data ONTAP DSM for Windows MPIO 9

10 Host OS Windows Server 2008 Enterprise SP2 ESE.dll file version Replication solution name/version N/A Storage Disk Configuration (Mailbox Store Disks) Disk type, speed and firmware SATA 1TB 7.2K RPM FW NA00 revision Raw capacity per disk (GB) 1 TB Number of physical disks in test 64 Total raw storage capacity (GB) 64 TB Disk slice size (GB) N/A Number of slices per LUN or number Four aggregates consisting of one 16- of disks per LUN disk RAID-DP groups for both database and log files Raid level RAID-DP Total formatted capacity TB Storage capacity utilization*** 39% Database capacity utilization*** 36% *** 30% of the total raw storage capacity is reserved for snapshot space and is also included in this calculation. If the 30% snapshot reserve is excluded from this calculation, the storage capacity and database capacity utilization would be 56% and 51%, respectively. Storage Disk Configuration (Transactional Log Disks Utilizing Same Disks as Mailbox Store Database) Disk type, speed and firmware revision Raw capacity per disk (GB) Number of Spindles in test total raw storage capacity (GB) Disk slice size (GB) Number of slices per LUN or number of disks per LUN Raid level Total formatted capacity SATA 1TB 7.2K RPM FW NA00 1 TB 64 (same as mailbox store disks) 64 TB N/A Four aggregate consisting of one 16- disk RAID-DP groups both database and log files RAID-DP 400 GB Best Practices Exchange server is a disk-sensitive application. Based on the testing run using the ESRP framework, we would recommend the following to improve the storage performance. 10

11 For Exchange 2010 best practices on storage design, please visit Sizing Performance, stability, disaster recovery procedures, and general Exchange maintenance all benefit from proper Exchange sizing. NetApp has studied the I/O patterns of Exchange systems running on NetApp storage. When a customer approaches NetApp for an Exchange storage solution, NetApp leverages this knowledge and expertise to properly size the storage specifically to the customer s environment. Several factors are taken into consideration in this process including but not limited to: Number of mailboxes Mailbox size IOPS per mailbox Storage platform type Physical drive type Backup retention time Layout Another key consideration for Exchange Server 2010 is layout of databases, volumes, and LUNs. NetApp storage solutions can take full advantage of the performance benefits of aggregates and flexible volumes. And following proper layout guidelines is essential to ensuring a high performing, low latency Exchange solution. Consulting with your NetApp Exchange specialist about proper layout will ensure that your Exchange deployment on NetApp storage will perform optimally in your environment. Mailbox Resiliency For this ESRP submission, we followed these NetApp Exchange best practices: Use dedicated FlexVol volumes for databases. Use dedicated FlexVol volumes for transaction logs. Use SnapDrive to provision LUNs. This reduces the complexity of LUN provisioning and additionally means that diskpart is not required or recommended as SnapDrive provides for correct LUN sector alignment. Spindle counts for databases and log files are derived from consulting with NetApp Exchange specialists. Further information on Exchange sizing is available from your local NetApp Exchange specialist. 11

12 Backup strategy The deployed solution allocates sufficient disk space for backing up and restoring Exchange databases and logs using Microsoft VSS technology and NetApp Snapshot technology. Contact for Additional Information Link to appropriate storage specs on netapp.com Data ONTAP Software FlexVol & FlexClone technologies SnapDrive Software SnapManager for Exchange Software NetApp RAID-DP RAID-DP and Exchange NetApp Flash Cache (PAM II) Test Result Summary This section provides a high level summary of the test data from ESRP and the link to the detailed html reports which are generated by the ESRP testing framework. Please click on the underlined headings below to view the html report for each test. Reliability A number of tests in the framework are to check Reliability where the tests run for 24 hours. The goal is to verify the storage can handle high IO 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. The following list provides an overview: (click on the underlined word will show the html report after the reliability tests run) There were no errors reported in any of the event logs collected for the reliability tests. There were no errors reported during 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 IO for 2 hours. The test is to show how long it takes for the storage to respond to an IO under load. The data below is the sum of all of the logical disk I/O s and average of all the 12

13 logical disks I/O latency in the 2 hours test duration. Each server is listed separately and the aggregate numbers across all servers is listed as well. Individual Server Metrics: The sum of I/O s across Storage Groups and the average latency across all Storage Groups on a per server basis. Host Database I/O Database Disks Transfers/sec 877 Database Disks Reads/sec 559 Database Disks Writes/sec 319 Database Disk Read (ms) Database Disk Write (ms) 3.82 Transaction Log I/O Log Disks Writes/sec 294 Log Disk Write (ms) 1.06 Host Database I/O Database Disks Transfers/sec 863 Database Disks Reads/sec 549 Database Disks Writes/sec 313 Database Disk Read (ms) Database Disk Write (ms) 4.03 Transaction Log I/O Log Disks Writes/sec 290 Log Disk Write (ms) 1.09 Aggregate Performance across all servers Metrics: The sum of I/O s across servers in the solution and the average latency across both servers in the solution. Database I/O Database Disks Transfers/sec 1740 Database Disks Reads/sec 1108 Database Disks Writes/sec 632 Database Disk Read (ms) Database Disk Write (ms) 3.93 Transaction Log I/O Log Disks Writes/sec 584 Log Disk Write (ms)

14 Database 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 in to the database). Database Read-only Performance The test is to measure the maximum rate at which databases could be backed up via VSS. The following table shows the average rate for a single database file. Host MB read/sec per database MB read/sec total per server Host MB read/sec per database MB read/sec total per server Transaction Log Recovery/Replay Performance The 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. Host time to play one Log file (sec) Host time to play one Log file (sec) Conclusion This document demonstrates that the NetApp FAS3140 with a Flash Cache Module is a high-performance, highly-reliable and high-efficiency storage system more than capable of supporting 12,000 Exchange 2010 users at IOPs per user and 2000 MB mailbox size in Exchange mailbox resilience configuration. Moreover, extra storage space was allocated in this tested solution for backing up and restoring Exchange databases and logs using Microsoft VSS technology and NetApp Snapshot technology. This document is developed by NetApp, and reviewed by the Microsoft Exchange Product team. The test results/data presented in this document is based on the tests introduced in the ESRP test framework. Customers should not quote the data directly for his/her pre-deployment verification. It is still 14

15 necessary to go through the exercises to validate the storage design for a specific customer environment. The ESRP program is not designed to be a benchmarking program; tests are not designed to get the maximum throughput for a giving solution. Rather, it is focused on producing recommendations from vendors for Exchange application. So the data presented in this document should not be used for direct comparisons among the solutions. NetApp offers its customers complete sizing information for Exchange Server deployments through its systems engineers. Contact your local NetApp sales office for additional information. Appendix A Test Results This section includes representative test results from one of the two servers under test: It is also representative of both servers test results, which are virtually identical. 24-Hour Stress/Reliability Test Results Microsoft Exchange Server Jetstress Tool - DBChecksum Test Result Report (from server ) Checksum Statistics - All Database Seen pages Bad pages Correctable pages Wrong pagenumber pages File length / seconds taken E:Jetstress edb M / sec F:Jetstress edb M / sec G:Jetstress edb M / sec H:Jetstress edb M / sec I:Jetstress edb M / sec J:Jetstress edb M / sec (Sum) M / sec Disk Subsystem Performance (of checksum) LogicalDisk Avg. Disk Avg. Disk sec/read sec/write Disk Reads/sec Disk Writes/sec Avg. Disk /Read E: F: G: H: I: J:

16 Memory System Performance (of checksum) Counter Minimum Maximum % Processor Time Available M Free System Page Table Entries Transition Pages RePurposed/sec Pool Nonpaged Pool Paged Test Log5/5/ :55:09 AM -- Jetstress testing begins... 5/5/ :55:09 AM -- Prepare testing begins... 5/5/ :55:16 AM -- Attaching databases... 5/5/ :55:16 AM -- Prepare testing ends. 5/5/ :55:16 AM -- Dispatching transactions begins... 5/5/ :55:16 AM -- Database cache settings: (minimum: MB, maximum: 1.5 GB) 5/5/ :55:16 AM -- Database flush thresholds: (start: 15.3 MB, stop: 30.7 MB) 5/5/ :55:23 AM -- Database read latency thresholds: (average: 20 msec/read, maximum: 200 msec/read). 5/5/ :55:23 AM -- Log write latency thresholds: (average: 10 msec/write, maximum: 200 msec/write). 5/5/ :55:26 AM -- Operation mix: Sessions 6, Inserts 40%, Deletes 20%, Replaces 5%, Reads 35%, Lazy Commits 70%. 5/5/ :55:26 AM -- Performance logging begins (interval: ms). 5/5/ :55:26 AM -- Attaining prerequisites: 5/5/ :01:20 PM -- \MSExchange Database(JetstressWin)\Database Cache Size, Last: (lower bound: , upper bound: none) 5/6/ :01:21 PM -- Performance logging ends. 5/6/ :01:21 PM -- JetInterop batch transaction stats: , , , , and /6/ :01:21 PM -- Dispatching transactions ends. 5/6/ :01:21 PM -- Shutting down databases... 5/6/ :01:38 PM -- Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete) and Instance (complete) 5/6/ :01:39 PM -- Performance logging begins (interval: ms). 5/6/ :01:39 PM -- Verifying database checksums... 5/7/ :03:25 AM -- E: (100% processed), F: (100% processed), G: (100% processed), H: (100% processed), I: (100% processed) and J: (100% processed) 5/7/ :03:25 AM -- Performance logging ends. 5/7/ :03:25 AM -- C:\Program Files\Exchange Jetstress\results\DBChecksum_2010_5_6_12_1_38.blg has 1442 samples. Microsoft Exchange Server Jetstress Tool - Stress Stress Test Result Report (from server ) Test Summary Overall Test Result Pass Machine Name Test Description Test Start Time Test End Time Collection Start Time Collection End Time 5/5/ :55:09 AM 5/6/ :01:38 PM 5/5/ :01:20 PM 5/6/ :01:13 PM Jetstress Version Ese Version Operating System Windows Server (R) 2008 Enterprise Service Pack 2 ( ) Performance Log C:\Program Files\Exchange Jetstress\results\Stress_2010_5_5_11_55_23.blg C:\Program Files\Exchange Jetstress\results\DBChecksum_2010_5_6_12_1_38.blg 16

17 Database Sizing and Throughput Achieved Transactional I/O per Second Target Transactional I/O per Second 720 Initial Database Size (bytes) Final Database Size (bytes) Database Files (Count) 6 Jetstress System Parameters Thread Count Minimum Database Cache Maximum Database Cache Insert Operations 40% Delete Operations 20% Replace Operations 5% Read Operations 35% Lazy Commits 70% Run Background Database Maintenance True Number of Copies per Database 2 6 (per database) MB MB Database Configuration Instance Log Path: K:\log11 Database: E:Jetstress edb Instance Log Path: K:\log12 Database: F:Jetstress edb Instance Log Path: K:\log13 Database: G:Jetstress edb Instance Log Path: L:\log14 Database: H:Jetstress edb Instance Log Path: L:\log15 Database: I:Jetstress edb Instance Log Path: L:\log16 Database: J:Jetstress edb MSExchange Database ==> Instances Transactional I/O Performance I/O I/O I/O Database Database Database Reads Writes Reads/sec I/O I/O Database Database Writes/sec Reads I/O Database Writes Reads Writes Reads/sec Writes/sec Writes Reads Instance Instance Instance Instance Instance Instance

18 Background Database Maintenance I/O Performance MSExchange Database ==> Database Maintenance IO Instances Reads/sec Instance Instance Instance Instance Instance Instance Database Maintenance IO Reads Log Replication I/O Performance MSExchange Database ==> Instances Reads/sec Reads Instance Instance Instance Instance Instance Instance MSExchange Database ==> Instances Total I/O Performance I/O I/O Database Database Reads Writes I/O I/O I/O Database Database Database Reads/sec Writes/sec Reads I/O Database Writes Reads Writes Reads/sec Writes/sec Reads Writes 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 Database Page Fault Stalls/sec Test Log5/5/ :55:09 AM -- Jetstress testing begins... 5/5/ :55:09 AM -- Prepare testing begins... 5/5/ :55:16 AM -- Attaching databases... 5/5/ :55:16 AM -- Prepare testing ends. 5/5/ :55:16 AM -- Dispatching transactions begins... 5/5/ :55:16 AM -- Database cache settings: (minimum: MB, maximum: 1.5 GB) 5/5/ :55:16 AM -- Database flush thresholds: (start: 15.3 MB, stop: 30.7 MB) 5/5/ :55:23 AM -- Database read latency thresholds: (average: 20 msec/read, maximum: 200 msec/read). 5/5/ :55:23 AM -- Log write latency thresholds: (average: 10 msec/write, maximum: 200 msec/write). 5/5/ :55:26 AM -- Operation mix: Sessions 6, Inserts 40%, Deletes 20%, Replaces 5%, Reads 35%, Lazy Commits 70%. 5/5/ :55:26 AM -- Performance logging begins (interval: ms). 18

19 5/5/ :55:26 AM -- Attaining prerequisites: 5/5/ :01:20 PM -- \MSExchange Database(JetstressWin)\Database Cache Size, Last: (lower bound: , upper bound: none) 5/6/ :01:21 PM -- Performance logging ends. 5/6/ :01:21 PM -- JetInterop batch transaction stats: , , , , and /6/ :01:21 PM -- Dispatching transactions ends. 5/6/ :01:21 PM -- Shutting down databases... 5/6/ :01:38 PM -- Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete) and Instance (complete) 5/6/ :01:39 PM -- Performance logging begins (interval: ms). 5/6/ :01:39 PM -- Verifying database checksums... 5/7/ :03:25 AM -- E: (100% processed), F: (100% processed), G: (100% processed), H: (100% processed), I: (100% processed) and J: (100% processed) 5/7/ :03:25 AM -- Performance logging ends. 5/7/ :03:25 AM -- C:\Program Files\Exchange Jetstress\results\DBChecksum_2010_5_6_12_1_38.blg has 1442 samples. 5/7/ :03:43 AM -- C:\Program Files\Exchange Jetstress\results\DBChecksum_2010_5_6_12_1_38.html is saved. 5/7/ :03:43 AM -- Verifying log checksums... 5/7/ :03:44 AM -- K:\log11 (12 log(s) processed), K:\log12 (12 log(s) processed), K:\log13 (12 log(s) processed), L:\log14 (12 log(s) processed), L:\log15 (12 log(s) processed) and L:\log16 (12 log(s) processed) 5/7/ :03:44 AM -- C:\Program Files\Exchange Jetstress\results\Stress_2010_5_5_11_55_23.blg has 5779 samples. 5/7/ :03:44 AM -- Creating test report... 5/7/ :04:49 AM -- Instance has 17.9 for I/O Database Reads. 5/7/ :04:49 AM -- Instance has 1.1 for Writes. 5/7/ :04:49 AM -- Instance has 1.1 for Reads. 5/7/ :04:49 AM -- Instance has 17.9 for I/O Database Reads. 5/7/ :04:49 AM -- Instance has 1.1 for Writes. 5/7/ :04:49 AM -- Instance has 1.1 for Reads. 5/7/ :04:49 AM -- Instance has 17.9 for I/O Database Reads. 5/7/ :04:49 AM -- Instance has 1.1 for Writes. 5/7/ :04:49 AM -- Instance has 1.1 for Reads. 5/7/ :04:49 AM -- Instance has 18.2 for I/O Database Reads. 5/7/ :04:49 AM -- Instance has 1.1 for Writes. 5/7/ :04:49 AM -- Instance has 1.1 for Reads. 5/7/ :04:49 AM -- Instance has 18.2 for I/O Database Reads. 5/7/ :04:49 AM -- Instance has 1.1 for Writes. 5/7/ :04:49 AM -- Instance has 1.1 for Reads. 5/7/ :04:49 AM -- Instance has 18.1 for I/O Database Reads. 5/7/ :04:49 AM -- Instance has 1.1 for Writes. 5/7/ :04:49 AM -- Instance has 1.1 for Reads. 5/7/ :04:49 AM -- Test has 0 Maximum Database Page Fault Stalls/sec. 5/7/ :04:49 AM -- Test has 0 Database Page Fault Stalls/sec samples higher than 0. 5/7/ :04:49 AM -- C:\Program Files\Exchange Jetstress\results\Stress_2010_5_5_11_55_23.xml has 5755 samples queried. 2-Hour Performance Test Results Microsoft Exchange Server Jetstress Tool - Performance Performance Test Result Report (from server ) Test Summary Overall Test Result Pass Machine Name Test Description Test Start Time Test End Time Collection Start Time Collection End Time 5/4/2010 8:37:50 PM 5/4/ :42:58 PM 5/4/2010 8:42:50 PM 5/4/ :42:43 PM 19

20 Jetstress Version Ese Version Operating System Windows Server (R) 2008 Enterprise Service Pack 2 ( ) Performance Log C:\Program Files\Exchange Jetstress\results\Performance_2010_5_4_20_38_4.blg C:\Program Files\Exchange Jetstress\results\DBChecksum_2010_5_4_22_42_58.blg Database Sizing and Throughput Achieved Transactional I/O per Second Target Transactional I/O per Second 720 Initial Database Size (bytes) Final Database Size (bytes) Database Files (Count) 6 Jetstress System Parameters Thread Count Minimum Database Cache Maximum Database Cache Insert Operations 40% Delete Operations 20% Replace Operations 5% Read Operations 35% Lazy Commits 70% Run Background Database Maintenance True Number of Copies per Database 2 6 (per database) MB MB Database Configuration Instance Log Path: K:\log11 Database: E:Jetstress edb Instance Log Path: K:\log12 Database: F:Jetstress edb Instance Log Path: K:\log13 Database: G:Jetstress edb Instance Log Path: L:\log14 Database: H:Jetstress edb Instance Log Path: L:\log15 Database: I:Jetstress edb Instance Log Path: L:\log16 Database: J:Jetstress edb 20

21 MSExchange Database ==> Instances Transactional I/O Performance I/O I/O I/O Database Database Database Reads Writes Reads/sec I/O I/O Database Database Writes/sec Reads I/O Database Writes Reads Writes Reads/sec Writes/sec Reads Writes Instance Instance Instance Instance Instance Instance Background Database Maintenance I/O Performance MSExchange Database ==> Database Maintenance IO Instances Reads/sec Instance Instance Instance Instance Instance Instance Database Maintenance IO Reads Log Replication I/O Performance MSExchange Database ==> Instances Reads/sec Reads Instance Instance Instance Instance Instance Instance MSExchange Database ==> Instances Total I/O Performance I/O I/O Database Database Reads Writes I/O I/O I/O Database Database Database Reads/sec Writes/sec Reads I/O Database Writes Reads Writes Reads/sec Writes/sec Reads Writes 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 Database Page Fault Stalls/sec

22 Test Log5/4/2010 8:37:50 PM -- Jetstress testing begins... 5/4/2010 8:37:50 PM -- Prepare testing begins... 5/4/2010 8:37:57 PM -- Attaching databases... 5/4/2010 8:37:57 PM -- Prepare testing ends. 5/4/2010 8:37:57 PM -- Dispatching transactions begins... 5/4/2010 8:37:57 PM -- Database cache settings: (minimum: MB, maximum: 1.5 GB) 5/4/2010 8:37:57 PM -- Database flush thresholds: (start: 15.3 MB, stop: 30.7 MB) 5/4/2010 8:38:04 PM -- Database read latency thresholds: (average: 20 msec/read, maximum: 100 msec/read). 5/4/2010 8:38:04 PM -- Log write latency thresholds: (average: 10 msec/write, maximum: 100 msec/write). 5/4/2010 8:38:06 PM -- Operation mix: Sessions 6, Inserts 40%, Deletes 20%, Replaces 5%, Reads 35%, Lazy Commits 70%. 5/4/2010 8:38:06 PM -- Performance logging begins (interval: ms). 5/4/2010 8:38:06 PM -- Attaining prerequisites: 5/4/2010 8:42:50 PM -- \MSExchange Database(JetstressWin)\Database Cache Size, Last: (lower bound: , upper bound: none) 5/4/ :42:51 PM -- Performance logging ends. 5/4/ :42:51 PM -- JetInterop batch transaction stats: 33106, 33015, 33178, 32966, and /4/ :42:51 PM -- Dispatching transactions ends. 5/4/ :42:51 PM -- Shutting down databases... 5/4/ :42:58 PM -- Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete) and Instance (complete) 5/4/ :42:59 PM -- Performance logging begins (interval: ms). 5/4/ :42:59 PM -- Verifying database checksums... 5/5/2010 9:57:36 AM -- E: (100% processed), F: (100% processed), G: (100% processed), H: (100% processed), I: (100% processed) and J: (100% processed) 5/5/2010 9:57:36 AM -- Performance logging ends. 5/5/2010 9:57:36 AM -- C:\Program Files\Exchange Jetstress\results\DBChecksum_2010_5_4_22_42_58.blg has 1348 samples. 5/5/2010 9:57:52 AM -- C:\Program Files\Exchange Jetstress\results\DBChecksum_2010_5_4_22_42_58.html is saved. 5/5/2010 9:57:52 AM -- Verifying log checksums... 5/5/2010 9:57:53 AM -- K:\log11 (12 log(s) processed), K:\log12 (13 log(s) processed), K:\log13 (12 log(s) processed), L:\log14 (12 log(s) processed), L:\log15 (13 log(s) processed) and L:\log16 (13 log(s) processed) 5/5/2010 9:57:53 AM -- C:\Program Files\Exchange Jetstress\results\Performance_2010_5_4_20_38_4.blg has 498 samples. 5/5/2010 9:57:53 AM -- Creating test report... 5/5/2010 9:57:59 AM -- Instance has 17.3 for I/O Database Reads. 5/5/2010 9:57:59 AM -- Instance has 1.1 for Writes. 5/5/2010 9:57:59 AM -- Instance has 1.1 for Reads. 5/5/2010 9:57:59 AM -- Instance has 17.3 for I/O Database Reads. 5/5/2010 9:57:59 AM -- Instance has 1.1 for Writes. 5/5/2010 9:57:59 AM -- Instance has 1.1 for Reads. 5/5/2010 9:57:59 AM -- Instance has 17.3 for I/O Database Reads. 5/5/2010 9:57:59 AM -- Instance has 1.1 for Writes. 5/5/2010 9:57:59 AM -- Instance has 1.1 for Reads. 5/5/2010 9:57:59 AM -- Instance has 18.4 for I/O Database Reads. 5/5/2010 9:57:59 AM -- Instance has 1.1 for Writes. 5/5/2010 9:57:59 AM -- Instance has 1.1 for Reads. 5/5/2010 9:57:59 AM -- Instance has 18.5 for I/O Database Reads. 5/5/2010 9:57:59 AM -- Instance has 1.1 for Writes. 5/5/2010 9:57:59 AM -- Instance has 1.1 for Reads. 5/5/2010 9:57:59 AM -- Instance has 18.4 for I/O Database Reads. 5/5/2010 9:57:59 AM -- Instance has 1.1 for Writes. 5/5/2010 9:57:59 AM -- Instance has 1.1 for Reads. 5/5/2010 9:57:59 AM -- Test has 0 Maximum Database Page Fault Stalls/sec. 5/5/2010 9:57:59 AM -- Test has 0 Database Page Fault Stalls/sec samples higher than 0. 5/5/2010 9:57:59 AM -- C:\Program Files\Exchange Jetstress\results\Performance_2010_5_4_20_38_4.xml has 479 samples queried. 22

23 Database Backup Test Results Microsoft Exchange Server Jetstress Tool Database Backup Database backup Test Result Report (from server ) Database Backup Statistics - All Database Instance Database Size (M) Elapsed Backup Time M Transferred/sec Instance :13: Instance :13: Instance :10: Instance :02: Instance :59: Instance :58: Jetstress System Parameters Thread Count 6 (per database) Minimum Database Cache MB Maximum Database Cache MB Insert Operations 40% Delete Operations 20% Replace Operations 5% Read Operations 35% Lazy Commits 70% Database Configuration Instance Log Path: K:\log11 Database: E:Jetstress edb Instance Log Path: K:\log12 Database: F:Jetstress edb Instance Log Path: K:\log13 Database: G:Jetstress edb Instance Log Path: L:\log14 Database: H:Jetstress edb Instance Log Path: L:\log15 Database: I:Jetstress edb Instance Log Path: L:\log16 Database: J:Jetstress edb MSExchange Database ==> Instances Transactional I/O Performance I/O I/O I/O Database Database Database Reads Writes Reads/sec I/O I/O Database Database Writes/sec Reads I/O Database Writes Reads Writes Reads/sec Writes/sec Reads Instance Instance Instance Instance Instance Instance Writes 23

24 Host System Performance Counter Minimum Maximum % Processor Time Available M Free System Page Table Entries Transition Pages RePurposed/sec Pool Nonpaged Pool Paged Database Page Fault Stalls/sec Test Log5/7/2010 5:18:14 AM -- Jetstress testing begins... 5/7/2010 5:18:14 AM -- Prepare testing begins... 5/7/2010 5:18:21 AM -- Attaching databases... 5/7/2010 5:18:21 AM -- Prepare testing ends. 5/7/2010 5:18:29 AM -- Performance logging begins (interval: ms). 5/7/2010 5:18:29 AM -- Backing up databases... 5/7/2010 8:32:18 PM -- Performance logging ends. 5/7/2010 8:32:18 PM -- Instance (100% processed), Instance (100% processed), Instance (100% processed), Instance (100% processed), Instance (100% processed) and Instance (100% processed) 5/7/2010 8:32:18 PM -- C:\Program Files\Exchange Jetstress\results\DatabaseBackup_2010_5_7_5_18_21.blg has 1826 samples. 5/7/2010 8:32:18 PM -- Creating test report... Soft Recovery Test Results Microsoft Exchange Server Jetstress Tool Soft Recovery SoftRecovery Test Result Report (from server ) Soft-Recovery Statistics - All Database Instance Log files replayed Elapsed seconds Instance Instance Instance Instance Instance Instance Database Configuration Instance Log Path: K:\log11 Database: E:Jetstress edb Instance Log Path: K:\log12 Database: F:Jetstress edb Instance Log Path: K:\log13 Database: G:Jetstress edb Instance Log Path: L:\log14 Database: H:Jetstress edb Instance Log Path: L:\log15 Database: I:Jetstress edb Instance Log Path: L:\log16 24

25 Database: J:Jetstress edb MSExchange Database ==> Instances Transactional I/O Performance I/O I/O I/O Database Database Database Reads Writes Reads/sec I/O I/O Database Database Writes/sec Reads I/O Database Writes Reads Writes Reads/sec Writes/sec Reads Instance Instance Instance Instance Instance Instance Writes Background Database Maintenance I/O Performance MSExchange Database ==> Database Maintenance IO Instances Reads/sec Instance Instance Instance Instance Instance Instance Database Maintenance IO Reads MSExchange Database ==> Instances Total I/O Performance I/O I/O Database Database Reads Writes I/O I/O I/O Database Database Database Reads/sec Writes/sec Reads I/O Database Writes Reads Writes Reads/sec Writes/sec Reads Instance Instance Instance Instance Instance Instance Writes Host System Performance Counter Minimum Maximum % Processor Time Available M Free System Page Table Entries Transition Pages RePurposed/sec Pool Nonpaged Pool Paged Database Page Fault Stalls/sec Test Log5/8/ :35:06 PM -- Jetstress testing begins... 5/8/ :35:06 PM -- Prepare testing begins... 5/8/ :35:12 PM -- Attaching databases... 5/8/ :35:12 PM -- Prepare testing ends. 5/8/ :35:12 PM -- Dispatching transactions begins... 5/8/ :35:12 PM -- Database cache settings: (minimum: MB, maximum: 1.5 GB) 5/8/ :35:12 PM -- Database flush thresholds: (start: 15.3 MB, stop: 30.7 MB) 5/8/ :35:19 PM -- Database read latency thresholds: (average: 20 msec/read, maximum:

26 msec/read). 5/8/ :35:19 PM -- Log write latency thresholds: (average: 10 msec/write, maximum: 100 msec/write). 5/8/ :35:21 PM -- Operation mix: Sessions 6, Inserts 40%, Deletes 20%, Replaces 5%, Reads 35%, Lazy Commits 70%. 5/8/ :35:21 PM -- Performance logging begins (interval: ms). 5/8/ :35:21 PM -- Generating log files... 5/8/2010 1:59:18 PM -- K:\log11 (100.4% generated), K:\log12 (101.0% generated), K:\log13 (100.2% generated), L:\log14 (104.4% generated), L:\log15 (102.8% generated) and L:\log16 (102.4% generated) 5/8/2010 1:59:18 PM -- Performance logging ends. 5/8/2010 1:59:18 PM -- JetInterop batch transaction stats: 21380, 21484, 21452, 21998, and /8/2010 1:59:18 PM -- Dispatching transactions ends. 5/8/2010 1:59:18 PM -- Shutting down databases... 5/8/2010 1:59:23 PM -- Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete) and Instance (complete) 5/8/2010 1:59:23 PM -- C:\Program Files\Exchange Jetstress\results\Performance_2010_5_8_12_35_19.blg has 335 samples. 5/8/2010 1:59:23 PM -- Creating test report... 5/8/2010 1:59:26 PM -- Instance has 22.9 for I/O Database Reads. 5/8/2010 1:59:26 PM -- Instance has 0.9 for Writes. 5/8/2010 1:59:26 PM -- Instance has 0.9 for Reads. 5/8/2010 1:59:26 PM -- Instance has 22.8 for I/O Database Reads. 5/8/2010 1:59:26 PM -- Instance has 0.9 for Writes. 5/8/2010 1:59:26 PM -- Instance has 0.9 for Reads. 5/8/2010 1:59:26 PM -- Instance has 22.9 for I/O Database Reads. 5/8/2010 1:59:26 PM -- Instance has 0.9 for Writes. 5/8/2010 1:59:26 PM -- Instance has 0.9 for Reads. 5/8/2010 1:59:26 PM -- Instance has 25.6 for I/O Database Reads. 5/8/2010 1:59:26 PM -- Instance has 1.0 for Writes. 5/8/2010 1:59:26 PM -- Instance has 1.0 for Reads. 5/8/2010 1:59:26 PM -- Instance has 25.8 for I/O Database Reads. 5/8/2010 1:59:26 PM -- Instance has 1.0 for Writes. 5/8/2010 1:59:26 PM -- Instance has 1.0 for Reads. 5/8/2010 1:59:26 PM -- Instance has 25.7 for I/O Database Reads. 5/8/2010 1:59:26 PM -- Instance has 1.0 for Writes. 5/8/2010 1:59:26 PM -- Instance has 1.0 for Reads. 5/8/2010 1:59:26 PM -- Test has 0 Maximum Database Page Fault Stalls/sec. 5/8/2010 1:59:26 PM -- Test has 0 Database Page Fault Stalls/sec samples higher than 0. 5/8/2010 1:59:26 PM -- C:\Program Files\Exchange Jetstress\results\Performance_2010_5_8_12_35_19.xml has 334 samples queried. 5/8/2010 1:59:26 PM -- C:\Program Files\Exchange Jetstress\results\Performance_2010_5_8_12_35_19.html is saved. 5/8/2010 1:59:29 PM -- Performance logging begins (interval: 4000 ms). 5/8/2010 1:59:29 PM -- Recovering databases... 5/8/2010 2:07:43 PM -- Performance logging ends. 5/8/2010 2:07:43 PM -- Instance ( ), Instance ( ), Instance ( ), Instance ( ), Instance ( ) and Instance ( ) 5/8/2010 2:07:43 PM -- C:\Program Files\Exchange Jetstress\results\SoftRecovery_2010_5_8_13_59_26.blg has 123 samples. 5/8/2010 2:07:43 PM -- Creating test report NetApp All rights reserved. Specifications subject to change without notice. NetApp, the NetApp logo, Data ONTAP, SnapManager, SnapDrive, and FlexVol are registered trademarks and NetApp, FlexClone, RAID-DP, and Snapshot are trademarks of NetApp in the U.S. and other countries. Intel is a registered trademark of Intel Corporation. Microsoft and Windows are registered trademarks of Microsoft Corporation. All other brands or products are trademarks or registered trademarks of their respective holders and should be treated as such. 26