Netapp and Exchange

NetApp FAS3140 12000 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) .............................. 10

Storage Disk Configuration (Transactional Log Disks Utilizing Same Disks

as Mailbox Store Database) ............................................................ 10

Best Practices ..................................................................................... 10

Mailbox Resiliency ............................................................................ 11

Backup strategy ............................................................................... 12

Contact for Additional Information ........................................................ 12

Test Result Summary .......................................................................... 12

Reliability ........................................................................................ 12

Storage Performance Results ............................................................. 12

Database Backup/Recovery Performance ............................................ 14

Database Read-only Performance .................................................... 14

Transaction Log Recovery/Replay Performance ................................. 14

Conclusion ......................................................................................... 14

Appendix A – Test Results .................................................................... 15

24-Hour Stress/Reliability Test Results ............................................... 15

2-Hour Performance Test Results ....................................................... 19

Database Backup Test Results ........................................................... 23

Soft Recovery Test Results ................................................................ 24

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 http://technet.microsoft.com/en-us/exchange/ff182054.aspx

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:

4

• Thin provisioning helps avoid the costly over provisioning and time-

consuming 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.

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® 7.3.2

� SATA disk shelves, 1 TB 7.2K RPM drives

� Link to FAS3140 Windows Server Catalog listing: http://www.windowsservercatalog.com/item.aspx?idItem=b79e68ad-68ef-2f36-d338-8403c10f398d&bCatID=1511

Switches:

� A pair of Brocade 4100 4Gbps 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: fas3140-9 and fas3140-10. The

first Exchange data copy (active copy) is on fas3140-9. The second Exchange data copy (passive copy) is on fas3140-10.

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 fas3140-9 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.

7

For Mailbox Resiliency configuration, databases and log files can be placed on the same set of disk drives (see http://technet.microsoft.com/en-

us/library/ee832792.aspx). 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

Aggregate Volume LUN RAID

Type

Number

of Data

Drives

Number

of Parity

Drives

Number of

LUNs

fas3140-9

aggr1

db11_fv DB11

RAID-DP 14 2 3 x 2.08TB

+ 1x 100GB

db12_fv DB12

db13_fv DB13 log1_fv LOG1

aggr2

db14_fv DB14

RAID-DP 14 2 3 x 2.08TB

+ 1x 100GB

db15_fv DB15

db16_fv DB16

log2_fv LOG2

aggr3

db21_fv DB21

RAID-DP 14 2 3 x 2.08TB

+ 1x 100GB

db22_fv DB22

db23_fv DB23

log3_fv LOG3

aggr4

db24_fv DB24

RAID-DP 14 2 3 x 2.08TB

+ 1x 100GB

db25_fv DB25

db26_fv DB26

log4_fv LOG4

The DAG configuration is as follows:

� Four mailbox servers: 3650-1, 3650-2, 3650-3 and 3650-4

� 1000 mailboxes per database

� Twelve active databases total:

o DB11 to DB16 hosted by 3650-1

o DB21 to DB26 hosted by 3650-3

� Twelve passive databases total (shown in gray in Figure 1): hosted by

3650-2 and 3650-4. All passive databases are on separate aggregates

and on the separate but identical storage controller: fas3140-10

� 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,

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

http://go.microsoft.com/fwlink/?LinkId=23454.

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)

• 0.100 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 simulated

12,000

Number of Database Availability Groups (DAGs)

2

Number of servers/DAG 2

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% headroom)

0.120 IOPs per mailbox (0.10 IOPs

plus 20% headroom added)

Database LUN size 2.08 TB

Log LUN size 100 GB

Total database size for performance testing

23,438 GB

% storage capacity used by Exchange database**

92%

**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)

Fibre Channel SAN

Storage model and OS/firmware revision

FAS3140 Data ONTAP 7.3.2

Storage cache 4 GB, plus 256GB Flash Cache

Number of storage controllers 2 (1 tested)

Number of storage ports 8 (4 tested)

Maximum bandwidth of storage connectivity to host

32 Gbps (8 x 4 Gb/sec per port)

Switch type/model/firmware revision Brocade 4100 FC Switch, v6.1.1b

HBA model and firmware Emulex LP11002, v2.72a2

Number of HBA’s/host 2 per host

Host server type IBM x3650, 4 x 3.6 GHz CPU, 18 GB

RAM

Total number of disks tested in

solution

64

Maximum number of spindles can be

hosted in the storage

420

Storage Software

HBA driver STOR miniport v2.20.006

HBA QueueTarget Setting N/A

HBA QueueDepth Setting 254

Multi-Pathing Data ONTAP DSM 3.3.1 for Windows

MPIO

10

Host OS Windows Server 2008 Enterprise SP2

ESE.dll file version 14.00.0639.019

Replication solution name/version N/A

Storage Disk Configuration (Mailbox Store Disks)

Disk type, speed and firmware revision

SATA 1TB 7.2K RPM – FW NA00

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 of disks per LUN

Four aggregates consisting of one 16-disk RAID-DP groups for both

database and log files

Raid level RAID-DP

Total formatted capacity 24.96 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

SATA 1TB 7.2K RPM – FW NA00

Raw capacity per disk (GB) 1 TB

Number of Spindles in test 64 (same as mailbox store disks)

total raw storage capacity (GB) 64 TB

Disk slice size (GB) N/A

Number of slices per LUN or number of disks per LUN

Four aggregate consisting of one 16-disk RAID-DP groups both database and log files

Raid level RAID-DP

Total formatted capacity 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.

11

For Exchange 2010 best practices on storage design, please visit http://technet.microsoft.com/en-us/library/dd346703.aspx

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.

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

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 3650-1

Database I/O

Database Disks Transfers/sec 877

Database Disks Reads/sec 559

Database Disks Writes/sec 319

Average Database Disk Read Latency (ms) 17.88

Average Database Disk Write Latency (ms) 3.82

Transaction Log I/O

Log Disks Writes/sec 294

Average Log Disk Write Latency (ms) 1.06

Host 3650-3

Database I/O






Transaction Log I/O



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






Transaction Log I/O



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 3650-1

MB read/sec per database 36.78

MB read/sec total per server 220.65

Host 3650-3

MB read/sec per database 36.65

MB read/sec total per server 219.88

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 3650-1

Average time to play one Log file (sec) 0.953

Host 3650-3

Average time to play one Log file (sec) 0.946

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

0.120 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

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: 3650-1. 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 3650-1) Checksum Statistics - All

Database Seen pages

Bad pages

Correctable pages

Wrong page-number pages

File length / seconds taken

E:Jetstress001001.edb 64159858 0 0 0 2004995 MBytes / 43305 sec

F:Jetstress002001.edb 64158578 0 0 0 2004955 MBytes / 43173 sec

G:Jetstress003001.edb 64159346 0 0 0 2004979 MBytes / 42823 sec

H:Jetstress004001.edb 64159090 0 0 0 2004971 MBytes / 41053 sec

I:Jetstress005001.edb 64159090 0 0 0 2004971 MBytes / 41050 sec

J:Jetstress006001.edb 64158578 0 0 0 2004955 MBytes / 41048 sec

(Sum) 384954540 0 0 0 12029829 MBytes / 43305 sec

Disk Subsystem Performance (of checksum)

LogicalDisk Avg. Disk sec/Read

Avg. Disk sec/Write

Disk Reads/sec

Disk Writes/sec

Avg. Disk Bytes/Read

E: 0.060 0.000 740.587 0.000 65536.000

F: 0.061 0.000 742.933 0.000 65536.000

G: 0.060 0.000 749.106 0.000 65536.000

H: 0.057 0.000 781.542 0.000 65536.000

I: 0.058 0.000 781.603 0.000 65536.000

J: 0.057 0.000 781.633 0.000 65536.000

16

Memory System Performance (of checksum)

Counter Average Minimum Maximum

% Processor Time 10.776 1.845 13.669

Available MBytes 16736.019 16618.000 16833.000

Free System Page Table Entries 33558817.865 33558422.000 33559311.000

Transition Pages RePurposed/sec 0.000 0.000 0.000

Pool Nonpaged Bytes 53390141.426 53301248.000 53891072.000

Pool Paged Bytes 122809112.499 121987072.000 162570240.000

Test Log5/5/2010 11:55:09 AM -- Jetstress testing begins ... 5/5/2010 11:55:09 AM -- Prepare testing begins ... 5/5/2010 11:55:16 AM -- Attaching databases ... 5/5/2010 11:55:16 AM -- Prepare testing ends. 5/5/2010 11:55:16 AM -- Dispatching transactions begins ... 5/5/2010 11:55:16 AM -- Database cache settings: (minimum: 192.0 MB, maximum: 1.5 GB) 5/5/2010 11:55:16 AM -- Database flush thresholds: (start: 15.3 MB, stop: 30.7 MB) 5/5/2010 11:55:23 AM -- Database read latency thresholds: (average: 20 msec/read, maximum: 200 msec/read). 5/5/2010 11:55:23 AM -- Log write latency thresholds: (average: 10 msec/write, maximum: 200 msec/write). 5/5/2010 11:55:26 AM -- Operation mix: Sessions 6, Inserts 40%, Deletes 20%, Replaces 5%, Reads 35%, Lazy Commits 70%. 5/5/2010 11:55:26 AM -- Performance logging begins (interval: 15000 ms). 5/5/2010 11:55:26 AM -- Attaining prerequisites: 5/5/2010 12:01:20 PM -- \MSExchange Database(JetstressWin)\Database Cache Size, Last: 1452159000.0 (lower bound: 1449551000.0, upper bound: none) 5/6/2010 12:01:21 PM -- Performance logging ends. 5/6/2010 12:01:21 PM -- JetInterop batch transaction stats: 370192, 369379, 369441, 368985, 368838 and 369623. 5/6/2010 12:01:21 PM -- Dispatching transactions ends. 5/6/2010 12:01:21 PM -- Shutting down databases ... 5/6/2010 12:01:38 PM -- Instance2700.1 (complete), Instance2700.2 (complete), Instance2700.3 (complete), Instance2700.4 (complete), Instance2700.5 (complete) and Instance2700.6 (complete) 5/6/2010 12:01:39 PM -- Performance logging begins (interval: 30000 ms). 5/6/2010 12:01:39 PM -- Verifying database checksums ... 5/7/2010 12:03:25 AM -- E: (100% processed), F: (100% processed), G: (100% processed), H: (100% processed), I: (100% processed) and J: (100% processed) 5/7/2010 12:03:25 AM -- Performance logging ends. 5/7/2010 12: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 3650-1) Test Summary

Overall Test Result Pass

Machine Name 3650-1

Test Description

Test Start Time 5/5/2010 11:55:09 AM

Test End Time 5/6/2010 12:01:38 PM

Collection Start Time 5/5/2010 12:01:20 PM

Collection End Time 5/6/2010 12:01:13 PM

Jetstress Version 14.01.0043.000

Ese Version 14.00.0639.019

Operating System Windows Server (R) 2008 Enterprise Service Pack 2 (6.0.6002.131072)

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

17

Database Sizing and Throughput

Achieved Transactional I/O per Second 887.372

Target Transactional I/O per Second 720

Initial Database Size (bytes) 12582984744960

Final Database Size (bytes) 12614190366720

Database Files (Count) 6

Jetstress System Parameters

Thread Count 6 (per database)

Minimum Database Cache 192.0 MB

Maximum Database Cache 1536.0 MB

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

Database Configuration

Instance2700.1 Log Path: K:\log11 Database: E:Jetstress001001.edb

Instance2700.2 Log Path: K:\log12 Database: F:Jetstress002001.edb

Instance2700.3 Log Path: K:\log13 Database: G:Jetstress003001.edb

Instance2700.4 Log Path: L:\log14 Database: H:Jetstress004001.edb

Instance2700.5 Log Path: L:\log15 Database: I:Jetstress005001.edb

Instance2700.6 Log Path: L:\log16 Database: J:Jetstress006001.edb

Transactional I/O Performance

MSExchange

Database ==>

Instances

I/O

Database

Reads

Average

Latency

(msec)

I/O

Database

Writes

Average

Latency

(msec)

I/O

Database

Reads/sec

I/O

Database

Writes/sec

I/O

Database

Reads

Average

Bytes

I/O

Database

Writes

Average

Bytes

I/O Log

Reads

Average

Latency

(msec)

I/O Log

Writes

Average

Latency

(msec)

I/O Log

Reads/sec

I/O Log

Writes/sec

I/O Log

Reads

Average

Bytes

I/O Log Writes

Average Bytes

Instance2700.1 17.938 5.518 93.694 54.635 34097.523 35851.676 0.000 1.137 0.000 46.612 0.000 4729.000

Instance2700.2 17.923 4.974 93.260 54.334 34147.095 35858.225 0.000 1.138 0.000 46.405 0.000 4711.300

Instance2700.3 17.904 4.428 93.392 54.444 34093.691 35860.498 0.000 1.139 0.000 46.566 0.000 4722.765

Instance2700.4 18.190 3.843 93.572 54.560 34090.691 35854.858 0.000 1.139 0.000 46.589 0.000 4719.087

Instance2700.5 18.170 3.240 93.419 54.440 34130.831 35850.817 0.000 1.140 0.000 46.568 0.000 4718.353

Instance2700.6 18.120 2.661 93.262 54.360 34105.041 35850.405 0.000 1.139 0.000 46.476 0.000 4722.985

18

Background Database Maintenance I/O Performance

MSExchange Database ==> Instances

Database Maintenance IO Reads/sec

Database Maintenance IO Reads Average Bytes

Instance2700.1 30.930 261945.407

Instance2700.2 30.970 261948.267

Instance2700.3 31.004 261941.772

Instance2700.4 31.042 261950.350

Instance2700.5 31.061 261944.120

Instance2700.6 31.115 261942.961

Log Replication I/O Performance

MSExchange Database ==> Instances I/O Log Reads/sec I/O Log Reads Average Bytes

Instance2700.1 0.895 231260.007

Instance2700.2 0.888 231180.212

Instance2700.3 0.893 231598.063

Instance2700.4 0.893 231621.880

Instance2700.5 0.892 231689.241

Instance2700.6 0.891 231627.836

Total I/O Performance

MSExchange

Database ==>

Instances

I/O

Database

Reads Average

Latency

(msec)

I/O

Database

Writes Average

Latency

(msec)

I/O

Database

Reads/sec

I/O

Database

Writes/sec

I/O

Database

Reads Average

Bytes

I/O

Database

Writes Average

Bytes

I/O Log

Reads

Average Latency

(msec)

I/O Log

Writes

Average Latency

(msec)

I/O Log

Reads/sec

I/O Log

Writes/sec

I/O Log

Reads

Average Bytes

I/O Log

Writes

Average Bytes

Instance2700.1 17.938 5.518 124.624 54.635 90646.043 35851.676 14.420 1.137 0.895 46.612 231260.007 4729.000

Instance2700.2 17.923 4.974 124.230 54.334 90937.234 35858.225 14.424 1.138 0.888 46.405 231180.212 4711.300

Instance2700.3 17.904 4.428 124.396 54.444 90881.530 35860.498 14.466 1.139 0.893 46.566 231598.063 4722.765

Instance2700.4 18.190 3.843 124.614 54.560 90852.135 35854.858 13.729 1.139 0.893 46.589 231621.880 4719.087

Instance2700.5 18.170 3.240 124.480 54.440 90975.644 35850.817 13.642 1.140 0.892 46.568 231689.241 4718.353

Instance2700.6 18.120 2.661 124.377 54.360 91102.749 35850.405 13.639 1.139 0.891 46.476 231627.836 4722.985

Host System Performance


% Processor Time 3.060 0.962 16.796





Pool Paged Bytes 123353453.765 122716160.000 163586048.000

Database Page Fault Stalls/sec 0.000 0.000 0.000

Test Log5/5/2010 11:55:09 AM -- Jetstress testing begins ... 5/5/2010 11:55:09 AM -- Prepare testing begins ... 5/5/2010 11:55:16 AM -- Attaching databases ... 5/5/2010 11:55:16 AM -- Prepare testing ends. 5/5/2010 11:55:16 AM -- Dispatching transactions begins ... 5/5/2010 11:55:16 AM -- Database cache settings: (minimum: 192.0 MB, maximum: 1.5 GB) 5/5/2010 11:55:16 AM -- Database flush thresholds: (start: 15.3 MB, stop: 30.7 MB) 5/5/2010 11:55:23 AM -- Database read latency thresholds: (average: 20 msec/read, maximum: 200 msec/read). 5/5/2010 11:55:23 AM -- Log write latency thresholds: (average: 10 msec/write, maximum: 200 msec/write). 5/5/2010 11:55:26 AM -- Operation mix: Sessions 6, Inserts 40%, Deletes 20%, Replaces 5%, Reads 35%, Lazy Commits 70%. 5/5/2010 11:55:26 AM -- Performance logging begins (interval: 15000 ms).

19

5/5/2010 11:55:26 AM -- Attaining prerequisites: 5/5/2010 12:01:20 PM -- \MSExchange Database(JetstressWin)\Database Cache Size, Last: 1452159000.0 (lower bound: 1449551000.0, upper bound: none) 5/6/2010 12:01:21 PM -- Performance logging ends. 5/6/2010 12:01:21 PM -- JetInterop batch transaction stats: 370192, 369379, 369441, 368985, 368838 and 369623. 5/6/2010 12:01:21 PM -- Dispatching transactions ends. 5/6/2010 12:01:21 PM -- Shutting down databases ... 5/6/2010 12:01:38 PM -- Instance2700.1 (complete), Instance2700.2 (complete), Instance2700.3 (complete), Instance2700.4 (complete), Instance2700.5 (complete) and Instance2700.6 (complete) 5/6/2010 12:01:39 PM -- Performance logging begins (interval: 30000 ms). 5/6/2010 12:01:39 PM -- Verifying database checksums ... 5/7/2010 12:03:25 AM -- E: (100% processed), F: (100% processed), G: (100% processed), H: (100% processed), I: (100% processed) and J: (100% processed) 5/7/2010 12:03:25 AM -- Performance logging ends. 5/7/2010 12:03:25 AM -- C:\Program Files\Exchange Jetstress\results\DBChecksum_2010_5_6_12_1_38.blg has 1442 samples. 5/7/2010 12:03:43 AM -- C:\Program Files\Exchange Jetstress\results\DBChecksum_2010_5_6_12_1_38.html is saved. 5/7/2010 12:03:43 AM -- Verifying log checksums ... 5/7/2010 12: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/2010 12:03:44 AM -- C:\Program Files\Exchange Jetstress\results\Stress_2010_5_5_11_55_23.blg has 5779 samples. 5/7/2010 12:03:44 AM -- Creating test report ... 5/7/2010 12:04:49 AM -- Instance2700.1 has 17.9 for I/O Database Reads Average Latency. 5/7/2010 12:04:49 AM -- Instance2700.1 has 1.1 for I/O Log Writes Average Latency. 5/7/2010 12:04:49 AM -- Instance2700.1 has 1.1 for I/O Log Reads Average Latency. 5/7/2010 12:04:49 AM -- Instance2700.2 has 17.9 for I/O Database Reads Average Latency. 5/7/2010 12:04:49 AM -- Instance2700.2 has 1.1 for I/O Log Writes Average Latency. 5/7/2010 12:04:49 AM -- Instance2700.2 has 1.1 for I/O Log Reads Average Latency. 5/7/2010 12:04:49 AM -- Instance2700.3 has 17.9 for I/O Database Reads Average Latency. 5/7/2010 12:04:49 AM -- Instance2700.3 has 1.1 for I/O Log Writes Average Latency. 5/7/2010 12:04:49 AM -- Instance2700.3 has 1.1 for I/O Log Reads Average Latency. 5/7/2010 12:04:49 AM -- Instance2700.4 has 18.2 for I/O Database Reads Average Latency. 5/7/2010 12:04:49 AM -- Instance2700.4 has 1.1 for I/O Log Writes Average Latency. 5/7/2010 12:04:49 AM -- Instance2700.4 has 1.1 for I/O Log Reads Average Latency. 5/7/2010 12:04:49 AM -- Instance2700.5 has 18.2 for I/O Database Reads Average Latency. 5/7/2010 12:04:49 AM -- Instance2700.5 has 1.1 for I/O Log Writes Average Latency. 5/7/2010 12:04:49 AM -- Instance2700.5 has 1.1 for I/O Log Reads Average Latency. 5/7/2010 12:04:49 AM -- Instance2700.6 has 18.1 for I/O Database Reads Average Latency. 5/7/2010 12:04:49 AM -- Instance2700.6 has 1.1 for I/O Log Writes Average Latency. 5/7/2010 12:04:49 AM -- Instance2700.6 has 1.1 for I/O Log Reads Average Latency. 5/7/2010 12:04:49 AM -- Test has 0 Maximum Database Page Fault Stalls/sec. 5/7/2010 12:04:49 AM -- Test has 0 Database Page Fault Stalls/sec samples higher than 0. 5/7/2010 12: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 3650-1) Test Summary

Overall Test Result Pass

Machine Name 3650-1

Test Description

Test Start Time 5/4/2010 8:37:50 PM

Test End Time 5/4/2010 10:42:58 PM

Collection Start Time 5/4/2010 8:42:50 PM

Collection End Time 5/4/2010 10:42:43 PM

20

Jetstress Version 14.01.0043.000

Ese Version 14.00.0639.019

Operating System Windows Server (R) 2008 Enterprise Service Pack 2 (6.0.6002.131072)

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 877.233

Target Transactional I/O per Second 720

Initial Database Size (bytes) 12582984744960

Final Database Size (bytes) 12585727819776

Database Files (Count) 6








Read Operations 35%

Lazy Commits 70%

Run Background Database Maintenance True

Number of Copies per Database 2








21


MSExchange

Database ==>

Instances

I/O

Database

Reads

Average

Latency

(msec)

I/O

Database

Writes

Average

Latency

(msec)

I/O

Database

Reads/sec

I/O

Database

Writes/sec

I/O

Database

Reads

Average

Bytes

I/O

Database

Writes

Average

Bytes

I/O Log

Reads

Average

Latency

(msec)

I/O Log

Writes

Average

Latency

(msec)

I/O Log

Reads/sec

I/O Log

Writes/sec

I/O Log

Reads

Average

Bytes

I/O Log

Writes

Average

Bytes

Instance3216.1 17.344 5.196 93.130 53.119 34588.058 37085.364 0.000 1.059 0.000 48.926 0.000 4776.380

Instance3216.2 17.346 4.663 93.240 53.199 34728.030 37078.454 0.000 1.060 0.000 49.199 0.000 4729.465

Instance3216.3 17.315 4.125 93.609 53.325 34524.057 37089.171 0.000 1.059 0.000 49.188 0.000 4733.737

Instance3216.4 18.445 3.506 92.802 52.901 34441.809 36943.409 0.000 1.056 0.000 48.804 0.000 4711.837

Instance3216.5 18.458 2.968 92.987 53.011 34561.257 37050.694 0.000 1.071 0.000 48.849 0.000 4693.622

Instance3216.6 18.382 2.437 92.921 52.989 34396.295 37055.170 0.000 1.076 0.000 48.844 0.000 4708.106





Instance3216.1 31.239 261957.568

Instance3216.2 31.259 261991.118

Instance3216.3 31.295 261956.547

Instance3216.4 31.331 261944.212

Instance3216.5 31.353 261953.178

Instance3216.6 31.387 261927.999

Log Replication I/O Performance

MSExchange Database ==> Instances I/O Log Reads/sec I/O Log Reads Average Bytes

Instance3216.1 0.949 231574.061

Instance3216.2 0.946 232019.297

Instance3216.3 0.946 231079.702

Instance3216.4 0.935 230069.392

Instance3216.5 0.929 232532.134

Instance3216.6 0.934 232020.776


MSExchange

Database ==> Instances

I/O

Database Reads

Average

Latency

(msec)

I/O

Database Writes

Average

Latency

(msec)

I/O

Database Reads/sec

I/O

Database Writes/sec

I/O

Database Reads

Average

Bytes

I/O

Database Writes

Average

Bytes

I/O Log

Reads Average

Latency

(msec)

I/O Log

Writes Average

Latency

(msec)

I/O Log

Reads/sec

I/O Log

Writes/sec

I/O Log

Reads Average

Bytes

I/O Log

Writes Average

Bytes

Instance3216.1 17.344 5.196 124.369 53.119 91698.202 37085.364 12.061 1.059 0.949 48.926 231574.061 4776.380

Instance3216.2 17.346 4.663 124.499 53.199 91789.135 37078.454 11.818 1.060 0.946 49.199 232019.297 4729.465

Instance3216.3 17.315 4.125 124.904 53.325 91507.962 37089.171 12.130 1.059 0.946 49.188 231079.702 4733.737

Instance3216.4 18.445 3.506 124.133 52.901 91863.223 36943.409 11.797 1.056 0.935 48.804 230069.392 4711.837

Instance3216.5 18.458 2.968 124.339 53.011 91899.087 37050.694 12.040 1.071 0.929 48.849 232532.134 4693.622

Instance3216.6 18.382 2.437 124.307 52.989 91846.065 37055.170 12.282 1.076 0.934 48.844 232020.776 4708.106



% Processor Time 3.673 1.533 17.230





Pool Paged Bytes 122330487.467 122085376.000 122572800.000


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: 192.0 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: 15000 ms). 5/4/2010 8:38:06 PM -- Attaining prerequisites: 5/4/2010 8:42:50 PM -- \MSExchange Database(JetstressWin)\Database Cache Size, Last: 1454948000.0 (lower bound: 1449551000.0, upper bound: none) 5/4/2010 10:42:51 PM -- Performance logging ends. 5/4/2010 10:42:51 PM -- JetInterop batch transaction stats: 33106, 33015, 33178, 32966, 32674 and 32832. 5/4/2010 10:42:51 PM -- Dispatching transactions ends. 5/4/2010 10:42:51 PM -- Shutting down databases ... 5/4/2010 10:42:58 PM -- Instance3216.1 (complete), Instance3216.2 (complete), Instance3216.3 (complete), Instance3216.4 (complete), Instance3216.5 (complete) and Instance3216.6 (complete) 5/4/2010 10:42:59 PM -- Performance logging begins (interval: 30000 ms). 5/4/2010 10: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 -- Instance3216.1 has 17.3 for I/O Database Reads Average Latency. 5/5/2010 9:57:59 AM -- Instance3216.1 has 1.1 for I/O Log Writes Average Latency. 5/5/2010 9:57:59 AM -- Instance3216.1 has 1.1 for I/O Log Reads Average Latency. 5/5/2010 9:57:59 AM -- Instance3216.2 has 17.3 for I/O Database Reads Average Latency. 5/5/2010 9:57:59 AM -- Instance3216.2 has 1.1 for I/O Log Writes Average Latency. 5/5/2010 9:57:59 AM -- Instance3216.2 has 1.1 for I/O Log Reads Average Latency. 5/5/2010 9:57:59 AM -- Instance3216.3 has 17.3 for I/O Database Reads Average Latency. 5/5/2010 9:57:59 AM -- Instance3216.3 has 1.1 for I/O Log Writes Average Latency. 5/5/2010 9:57:59 AM -- Instance3216.3 has 1.1 for I/O Log Reads Average Latency. 5/5/2010 9:57:59 AM -- Instance3216.4 has 18.4 for I/O Database Reads Average Latency.

5/5/2010 9:57:59 AM -- Instance3216.4 has 1.1 for I/O Log Writes Average Latency. 5/5/2010 9:57:59 AM -- Instance3216.4 has 1.1 for I/O Log Reads Average Latency. 5/5/2010 9:57:59 AM -- Instance3216.5 has 18.5 for I/O Database Reads Average Latency. 5/5/2010 9:57:59 AM -- Instance3216.5 has 1.1 for I/O Log Writes Average Latency. 5/5/2010 9:57:59 AM -- Instance3216.5 has 1.1 for I/O Log Reads Average Latency. 5/5/2010 9:57:59 AM -- Instance3216.6 has 18.4 for I/O Database Reads Average Latency. 5/5/2010 9:57:59 AM -- Instance3216.6 has 1.1 for I/O Log Writes Average Latency. 5/5/2010 9:57:59 AM -- Instance3216.6 has 1.1 for I/O Log Reads Average Latency. 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.

23

Database Backup Test Results

Microsoft Exchange Server Jetstress Tool – Database Backup

Database backup Test Result Report (from server 3650-1) Database Backup Statistics - All

Database Instance Database Size (MBytes) Elapsed Backup Time MBytes Transferred/sec

Instance2756.1 2000003.59 15:13:48 36.48

Instance2756.2 2000003.59 15:13:15 36.50

Instance2756.3 2000003.59 15:10:36 36.61

Instance2756.4 2000003.59 15:02:37 36.93

Instance2756.5 2000003.59 14:59:39 37.05

Instance2756.6 2000003.59 14:58:59 37.08








Read Operations 35%

Lazy Commits 70%









MSExchange

Database ==>

Instances

I/O

Database

Reads Average

Latency

(msec)

I/O

Database

Writes Average

Latency

(msec)

I/O

Database

Reads/sec

I/O

Database

Writes/sec

I/O

Database

Reads Average

Bytes

I/O

Database

Writes Average

Bytes

I/O Log

Reads

Average Latency

(msec)

I/O Log

Writes

Average Latency

(msec)

I/O Log

Reads/sec

I/O Log

Writes/sec

I/O Log

Reads

Average Bytes

I/O Log

Writes

Average Bytes

Instance2756.1 12.865 0.000 145.838 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000

Instance2756.2 12.835 0.000 145.971 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000

Instance2756.3 12.791 0.000 146.430 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000

Instance2756.4 12.701 0.000 147.688 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000

Instance2756.5 12.665 0.000 148.194 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000

Instance2756.6 12.670 0.000 148.332 0.000 262144.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000

24



% Processor Time 4.897 2.494 12.318





Pool Paged Bytes 123659938.068 121999360.000 163803136.000


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: 30000 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 -- Instance2756.1 (100% processed), Instance2756.2 (100% processed), Instance2756.3 (100% processed), Instance2756.4 (100% processed), Instance2756.5 (100% processed) and Instance2756.6 (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 3650-1) Soft-Recovery Statistics - All

Database Instance Log files replayed Elapsed seconds

Instance3368.1 501 494.3359688

Instance3368.2 504 486.6451195

Instance3368.3 500 487.4407246

Instance3368.4 521 493.5403637

Instance3368.5 513 465.4289835

Instance3368.6 511 477.8934634







Instance3368.6 Log Path: L:\log16

25

Database: J:Jetstress006001.edb


MSExchange

Database ==>

Instances

I/O

Database

Reads

Average

Latency (msec)

I/O

Database

Writes

Average

Latency (msec)

I/O

Database

Reads/sec

I/O

Database

Writes/sec

I/O

Database

Reads

Average

Bytes

I/O

Database

Writes

Average

Bytes

I/O Log

Reads

Average

Latency

(msec)

I/O Log

Writes

Average

Latency

(msec)

I/O Log

Reads/sec

I/O Log

Writes/sec

I/O Log

Reads

Average

Bytes

I/O Log

Writes

Average

Bytes

Instance3368.1 23.874 9.263 981.800 6.050 36213.704 32768.000 11.946 0.000 9.076 0.000 232522.701 0.000

Instance3368.2 26.864 13.503 973.936 6.171 36258.769 32768.000 12.404 0.000 9.257 0.000 232757.794 0.000

Instance3368.3 24.438 9.555 980.179 6.084 36374.442 32768.000 10.887 0.000 9.126 0.000 232500.843 0.000

Instance3368.4 24.124 10.533 973.866 6.286 36220.740 32768.000 13.320 0.019 9.419 0.006 232487.587 4.197

Instance3368.5 26.377 9.691 982.162 6.537 36393.783 32768.000 13.478 0.004 9.809 0.013 232508.465 4.452

Instance3368.6 25.280 9.953 971.355 6.377 36318.612 32768.000 12.046 0.003 9.565 0.006 232512.942 4.339





Instance3368.1 20.918 261957.372

Instance3368.2 20.409 262079.326

Instance3368.3 20.407 262053.937

Instance3368.4 21.031 262082.628

Instance3368.5 20.784 261916.148

Instance3368.6 20.981 262047.431


MSExchange

Database ==>

Instances

I/O

Database

Reads

Average

Latency

(msec)

I/O

Database

Writes

Average

Latency

(msec)

I/O

Database

Reads/sec

I/O

Database

Writes/sec

I/O

Database

Reads

Average

Bytes

I/O

Database

Writes

Average

Bytes

I/O Log

Reads

Average

Latency

(msec)

I/O Log

Writes

Average

Latency

(msec)

I/O Log

Reads/sec

I/O Log

Writes/sec

I/O Log

Reads

Average

Bytes

I/O Log

Writes

Average

Bytes

Instance3368.1 23.874 9.263 1002.718 6.050 40923.082 32768.000 11.946 0.000 9.076 0.000 232522.701 0.000

Instance3368.2 26.864 13.503 994.345 6.171 40893.666 32768.000 12.404 0.000 9.257 0.000 232757.794 0.000

Instance3368.3 24.438 9.555 1000.585 6.084 40977.083 32768.000 10.887 0.000 9.126 0.000 232500.843 0.000

Instance3368.4 24.124 10.533 994.897 6.286 40995.148 32768.000 13.320 0.019 9.419 0.006 232487.587 4.197

Instance3368.5 26.377 9.691 1002.946 6.537 41067.269 32768.000 13.478 0.004 9.809 0.013 232508.465 4.452

Instance3368.6 25.280 9.953 992.335 6.377 41091.127 32768.000 12.046 0.003 9.565 0.006 232512.942 4.339



% Processor Time 14.977 2.432 26.751





Pool Paged Bytes 123408783.610 122134528.000 123465728.000


Test Log5/8/2010 12:35:06 PM -- Jetstress testing begins ... 5/8/2010 12:35:06 PM -- Prepare testing begins ... 5/8/2010 12:35:12 PM -- Attaching databases ... 5/8/2010 12:35:12 PM -- Prepare testing ends. 5/8/2010 12:35:12 PM -- Dispatching transactions begins ... 5/8/2010 12:35:12 PM -- Database cache settings: (minimum: 192.0 MB, maximum: 1.5 GB) 5/8/2010 12:35:12 PM -- Database flush thresholds: (start: 15.3 MB, stop: 30.7 MB) 5/8/2010 12:35:19 PM -- Database read latency thresholds: (average: 20 msec/read, maximum: 100

26

msec/read). 5/8/2010 12:35:19 PM -- Log write latency thresholds: (average: 10 msec/write, maximum: 100 msec/write). 5/8/2010 12:35:21 PM -- Operation mix: Sessions 6, Inserts 40%, Deletes 20%, Replaces 5%, Reads 35%, Lazy Commits 70%. 5/8/2010 12:35:21 PM -- Performance logging begins (interval: 15000 ms). 5/8/2010 12: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, 21566 and 21731. 5/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 -- Instance3368.1 (complete), Instance3368.2 (complete), Instance3368.3 (complete), Instance3368.4 (complete), Instance3368.5 (complete) and Instance3368.6 (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 -- Instance3368.1 has 22.9 for I/O Database Reads Average Latency. 5/8/2010 1:59:26 PM -- Instance3368.1 has 0.9 for I/O Log Writes Average Latency. 5/8/2010 1:59:26 PM -- Instance3368.1 has 0.9 for I/O Log Reads Average Latency.

5/8/2010 1:59:26 PM -- Instance3368.2 has 22.8 for I/O Database Reads Average Latency. 5/8/2010 1:59:26 PM -- Instance3368.2 has 0.9 for I/O Log Writes Average Latency. 5/8/2010 1:59:26 PM -- Instance3368.2 has 0.9 for I/O Log Reads Average Latency. 5/8/2010 1:59:26 PM -- Instance3368.3 has 22.9 for I/O Database Reads Average Latency. 5/8/2010 1:59:26 PM -- Instance3368.3 has 0.9 for I/O Log Writes Average Latency. 5/8/2010 1:59:26 PM -- Instance3368.3 has 0.9 for I/O Log Reads Average Latency. 5/8/2010 1:59:26 PM -- Instance3368.4 has 25.6 for I/O Database Reads Average Latency. 5/8/2010 1:59:26 PM -- Instance3368.4 has 1.0 for I/O Log Writes Average Latency. 5/8/2010 1:59:26 PM -- Instance3368.4 has 1.0 for I/O Log Reads Average Latency. 5/8/2010 1:59:26 PM -- Instance3368.5 has 25.8 for I/O Database Reads Average Latency. 5/8/2010 1:59:26 PM -- Instance3368.5 has 1.0 for I/O Log Writes Average Latency. 5/8/2010 1:59:26 PM -- Instance3368.5 has 1.0 for I/O Log Reads Average Latency. 5/8/2010 1:59:26 PM -- Instance3368.6 has 25.7 for I/O Database Reads Average Latency. 5/8/2010 1:59:26 PM -- Instance3368.6 has 1.0 for I/O Log Writes Average Latency. 5/8/2010 1:59:26 PM -- Instance3368.6 has 1.0 for I/O Log Reads Average Latency. 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 -- Instance3368.1 (494.3359688), Instance3368.2 (486.6451195), Instance3368.3 (487.4407246), Instance3368.4 (493.5403637), Instance3368.5 (465.4289835) and Instance3368.6 (477.8934634) 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 ...

© 2010 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.

Netapp and Exchange

Documents

program filesexchange

program filesexchange

program filesexchange

program filesexchange

program filesexchange

jetstress

performance

dispatching