Hus 130 Dynamically Provisioned 36000 Mailbox Exchange Storage Solution PDF

1
Hitachi Unified Storage 130 Dynamically

Provisioned 36,000 Mailbox Exchange 2010
Mailbox Resiliency Storage Solution
Tested with: ESRP Storage Version 3.0
Test Date: July 2012
Month Year
Notices and Disclaimer

Copyright 2012 Hitachi Data Systems Corporation. All rights reserved.
The performance data contained herein was obtained in a controlled isolated environment. Actual results that
may be obtained in other operating environments may vary significantly. While Hitachi Data Systems
Corporation has reviewed each item for accuracy in a specific situation, there is no guarantee that the same
results can be obtained elsewhere.
All designs, specifications, statements, information and recommendations (collectively, "designs") in this
manual are presented "AS IS," with all faults. Hitachi Data Systems Corporation and its suppliers disclaim all
warranties, including without limitation, the warranty of merchantability, fitness for a particular purpose and
non-infringement or arising from a course of dealing, usage or trade practice. In no event shall Hitachi Data
Systems Corporation or its suppliers be liable for any indirect, special, consequential or incidental damages,
including without limitation, lost profit or loss or damage to data arising out of the use or inability to use the
designs, even if Hitachi Data Systems Corporation or its suppliers have been advised of the possibility of such
damages.
This document has been reviewed for accuracy as of the date of initial publication. Hitachi Data Systems
Corporation may make improvements and/or changes in product and/or programs at any time without notice.
Table of Contents
Overview ..................................................................................................................................... 3
Disclaimer ................................................................................................................................... 3
Features ...................................................................................................................................... 4
Solution Description .................................................................................................................. 5
Targeted Customer Profile ........................................................................................................ 13
Test Deployment ........................................................................................................................ 14
Replication Configuration ......................................................................................................... 16
Best Practices ............................................................................................................................ 18
Core Storage ............................................................................................................................. 18
Storage-based Replication ....................................................................................................... 19
Backup Strategy........................................................................................................................ 19
Test Results Summary .............................................................................................................. 20
Reliability................................................................................................................................... 20
Storage Performance Results ................................................................................................... 20
Database Backup and Recovery Performance ........................................................................ 24
Conclusion .................................................................................................................................. 25
Performance Test Result Report: CB15 ................................................................................... 26
Performance Test Database Checksum Result: CB15 ............................................................ 35
Stress Test Result Report: CB15 .............................................................................................. 39
Stress Test Database Checksums Result: CB15 ..................................................................... 48
Backup Test Result Report: CB15 ............................................................................................ 52
Soft Recovery Test Result Report: CB15 ................................................................................. 56
Soft Recovery Test Performance Result: CB15 ....................................................................... 63
Hitachi Unified Storage 130 Dynamically

Provisioned 36,000 Mailbox Exchange 2010
Mailbox Resiliency Storage Solution
Tested with: ESRP Storage Version 3.0
Test Date: July 2012
Overview
This document provides information on a Microsoft Exchange Server 2010 mailbox resiliency storage solution
that uses Hitachi Unified Storage 130 storage systems with Hitachi Dynamic Provisioning. This solution is
based on the Microsoft Exchange Solution Reviewed Program (ESRP) Storage program. For more
information about the contents of this document or Hitachi Data Systems best practice recommendations for
Microsoft Exchange Server 2010 storage design, see Hitachi Data Systems Microsoft Exchange Solutions
Web page.
The ESRP Storage program was developed by Microsoft Corporation to provide a common storage testing
framework for vendors to provide information on its storage solutions for Microsoft Exchange Server software.
For more information about the Microsoft ESRP Storage program, see TechNets overview of the program.
Disclaimer
This document has been produced independently of Microsoft Corporation. Microsoft Corporation expressly
disclaims responsibility for, and makes no warranty, express or implied, with respect to the accuracy of the
contents of this document.
The information contained in this document represents the current view of Hitachi Data Systems on the issues
discussed as of the date of publication. Due to changing market conditions, it should not be interpreted to be a
commitment on the part of Hitachi Data Systems, and Hitachi Data Systems cannot guarantee the accuracy of
any information presented after the date of publication.
Features
The purpose of this testing was to measure the ESRP 3.0 results on a Microsoft Exchange 2010 environment
with 36,000 users and eight servers. This testing used Hitachi Unified Storage 130 with Hitachi Dynamic
Provisioning in a two-pool RAID-10 (4D+4D) (one for databases and one for logs) resiliency configuration.
These results help answer questions about the kind of performance capabilities to expect with a large-scale
Exchange deployment on Hitachi Unified Storage 130.
Testing used eight Hitachi Compute Blade 2000 server blades (4 blades were used per chassis) mounted in
two separate chassis, each with the following:
64 GB of RAM
Two six-core Intel Xeon X5690 3.46 GHz CPUs
Two dual-port 8 Gb/sec Fibre Channel PCIe HBA (Emulex LPe1205-HI) located in the chassis I/O
expansion tray
Microsoft Windows Server 2008 R2 Enterprise
This solution includes Exchange 2010 Mailbox Resiliency by using the database availability group (DAG)
feature. This tested configuration uses eight DAGs, each containing 12 database copies and two servers. The
test configuration was capable of supporting 36,000 users with a 0.18 IOPS per user profile and user mailbox
size of 3 GB.
A Hitachi Unified Storage130 with the following was used for these tests:
240 2TB 7.2K RPM SAS disks
16 GB of cache
16 8 Gb/sec paths used
Hitachi Unified Storage 130 is a large-sized, high-performance, highly reliable midrange storage system that
can scale to 240 disks while maintaining 99.999% availability. It is highly suitable for a variety of applications
and host platforms and is modular in scale. With the option of in-system and cross-system replication
functionality, Hitachi Unified Storage 130 is fully capable of being used as the core underlying storage platform
for high-performance Exchange Server 2010 architectures.
Solution Description
Deploying Microsoft Exchange Server 2010 requires careful consideration of all aspects of the solution
architecture. Host servers need to be configured so that they are robust enough to handle the required
Exchange load. The storage solution must be designed to provide the necessary performance while also being
reliable and easy to administer. Of course, an effective backup and recovery plan should be incorporated into
the solution as well. The aim of this solution report is to provide a tested configuration that uses Hitachi Unified
Storage 130 to meet the needs of a large Exchange Server deployment.
This solution used Hitachi Dynamic Provisioning (HDP), which is enabled on Hitachi Unified Storage 130 via a
license key. In the most basic sense, Hitachi Dynamic Provisioning is similar to the use of a host-based logical
volume manager (LVM), but with several additional features available within Hitachi Unified Storage 130 and
without the need to install software on the host or incur host processing overhead. Hitachi Dynamic
Provisioning is a superior solution by providing for one or more separate pools of wide striping across many
RAID groups within Hitachi Unified Storage 130. One or more Hitachi Dynamic Provisioning virtual volumes
(DP-VOLs) of a user-specified logical size (with no initial physical space allocated) are created and associated
with a single pool.
Primarily, Hitachi Dynamic Provisioning is deployed to avoid the routine issue of hot spots that occur on logical
units (LUs) from individual RAID groups when the host workload exceeds the IOPS or throughput capacity of
that RAID group. By using many RAID groups as members of a striped dynamic provisioning pool underneath
the virtual or logical volumes seen by the hosts, a host workload is distributed across many RAID groups,
which provides a smoothing effect that dramatically reduces hot spots and results in fewer mailbox moves for
the Exchange administrator.
Hitachi Dynamic Provisioning also carries the side benefit of thin provisioning, where physical space is only
assigned from the pool to the DP-VOL as needed using 1 GB chunks per RAID Group, up to the logical volume
size specified by the user for each DP-VOL. Space from a 1 GB chunk is then allocated as needed as
individual 32 MB pool pages to that DP-VOLs logical block address range. A pool can also be dynamically
expanded by adding more RAID groups without disruption or requiring downtime. Upon expansion, a pool can
easily be rebalanced so that the data and workload are wide striped evenly across the current and newly
added RAID groups that make up the pool.
High availability is also a part of this solution with the use of database availability groups (DAG), which is the
base component of the high availability and site resilience framework built into Microsoft Exchange Server
2010. A DAG is a group of up to 16 mailbox servers that host a set of databases and logs and use continuous
replication to provide automatic database-level recovery from failures that affect individual servers or
databases.
Any server in a DAG can host a copy of a mailbox database from any other server in the DAG. When a server
is added to a DAG, it monitors and works with the other servers in the DAG to provide automatic recovery
delivering a robust, highly available Exchange solution without the administrative complexities of traditional
failover clustering. For more information about the DAG feature in Exchange Server 2010, see
http://technet.microsoft.com/en-us/library/dd979799.aspx .
This solution included two copies of each Exchange database using eight DAGs, with each DAG configured
with two server blades (one simulated) that host active mailboxes in 12 databases.
To target the 36,000 user resiliency solution, a Hitachi Unified Storage 130 storage system was configured
with 240 disks (of a maximum of 240). Eight servers (one per DAG) were used, with each server configured
with 4,500 mailboxes. There were 12 active databases and the simulated database copies for the tests.
Each DAG contained two copies of the databases hosted by that DAG;
A local, active copy on a server connected to the primary Hitachi Unified Storage 130
A passive copy (simulated) on another server connected to a second Hitachi Unified Storage 130
(simulated).
This recommended configuration can support both high-availability and disaster-recovery scenarios when the
active and passive database copies are allocated among both DAG members and dispersed across both
storage systems. Each simulated DAG server node in this solution maintains a mirrored configuration and
possesses adequate capacity and performance capabilities to support the second set of replicated databases.
Figure 1 illustrates the systems that makes up the simulated DAG configuration. For more information, see the
Hitachi Data Systems Storage Systems web page.
Figure 1
This solution enables organizations to consolidate Exchange Server 2010 DAG deployments on two Hitachi
Unified Storage 130 storage systems. Using identical hardware and software configurations guarantees that an
active database and its replicated copy do not share storage paths, disk spindles or storage controllers,
making it a very reliable, high-performing, highly available Exchange Server 2010 solution that is cost effective
and easy to manage. This helps ensure that performance and service levels related to storage are maintained
regardless of which server is hosting the active database. If further protection is needed in a production
environment, additional Exchange Server 2010 mailbox servers can be easily added to support these failover
scenarios.
Table 1 illustrates how the disks in Hitachi Unified Storage 130 were organized into RAID groups for use by
either databases or logs. Each set of colored disks represents a RAID-10 (4D+ 4D) groups. There were 240
2TB 7.2K RPM SAS disks used in these tests configured as 30 RAID groups for the Exchange databases and
logs.
Table 1. Hitachi Unified Storage 130 RAID Groups by Tray Layout
HUS130, 2TB 7.2K SAS, R-10(4D+4D) HDP Pool Disk Layout
Unit 19
RG46
Unit 18
RG47
Unit 17
RG49
Unit 16
RG50
Unit 15
RG52
Unit 14
RG53
Unit 13
RG55
Unit 12
RG56
Unit 11
RG58
Unit 10
Rg59
Unit 9
RG61
Unit 8
RG62
Unit 7
RG64
Unit 6
RG65
Unit 5
RG67
Unit 4
RG68
Unit 3
RG70
Unit 2
RG71
Unit 1
RG73
Unit 0
RG74
Slot #
RG45
RG46
RG48
RG49
RG51
RG52
RG54
RG55
RG57
RG58
RG60
RG61
RG63
RG64
RG66
RG67
RG69
RG70
RG72
RG73
10
11
DB Pool
Log Pool
Two dynamic provisioning pools were created, one for the databases and the other for the logs. The database
pool was created from 27 RAID-10 (4D+4D) RAID groups and the log pool was created from 3 RAID-10
(4D+4D) groups. From the database pool, 96 DP-VOLs (each specified to have a 1990 GB size limit) were
created for 96 databases (12 per server). From the log pool, 96 DP-VOLs (each specified to have a size limit of
199 GB) were created for 96 logs (12 per server).
Table 2 outlines the port layout for the primary storage system and servers. An identical configuration would be
deployed on the replicated storage and servers for this solution.
Table 2. Hitachi Unified Storage 130 Ports to Server Layout
Server
Primary
Path
Secondary
Path
CB14
0A
1A
0C
1C
0E
1E
0G
1G
0B
1B
0D
1D
0F
1F
0H
1H
1A
0A
1C
0C
1E
0E
1G
0G
1B
0B
1D
0D
1F
0F
1H
0H
CB15
CB16
CB17
CB18
CB19
CB20
CB21
Table 3 outlines the port layout with the database DP-VOL assignments for the primary storage and servers.
An identical configuration would be deployed on the replicated storage and servers for this solution.
Table 3. Hitachi Unified Storage 130 Ports to Database DP-VOL Layout
Port
Database
DB DP-VOLs
0A
Databases 1-6
0-5
0C
Databases 7-12
6-11
0E
Databases 13-17
12-17
0G
Databases 18-24
18-23
0B
Databases 25-30
24-29
0D
Databases 31-36
30-35
0F
Databases 37-42
36-41
0H
Databases 43-48
42-47
1A
Databases 49-54
48-53
1C
Databases 55-60
54-59
1E
Databases 61-66
60-65
1G
Databases 67-72
66-71
1B
Databases 73-78
72-77
1D
Databases 79-84
78-83
1F
Databases 85-90
84-89
1H
Databases 91-96
90-95
10
Table 4 outlines the port layout with the log DP-VOL assignments for the primary storage system and servers.
An identical configuration would be deployed on the replicated storage and servers for this solution.
Table 4. Hitachi Unified Storage 130 Ports to Log DP-VOL Layout
Port
Log
Log DPVOLs
0A
Log 1-6
96-101
0C
Log 7-12
102-107
0E
Log 13-17
108-113
0G
Log 18-24
114-119
0B
Log 25-30
120-125
0D
Log 31-36
126-131
0F
Log 37-42
132-137
0H
Log 43-48
138-143
1A
Log 49-54
144-149
1C
Log 55-60
150-155
1E
Log 61-66
156-161
1G
Log 67-72
162-167
1B
Log 73-78
168-173
1D
Log 79-84
174-179
1F
Log 85-90
180-185
1H
Log 91-96
186-191
11
Table 5 provides the detailed specifications for the storage configurations which use RAID-10 (4D+4D) RAID
groups and 2TB SAS 7.2K RPM disks. Dynamic Provisioning Pool 0 is dedicated for the databases and
Dynamic Provisioning Pool 1 is dedicated for the logs
Table 5. Hitachi Unified Storage 130 Configuration Details
Host
Pool
Port
DP-VOL
Size (GB)
RAID Level
Description
CB14
0A/1A
0-5
1990
RAID-10
Databases 1-6
0C/1C
6-11
1990
RAID-10
Databases 7-12
0E/1E
12-17
1990
RAID-10
Databases 13-17
0G/1G
18-23
1990
RAID-10
Databases 18-24
0B/1B
24-29
1990
RAID-10
Databases 25-30
0D/1D
30-35
1990
RAID-10
Databases 31-36
0F/1F
36-41
1990
RAID-10
Databases 37-42
0H/1H
42-47
1990
RAID-10
Databases 43-48
1A/0A
48-53
1990
RAID-10
Databases 49-54
1C/0C
54-59
1990
RAID-10
Databases 55-60
1E/0E
60-65
1990
RAID-10
Databases 61-66
1G/0G
66-71
1990
RAID-10
Databases 67-72
1B/0B
72-77
1990
RAID-10
Databases 73-78
1D/0D
78-83
1990
RAID-10
Databases 79-84
1F/0F
84-89
1990
RAID-10
Databases 85-90
1H/0H
90-95
1990
RAID-10
Databases 91-96
0A/1A
96-101
199
RAID-10
Log 1-6
0C/1C
102-107
199
RAID-10
Log 7-12
0E/1E
108-113
199
RAID-10
Log 13-17
0G/1G
114-119
199
RAID-10
Log 18-24
0B/1B
120-125
199
RAID-10
Log 25-30
0D/1D
126-131
199
RAID-10
Log 31-36
0F/1F
132-137
199
RAID-10
Log 37-42
0H/1H
138-143
199
RAID-10
Log 43-48
1A/0A
144-149
199
RAID-10
Log 49-54
1C/0C
150-155
199
RAID-10
Log 55-60
1E/0E
156-161
199
RAID-10
Log 61-66
1G/0G
162-167
199
RAID-10
Log 67-72
1B/0B
168-173
199
RAID-10
Log 73-78
1D/0D
174-179
199
RAID-10
Log 79-84
1F/0F
180-185
199
RAID-10
Log 85-90
1H/0H
186-191
199
RAID-10
Log 91-96
CB15
CB16
CB17
CB18
CB19
CB20
CB21
CB14
CB15
CB16
CB17
CB18
CB19
CB20
CB21
12
The ESRP Storage program focuses on storage solution testing to address performance and reliability
issues with storage design. However, storage is not the only factor to take into consideration when designing a
scale-up Exchange solution. These factors also affect server scalability:
Server processor utilization
Server physical and virtual memory limitations
Resource requirements for other applications
Directory and network service latencies
Network infrastructure limitations
Replication and recovery requirements
Client usage profiles
These factors are all beyond the scope of the ESRP Storage program. Therefore, the number of mailboxes
hosted per server as part of the tested configuration might not necessarily be viable for some customer
deployments.
For more information about identifying and addressing performance bottlenecks in an Exchange system, see
Microsoft's Troubleshooting Microsoft Exchange Server Performance.
Targeted Customer Profile

This solution is designed for medium to large organizations that plan to consolidate their Exchange Server
2010 storage on high-performance, high-reliability storage systems. This configuration is designed to support
36,000 Exchange users with the following specifications:
Sixteen Exchange servers (8 tested, 8 simulated for the database copies)
Eight database availability groups (DAG) each with two servers (one simulated) and two copies per
database
Two Hitachi Unified Storage 130 (one tested)
0.15 IOPS per user (0.18 tested for 20 percent growth)
3 GB mailbox size
Mailbox resiliency provides high-availability and used as primary data protection mechanism.
Hitachi Unified Storage RAID protection against physical failure or loss.
24x7 background database maintenance enabled.
13
Test Deployment
The following tables summarize the testing environment.
Table 6. Simulated Exchange Configuration
Number of Exchange mailboxes simulated
36,000
Number of database availability groups (DAGs)
Number of servers per DAG
2 (1 simulated)
Number of active mailboxes per server
4,500
Number of databases per host
12
Number of copies per database
Number of mailboxes per database
375
Simulated profile: I/Os per second per mailbox (IOPS, include 20% headroom)
0.18
Database LU size
1990 GB
Log LU size
199 GB
Total database size for performance testing
108,000 GB
% storage capacity used by Exchange database**
56.5%
** Storage performance characteristics change based on the percentage utilization of the individual disks.
Tests that use a small percentage of the storage (~25%) might exhibit reduced throughput if the storage
capacity utilization is significantly increased beyond what was tested for this paper.
Table 7. Storage Hardware
Storage connectivity (Fibre Channel, SAS, SATA, iSCSI)
Fibre Channel
Storage model and OS/firmware revision
1 Hitachi Unified
Storage 130
Firmware: 0920/A-S
WHQL listing: Hitachi
Unified Storage 130
Storage cache
16 GB
Number of storage controllers
Number of storage ports
16
Maximum bandwidth of storage connectivity to host
128 Gb/sec (16 8

Gb/sec ports)
Switch type/model/firmware revision
Brocade 5300, Fabric

OS v7.0.1b
HBA model and firmware
Emulex LPe1205-HI
Firmware : 1.11X14
Number of HBAs per host
2 dual-ported HBA per

host, 2 8 Gb/sec port
used per HBA
14
Host server type
Hitachi Compute Blade

E55A2 2 3.46 GHz
six-core Intel Xeon
X5690 CPUs, 64 GB
memory
Total number of disks tested in solution
240
Maximum number of spindles that can be hosted in the storage
240
Table 8. Storage Software

HBA driver
Driver version :
7.2.20.006
HBA QueueTarget setting
HBA QueueDepth setting
32
Multipathing
Hitachi Dynamic Link

Manager v7.2.1-00
Host OS
Microsoft Windows
Server 2008 R2
Enterprise
ESE.dll file version
14.01.0218.012
Replication solution name/version
N/A
Table 9. Storage Disk Configuration (Mailbox Store Disks)

Disk type, speed and firmware revision
SAS 2TB 7.2K 5C0C
Raw capacity per disk (GB)
2 TB
Number of physical disks in test
216 (dynamic
provisioning pool)
Total raw storage capacity (GB)
432,000
Disk slice size (GB)
N /A
Number of slices per LU or number of disks per LU
N/A
RAID level
RAID-10 (4D+4D) at
storage level
Total formatted capacity
191,160 GB
Storage capacity utilization
44.3%
Database capacity utilization
44.2%
Table 10. Storage Disk Configuration (Transaction Log Disks)

SAS 2TB 7.2K 5C0C
2 TB
Number of spindles in test
24 (dynamic
provisioning pool)
48,000
15
N/A
N/A
RAID level
RAID-10 (4D+4D) at
storage level
21,240 GB
Replication Configuration
Table 11. Replication Configuration
Replication mechanism
Exchange Server 2010

Database Availability
Group (DAG)
Number of links
Simulated link distance
N/A
Link type
IP
Link bandwidth
GigE (1 Gb/sec)
Table 12. Replicated Storage Hardware

Storage connectivity (Fibre Channel, SAS, SATA, iSCSI)
Fibre Channel
Storage model and OS/firmware revision
1 Hitachi Unified
Storage 130
Firmware: 0920/A-S
WHQL listing: Hitachi
Unified Storage 130
Storage cache
16 GB
Number of storage controllers
Number of storage ports
Maximum bandwidth of storage connectivity to host
128 Gb/sec (16 8

Gb/sec ports)
Switch type/model/firmware revision
Brocade 5300, Fabric

OS v7.0.1b
HBA model and firmware
Emulex LPe1205-HI
Firmware:1.11X14
Number of HBAs per host
2 dual-ported HBA per

host, 2 8 Gb/sec
ports used per HBA
Host server type
Hitachi Compute Blade

E55A2 2 3.46 GHz
six-core Intel Xeon
X5690 CPUs, 64 GB
memory
Total number of disks tested in solution
240
Maximum number of spindles that can be hosted in the storage
240
16
Table 13. Replicated Storage Software

HBA driver
Driver version :
7.2.20.006
HBA QueueTarget setting
HBA QueueDepth setting
32
Multipathing
Hitachi Dynamic Link

Manager v7.2.1-00
Host OS
Microsoft Windows
Server 2008 R2
Enterprise
ESE.dll file version
14.01.0218.012
Replication solution name/version
N/A
Table 14. Replicated Storage Disk Configuration (Mailbox Store Disks)

SAS 2TB 7.2K 5C0C
2 TB
Number of physical disks in test
216 (dynamic
provisioning pool)
432,000
N /A
N/A
RAID level
RAID-10 (4D+4D) at
storage level
191,160 GB
Storage capacity utilization
44.3%
Database capacity utilization
44.2%
Table 15. Replicated Storage Disk Configuration (Transactional Log Disks)

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

This section provides a high-level summary of the test data from ESRP and the link to the detailed HTML
reports that are generated by ESRP testing framework.
Reliability
A number of tests in the framework check reliability spanning a 24-hour window. The goal is to verify the
storage can handle high I/O load for a long period of time. Following these stress tests, both log and database
files are analyzed for integrity to ensure that no database or log corruption occurs.
No errors were reported in the event log file for the storage reliability testing.
No errors were reported for the database and log checksum process.
If done, no errors were reported during the backup to disk test process.
No errors were reported for the database checksum on the remote storage database.
Storage Performance Results

Primary storage performance testing exercises the storage with maximum sustainable Exchange type of I/O for
two hours. The test shows how long it takes for the storage to respond to an I/O under load. The following data
is the sum of all of the logical disk I/Os and average of all the logical disks I/O latency in the two-hour test
duration.
Individual Server Metrics

These individual server metrics show the sum of the I/O across the storage groups and the average latency
across all storage groups on a per-server basis.
Table 16. Individual Server Metrics for Exchange Server (CB14)
Database I/O
Database Disk Transfers Per Second
930
Database Disk Reads Per Second
551
Database Disk Writes Per Second
379
Average Database Disk Read Latency (ms)
15.1
Average Database Disk Write Latency (ms)
1.7
Transaction Log I/O

Log Disk Writes Per Second
324
Average Log Disk Write Latency (ms)
0.6
20

Database I/O
928
550
378
15.3
1.6
Transaction Log I/O

325
0.6

Database I/O
927
549
378
15.2
1.7
Transaction Log I/O

324
0.6

Database I/O
925
548
377
15.4
1.7
Transaction Log I/O

323
0.6
21

Database I/O
923
546
377
15.6
1.6
Transaction Log I/O

323
0.6

Database I/O
925
547
378
15.5
1.6
Transaction Log I/O

323
0.6

Database I/O
923
547
376
15.4
1.7
Transaction Log I/O

324
0.6
22

Database I/O
926
548
378
15.5
1.6
Transaction Log I/O

324
0.6
23
Aggregate Performance Across All Servers Metric

The aggregate performance across all server metrics shows the sum of I/Os across all servers in the solution
and the average latency across all servers in the solution.
Table 24. Aggregate Performance for Exchange Server 2010
Database I/O
3709.97
2198.05
1511.92
15.24
1.68
Transaction Log I/O

1297.49
0.61
Database Backup and Recovery Performance

This section has two tests: The first measures the sequential read rate of the database files and the second
measures recovery/replay performance (playing transaction logs in to the database).
Database Read-only Performance

This test measures the maximum rate at which databases can be backed up via VSS. The following tables
show the average rate for a single database file.
Table 25. Database Read-only Performance
MB Read Per Second Per Database
51.72
MB Read Per Second Total Per Server
620.69
Transaction Log Recovery/Replay Performance

This test measures the maximum rate at which the log files can be played against the databases. The following
table shows the average rate for 500 log files played in a single storage group. Each log file is 1MB in size.
Table 26. Transaction Log Recovery/Replay Performance
Average Time to Play One Log File (sec)
3.51274
24
Conclusion
This document details a tested and robust Exchange Server 2010 Resiliency solution capable of supporting
36,000 Users with a 0.18 IOPS per user profile and user mailbox size of 3 GB using eight DAGs, each
configured using two server nodes (one simulated).
One Hitachi Unified Storage 130, with 16 GB of cache and sixteen 8 Gb/sec Fibre Channel host paths, using
Hitachi Dynamic Provisioning (with two pools) and 240 2TB 7.2K RPM SAS disks in a RAID-10 (4D+4D)
configuration was used for these tests.
Testing confirmed that Hitachi Unified Storage 130 is more than capable of delivering the IOPS and capacity
requirements needed to support the active and replicated databases for 36,000 Exchange mailboxes
configured with the specified user profile, while maintaining additional headroom to support peak throughput.
The solution outlined in this document does not include data protection components, such as VSS snapshot or
clone backups, and relies on the built-in Mailbox Resiliency features of Exchange Server 2010 coupled with
Adaptable Modular Storage RAID technology to provide high-availability and protection from logical and
physical failures. Adding additional protection requirements may affect performance and capacity requirements
of the underlying storage configuration, and as such need to be factored into the storage design accordingly.
For more information about planning Exchange Server 2010 storage architectures for the Hitachi Unified
Storage 100 family, see www.hds.com
This document is developed by Hitachi Data Systems and reviewed by the Microsoft Exchange product team.
The test results and data presented in this document are based on the tests introduced in the ESRP test
framework. Do not quote the data directly for pre-deployment verification. It is still necessary to validate the
storage design for a specific customer environment.
The ESRP program is not designed to be a benchmarking program; tests do not generate the maximum
throughput for a given solution. Rather, it is focused on producing recommendations from vendors for
Exchange application. Thus, do not use the data presented in this document for direct comparisons among the
solutions.
25
Appendix A Test Reports for HUS130

This appendix contains Jetstress test results for one of the servers used in testing this storage solution. These test results are representative of
the results obtained for all of the servers tested.
Performance Test Result Report: CB15

Test Summary
Overall Test Result
Pass
Machine Name
CB15
Test Description
Test Start Time
9/5/2012 12:24:56 AM
Test End Time
9/5/2012 2:54:03 AM
Collection Start Time
9/5/2012 12:30:02 AM
Collection End Time
9/5/2012 2:29:54 AM
Jetstress Version
14.01.0225.017
ESE Version
14.01.0218.012
Operating System
Windows Server 2008 R2 Enterprise Service Pack 1 (6.1.7601.65536)
Performance Log
C:\HUS130_PE104_CB15_SAS7K_ESRP_R10_3GB Mbox_36000Users\Performance Test\Checksum\Performance_2012_9_5_0_25_22.blg
Database Sizing and Throughput

Achieved Transactional I/O per Second
927.878
Target Transactional I/O per Second
810
Initial Database Size (bytes)
8808393605120
Final Database Size (bytes)
8812067815424
Database Files (Count)
12
26
Jetstress System Parameters

Thread Count
6 (per database)
Minimum Database Cache
384.0 MB
Maximum Database Cache
3072.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
27
Database Configuration
Instance4864.1
Log path: C:\logluns\log1

Database: C:\dbluns\db1\Jetstress001001.edb
Instance4864.2

Instance4864.3

Instance4864.4

Instance4864.5

Instance4864.6

Instance4864.7

Instance4864.8

Instance4864.9

Instance4864.10

Instance4864.11

Instance4864.12

28
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
Instance4864.1
16.762
1.811
45.786
31.486
35545.783
35076.032
0.000
0.693
0.000
27.086
0.000
4504.003
Instance4864.2
14.947
1.552
46.023
31.795
35707.646
35117.765
0.000
0.576
0.000
27.141
0.000
4495.664
Instance4864.3
14.797
1.620
45.735
31.434
35671.107
35069.857
0.000
0.608
0.000
27.033
0.000
4470.863
Instance4864.4
15.180
1.470
45.664
31.473
35693.560
35184.715
0.000
0.562
0.000
27.151
0.000
4506.855
Instance4864.5
15.255
1.766
45.107
30.934
35668.253
35064.040
0.000
0.659
0.000
26.684
0.000
4496.011
Instance4864.6
15.379
1.526
46.077
31.784
35825.437
35153.600
0.000
0.574
0.000
27.514
0.000
4489.875
Instance4864.7
15.222
1.710
46.318
31.956
35369.903
35030.026
0.000
0.597
0.000
27.385
0.000
4434.772
Instance4864.8
15.161
1.596
45.769
31.475
35606.334
35070.292
0.000
0.565
0.000
27.022
0.000
4513.524
Instance4864.9
15.360
1.712
46.028
31.769
35689.716
35085.197
0.000
0.627
0.000
27.397
0.000
4506.956
Instance4864.10
15.132
1.581
45.519
31.264
35759.001
35087.542
0.000
0.544
0.000
26.901
0.000
4518.610
Instance4864.11
15.021
1.722
46.020
31.695
36014.688
35111.994
0.000
0.609
0.000
27.343
0.000
4491.569
Instance4864.12
14.798
1.665
45.474
31.295
35540.758
35086.833
0.000
0.567
0.000
26.784
0.000
4482.916
29
Background Database Maintenance I/O Performance

MSExchange Database ==> Instances
Database Maintenance IO Reads/sec
Database Maintenance IO Reads Average Bytes
Instance4864.1
36.952
261592.806
Instance4864.2
37.967
261564.955
Instance4864.3
38.498
261565.362
Instance4864.4
37.390
261564.033
Instance4864.5
37.321
261566.502
Instance4864.6
37.324
261562.905
Instance4864.7
37.711
261531.837
Instance4864.8
37.627
261545.079
Instance4864.9
37.230
261576.024
Instance4864.10
37.637
261511.389
Instance4864.11
38.023
261553.357
Instance4864.12
38.392
261611.486
30
Log Replication I/O Performance

I/O Log Reads/sec
I/O Log Reads Average Bytes
Instance4864.1
0.492
187291.159
Instance4864.2
0.493
184733.150
Instance4864.3
0.487
185437.696
Instance4864.4
0.493
188282.133
Instance4864.5
0.484
183901.456
Instance4864.6
0.497
185820.071
Instance4864.7
0.489
185609.764
Instance4864.8
0.490
183294.436
Instance4864.9
0.498
189655.606
Instance4864.10
0.491
185368.279
Instance4864.11
0.494
189881.207
Instance4864.12
0.484
183228.694
31
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
Instance4864.1
16.762
1.811
82.738
31.486
136502.624
35076.032
21.723
0.693
0.492
27.086
187291.159
4504.003
Instance4864.2
14.947
1.552
83.990
31.795
137804.934
35117.765
16.281
0.576
0.493
27.141
184733.150
4495.664
Instance4864.3
14.797
1.620
84.233
31.434
138914.879
35069.857
14.001
0.608
0.487
27.033
185437.696
4470.863
Instance4864.4
15.180
1.470
83.054
31.473
137378.707
35184.715
16.687
0.562
0.493
27.151
188282.133
4506.855
Instance4864.5
15.255
1.766
82.428
30.934
137949.726
35064.040
21.018
0.659
0.484
26.684
183901.456
4496.011
Instance4864.6
15.379
1.526
83.401
31.784
136849.725
35153.600
15.399
0.574
0.497
27.514
185820.071
4489.875
Instance4864.7
15.222
1.710
84.029
31.956
136869.374
35030.026
16.333
0.597
0.489
27.385
185609.764
4434.772
Instance4864.8
15.161
1.596
83.396
31.475
137547.013
35070.292
14.145
0.565
0.490
27.022
183294.436
4513.524
Instance4864.9
15.360
1.712
83.258
31.769
136697.518
35085.197
22.263
0.627
0.498
27.397
189655.606
4506.956
Instance4864.10
15.132
1.581
83.156
31.264
137936.588
35087.542
16.831
0.544
0.491
26.901
185368.279
4518.610
Instance4864.11
15.021
1.722
84.044
31.695
138053.318
35111.994
18.168
0.609
0.494
27.343
189881.207
4491.569
Instance4864.12
14.798
1.665
83.866
31.295
139031.181
35086.833
14.519
0.567
0.484
26.784
183228.694
4482.916
Host System Performance

Counter
Average
Minimum
Maximum
% Processor Time
1.630
0.000
3.268
Available MBytes
58046.332
58041.000
58343.000
Free System Page Table Entries
33555792.998
33555791.000
33555795.000
Transition Pages RePurposed/sec
0.000
0.000
0.000
Pool Nonpaged Bytes
83833610.154
83783680.000
83976192.000
Pool Paged Bytes
192437348.476
192393216.000
192503808.000
Database Page Fault Stalls/sec
0.000
0.000
0.000
Test Log 9/5/2012 12:24:56 AM -- Jetstress testing begins ...

32
9/5/2012 12:24:56 AM -- Preparing for testing ...

9/5/2012 12:25:09 AM -- Attaching databases ...
9/5/2012 12:25:09 AM -- Preparations for testing are complete.
9/5/2012 12:25:09 AM -- Starting transaction dispatch ..
9/5/2012 12:25:09 AM -- Database cache settings: (minimum: 384.0 MB, maximum: 3.0 GB)
9/5/2012 12:25:09 AM -- Database flush thresholds: (start: 30.7 MB, stop: 61.4 MB)
9/5/2012 12:25:22 AM -- Database read latency thresholds: (average: 20 msec/read, maximum: 100 msec/read).
9/5/2012 12:25:22 AM -- Log write latency thresholds: (average: 10 msec/write, maximum: 100 msec/write).
9/5/2012 12:25:32 AM -- Operation mix: Sessions 6, Inserts 40%, Deletes 20%, Replaces 5%, Reads 35%, Lazy Commits 70%.
9/5/2012 12:25:32 AM -- Performance logging started (interval: 15000 ms).
9/5/2012 12:25:32 AM -- Attaining prerequisites:
9/5/2012 12:30:02 AM -- \MSExchange Database(JetstressWin)\Database Cache Size, Last: 2910351000.0 (lower bound: 2899103000.0,
upper bound: none)
9/5/2012 2:30:02 AM -- Performance logging has ended.
9/5/2012 2:53:47 AM -- JetInterop batch transaction stats: 21298, 21413, 21288, 21308, 21103, 21307, 21437, 21313, 21307, 21210, 21350
and 20988.
9/5/2012 2:53:49 AM -- Dispatching transactions ends.
9/5/2012 2:53:49 AM -- Shutting down databases ...
9/5/2012 2:54:03 AM -- Instance4864.1 (complete), Instance4864.2 (complete), Instance4864.3 (complete), Instance4864.4 (complete),
Instance4864.5 (complete), Instance4864.6 (complete), Instance4864.7 (complete), Instance4864.8 (complete), Instance4864.9 (complete),
Instance4864.10 (complete), Instance4864.11 (complete) and Instance4864.12 (complete)
9/5/2012 2:54:03 AM -- C:\HUS130_PE104_CB15_SAS7K_ESRP_R10_3GB Mbox_36000Users\Performance
Test\Checksum\Performance_2012_9_5_0_25_22.blg has 496 samples.
9/5/2012 2:54:03 AM -- Creating test report ...
9/5/2012 2:54:08 AM -- Instance4864.1 has 16.8 for I/O Database Reads Average Latency.
9/5/2012 2:54:08 AM -- Instance4864.1 has 0.7 for I/O Log Writes Average Latency.
9/5/2012 2:54:08 AM -- Instance4864.1 has 0.7 for I/O Log Reads Average Latency.
33
9/5/2012 2:54:08 AM -- Test has 0 Maximum Database Page Fault Stalls/sec.
9/5/2012 2:54:08 AM -- The test has 0 Database Page Fault Stalls/sec samples higher than 0.
Test\Checksum\Performance_2012_9_5_0_25_22.xml has 478 samples queried.
34
Performance Test Database Checksum Result: CB15

Checksum Statistics - All
Database
Seen pages
Bad pages
Correctable pages
Wrong page-number pages
File length / seconds taken
C:\dbluns\db1\Jetstress001001.edb
22411314
700353 MB/26640 sec
22409266
700289 MB/26133 sec
22408498
700265 MB/18926 sec
22411826
700369 MB/18867 sec
22409778
700305 MB/26394 sec
22409778
700305 MB/26161 sec
22411314
700353 MB/26257 sec
22409266
700289 MB/26122 sec
22410546
700329 MB/19158 sec
22410034
700313 MB/18872 sec
22411314
700353 MB/26281 sec
22410034
700313 MB/26096 sec
(Sum)
268922968
8403842 MB/26640 sec
35
Disk Subsystem Performance (of checksum)

LogicalDisk
Avg. Disk sec/Read
Avg. Disk sec/Write
Disk Reads/sec
Disk Writes/sec
Avg. Disk Bytes/Read
C:\dbluns\db1
0.061
0.000
419.939
0.000
65536.000
C:\dbluns\db2
0.060
0.000
428.620
0.000
65536.000
C:\dbluns\db3
0.042
0.000
591.794
0.000
65536.000
C:\dbluns\db4
0.042
0.000
593.814
0.000
65536.000
C:\dbluns\db5
0.060
0.000
424.423
0.000
65536.000
C:\dbluns\db6
0.059
0.000
427.780
0.000
65536.000
C:\dbluns\db7
0.060
0.000
426.560
0.000
65536.000
C:\dbluns\db8
0.060
0.000
428.896
0.000
65536.000
C:\dbluns\db9
0.042
0.000
584.757
0.000
65536.000
C:\dbluns\db10
0.042
0.000
593.493
0.000
65536.000
C:\dbluns\db11
0.060
0.000
425.961
0.000
65536.000
C:\dbluns\db12
0.059
0.000
429.290
0.000
65536.000
Memory System Performance (of checksum)

Counter
Average
Minimum
Maximum
% Processor Time
1.674
0.619
3.293
Available MBytes
61240.777
61224.000
61260.000
33555793.001
33555792.000
33555795.000
0.000
0.000
0.000
Pool Nonpaged Bytes
84403039.531
84103168.000
84770816.000
Pool Paged Bytes
192986872.785
192737280.000
193081344.000

9/5/2012 12:25:09 AM -- Starting transaction dispatch ..
9/5/2012 12:25:09 AM -- Database cache settings: (minimum: 384.0 MB, maximum: 3.0 GB)
36
9/5/2012 12:25:09 AM -- Database flush thresholds: (start: 30.7 MB, stop: 61.4 MB)
9/5/2012 12:25:22 AM -- Database read latency thresholds: (average: 20 msec/read, maximum: 100 msec/read).
9/5/2012 12:25:22 AM -- Log write latency thresholds: (average: 10 msec/write, maximum: 100 msec/write).
9/5/2012 12:25:32 AM -- Operation mix: Sessions 6, Inserts 40%, Deletes 20%, Replaces 5%, Reads 35%, Lazy Commits 70%.
9/5/2012 12:25:32 AM -- Attaining prerequisites:
9/5/2012 12:30:02 AM -- \MSExchange Database(JetstressWin)\Database Cache Size, Last: 2910351000.0 (lower bound: 2899103000.0,
upper bound: none)
9/5/2012 2:53:47 AM -- JetInterop batch transaction stats: 21298, 21413, 21288, 21308, 21103, 21307, 21437, 21313, 21307, 21210, 21350
and 20988.
9/5/2012 2:53:49 AM -- Dispatching transactions ends.
9/5/2012 2:53:49 AM -- Shutting down databases ...
9/5/2012 2:54:03 AM -- Instance4864.1 (complete), Instance4864.2 (complete), Instance4864.3 (complete), Instance4864.4 (complete),
Test\Checksum\Performance_2012_9_5_0_25_22.blg has 496 samples.
9/5/2012 2:54:03 AM -- Creating test report ...
37
9/5/2012 2:54:08 AM -- Test has 0 Maximum Database Page Fault Stalls/sec.
9/5/2012 2:54:08 AM -- The test has 0 Database Page Fault Stalls/sec samples higher than 0.
Test\Checksum\Performance_2012_9_5_0_25_22.xml has 478 samples queried.
Test\Checksum\Performance_2012_9_5_0_25_22.html was saved.
9/5/2012 2:54:09 AM -- Verifying database checksums ...
9/5/2012 10:18:09 AM -- C:\dbluns\db1 (100% processed), C:\dbluns\db2 (100% processed), C:\dbluns\db3 (100% processed), C:\dbluns\db4
(100% processed), C:\dbluns\db5 (100% processed), C:\dbluns\db6 (100% processed), C:\dbluns\db7 (100% processed), C:\dbluns\db8 (100%
processed), C:\dbluns\db9 (100% processed), C:\dbluns\db10 (100% processed), C:\dbluns\db11 (100% processed) and C:\dbluns\db12
(100% processed)
Test\Checksum\DBChecksum_2012_9_5_2_54_8.blg has 887 samples.
38
Stress Test Result Report: CB15

Test Summary
Overall Test Result
Pass
Machine Name
CB15
Test Description
Test Start Time
9/5/2012 8:46:35 PM
Test End Time
9/6/2012 9:25:56 PM
9/5/2012 8:51:47 PM
Collection End Time
9/6/2012 8:51:38 PM
Jetstress Version
14.01.0225.017
ESE Version
14.01.0218.012
Operating System
Performance Log
C:\HUS130_PE104_CB15_SAS7K_ESRP_R10_3GB Mbox_36000Users\Stress Test\Performance_2012_9_5_20_47_0.blg

921.587
Target Transactional I/O per Second
810
8812067815424
8847996223488
12
39

Thread Count
6 (per database)
384.0 MB
3072.0 MB
Insert Operations
40%
Delete Operations
20%
Replace Operations
5%
Read Operations
35%
Lazy Commits
70%
Run Background Database Maintenance
True
Number of Copies per Database
40
Instance4864.1

Instance4864.2

Instance4864.3

Instance4864.4

Instance4864.5

Instance4864.6

Instance4864.7

Instance4864.8

Instance4864.9

Instance4864.10

Instance4864.11

Instance4864.12

41
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
Instance4864.1
17.280
1.744
45.371
31.258
35503.859
35053.512
0.000
0.635
0.000
26.708
0.000
4489.100
Instance4864.2
15.450
1.532
45.714
31.553
35694.551
35056.825
0.000
0.552
0.000
27.018
0.000
4470.569
Instance4864.3
15.368
1.570
45.298
31.221
35730.287
35056.529
0.000
0.595
0.000
26.782
0.000
4482.365
Instance4864.4
15.315
1.509
45.383
31.281
35716.982
35089.461
0.000
0.554
0.000
26.893
0.000
4489.500
Instance4864.5
15.508
1.664
45.387
31.279
35721.603
35041.718
0.000
0.635
0.000
26.656
0.000
4487.812
Instance4864.6
15.421
1.499
45.452
31.355
35771.783
35068.339
0.000
0.554
0.000
26.943
0.000
4483.975
Instance4864.7
15.367
1.634
45.615
31.472
35696.710
35072.363
0.000
0.591
0.000
26.978
0.000
4493.632
Instance4864.8
15.290
1.575
45.400
31.303
35729.235
35068.017
0.000
0.544
0.000
26.892
0.000
4484.210
Instance4864.9
15.455
1.715
45.386
31.300
35749.605
35062.470
0.000
0.621
0.000
26.771
0.000
4492.124
Instance4864.10
15.367
1.553
45.625
31.499
35783.706
35080.416
0.000
0.539
0.000
27.048
0.000
4491.895
Instance4864.11
15.423
1.690
45.389
31.278
35788.086
35069.378
0.000
0.587
0.000
26.779
0.000
4485.579
Instance4864.12
15.362
1.635
45.436
31.332
35762.415
35068.266
0.000
0.543
0.000
26.913
0.000
4483.967
42

Instance4864.1
35.610
261535.812
Instance4864.2
37.120
261522.853
Instance4864.3
37.228
261528.629
Instance4864.4
37.321
261520.552
Instance4864.5
37.045
261544.944
Instance4864.6
37.154
261532.959
Instance4864.7
37.312
261527.979
Instance4864.8
37.408
261535.151
Instance4864.9
37.089
261517.473
Instance4864.10
37.265
261540.253
Instance4864.11
37.098
261533.788
Instance4864.12
37.197
261531.258
43
Log Replication I/O Performance

I/O Log Reads/sec
I/O Log Reads Average Bytes
Instance4864.1
0.483
185293.635
Instance4864.2
0.487
185564.183
Instance4864.3
0.484
185037.682
Instance4864.4
0.486
185683.720
Instance4864.5
0.482
185150.384
Instance4864.6
0.486
185522.861
Instance4864.7
0.488
187640.657
Instance4864.8
0.486
185245.331
Instance4864.9
0.484
185712.981
Instance4864.10
0.489
186896.390
Instance4864.11
0.484
185347.149
Instance4864.12
0.486
185886.589
44
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
Instance4864.1
17.280
1.744
80.981
31.258
134897.955
35053.512
22.128
0.635
0.483
26.708
185293.635
4489.100
Instance4864.2
15.450
1.532
82.834
31.553
136894.366
35056.825
17.246
0.552
0.487
27.018
185564.183
4470.569
Instance4864.3
15.368
1.570
82.527
31.221
137589.541
35056.529
14.826
0.595
0.484
26.782
185037.682
4482.365
Instance4864.4
15.315
1.509
82.704
31.281
137612.277
35089.461
17.142
0.554
0.486
26.893
185683.720
4489.500
Instance4864.5
15.508
1.664
82.432
31.279
137206.697
35041.718
21.088
0.635
0.482
26.656
185150.384
4487.812
Instance4864.6
15.421
1.499
82.606
31.355
137314.368
35068.339
15.964
0.554
0.486
26.943
185522.861
4483.975
Instance4864.7
15.367
1.634
82.927
31.472
137306.988
35072.363
17.815
0.591
0.488
26.978
187640.657
4493.632
Instance4864.8
15.290
1.575
82.808
31.303
137736.223
35068.017
16.005
0.544
0.486
26.892
185245.331
4484.210
Instance4864.9
15.455
1.715
82.475
31.300
137276.583
35062.470
21.699
0.621
0.484
26.771
185712.981
4492.124
Instance4864.10
15.367
1.553
82.890
31.499
137277.258
35080.416
17.569
0.539
0.489
27.048
186896.390
4491.895
Instance4864.11
15.423
1.690
82.488
31.278
137315.973
35069.378
17.100
0.587
0.484
26.779
185347.149
4485.579
Instance4864.12
15.362
1.635
82.633
31.332
137390.718
35068.266
14.585
0.543
0.486
26.913
185886.589
4483.967

Counter
Average
Minimum
Maximum
% Processor Time
1.635
0.000
4.268
Available MBytes
58027.602
57999.000
58246.000
33555792.995
33555791.000
33555795.000
0.000
0.000
0.000
Pool Nonpaged Bytes
83791866.294
83746816.000
83906560.000
Pool Paged Bytes
194323357.041
193605632.000
235577344.000
0.000
0.000
0.000
Test Log 9/5/2012 8:46:35 PM -- Jetstress testing begins ...

45
9/5/2012 8:46:35 PM -- Preparing for testing ...

9/5/2012 8:46:47 PM -- Attaching databases ...
9/5/2012 8:46:47 PM -- Preparations for testing are complete.
9/5/2012 8:46:47 PM -- Starting transaction dispatch ..
9/5/2012 8:46:47 PM -- Database cache settings: (minimum: 384.0 MB, maximum: 3.0 GB)
9/5/2012 8:46:47 PM -- Database flush thresholds: (start: 30.7 MB, stop: 61.4 MB)
9/5/2012 8:47:00 PM -- Database read latency thresholds: (average: 20 msec/read, maximum: 100 msec/read).
9/5/2012 8:47:00 PM -- Log write latency thresholds: (average: 10 msec/write, maximum: 100 msec/write).
9/5/2012 8:47:10 PM -- Operation mix: Sessions 6, Inserts 40%, Deletes 20%, Replaces 5%, Reads 35%, Lazy Commits 70%.
9/5/2012 8:47:10 PM -- Performance logging started (interval: 15000 ms).
9/5/2012 8:47:10 PM -- Attaining prerequisites:
9/5/2012 8:51:47 PM -- \MSExchange Database(JetstressWin)\Database Cache Size, Last: 2899202000.0 (lower bound: 2899103000.0, upper
bound: none)
9/6/2012 8:51:47 PM -- Performance logging has ended.
9/6/2012 9:25:47 PM -- JetInterop batch transaction stats: 209385, 210645, 208991, 209979, 208966, 210052, 211088, 210257, 209946,
210903, 209259 and 210045.
9/6/2012 9:25:49 PM -- Dispatching transactions ends.
9/6/2012 9:25:49 PM -- Shutting down databases ...
9/6/2012 9:25:56 PM -- Instance4864.1 (complete), Instance4864.2 (complete), Instance4864.3 (complete), Instance4864.4 (complete),
9/6/2012 9:25:56 PM -- C:\HUS130_PE104_CB15_SAS7K_ESRP_R10_3GB Mbox_36000Users\Stress
Test\Performance_2012_9_5_20_47_0.blg has 5761 samples.
9/6/2012 9:25:56 PM -- Creating test report ...
9/6/2012 9:26:49 PM -- Instance4864.1 has 17.3 for I/O Database Reads Average Latency.
9/6/2012 9:26:49 PM -- Instance4864.1 has 0.6 for I/O Log Writes Average Latency.
9/6/2012 9:26:49 PM -- Instance4864.1 has 0.6 for I/O Log Reads Average Latency.
46
9/6/2012 9:26:49 PM -- Test has 0 Maximum Database Page Fault Stalls/sec.
9/6/2012 9:26:49 PM -- The test has 0 Database Page Fault Stalls/sec samples higher than 0.
Test\Performance_2012_9_5_20_47_0.xml has 5742 samples queried.
47
Stress Test Database Checksums Result: CB15

Checksum Statistics - All
Database
Seen pages
Bad pages
Correctable pages
Wrong page-number pages
File length / seconds taken
22501938
703185 MB/26845 sec
22500914
703153 MB/26275 sec
22499378
703105 MB/19159 sec
22503218
703225 MB/18979 sec
22500658
703145 MB/26584 sec
22501426
703169 MB/26192 sec
22502962
703217 MB/26448 sec
22500914
703153 MB/26200 sec
22501938
703185 MB/19312 sec
22502450
703201 MB/18941 sec
22502194
703193 MB/26329 sec
22501426
703169 MB/26247 sec
(Sum)
270019416
8438106 MB/26845 sec
48
Disk Subsystem Performance (of checksum)

LogicalDisk
Avg. Disk sec/Read
Avg. Disk sec/Write
Disk Reads/sec
Disk Writes/sec
Avg. Disk Bytes/Read
C:\dbluns\db1
0.061
0.000
418.467
0.000
65536.000
C:\dbluns\db2
0.060
0.000
427.696
0.000
65536.000
C:\dbluns\db3
0.042
0.000
586.832
0.000
65536.000
C:\dbluns\db4
0.042
0.000
592.468
0.000
65536.000
C:\dbluns\db5
0.060
0.000
422.379
0.000
65536.000
C:\dbluns\db6
0.059
0.000
429.240
0.000
65536.000
C:\dbluns\db7
0.060
0.000
424.838
0.000
65536.000
C:\dbluns\db8
0.060
0.000
428.999
0.000
65536.000
C:\dbluns\db9
0.043
0.000
582.130
0.000
65536.000
C:\dbluns\db10
0.042
0.000
593.683
0.000
65536.000
C:\dbluns\db11
0.060
0.000
427.018
0.000
65536.000
C:\dbluns\db12
0.060
0.000
428.200
0.000
65536.000
Memory System Performance (of checksum)

Counter
Average
Minimum
Maximum
% Processor Time
1.682
0.000
2.914
Available MBytes
61203.798
61188.000
61224.000
33555793.000
33555791.000
33555795.000
0.000
0.000
0.000
Pool Nonpaged Bytes
84074940.421
83992576.000
84234240.000
Pool Paged Bytes
200703505.181
200568832.000
204472320.000

49
9/5/2012 8:47:10 PM -- Attaining prerequisites:
9/5/2012 8:51:47 PM -- \MSExchange Database(JetstressWin)\Database Cache Size, Last: 2899202000.0 (lower bound: 2899103000.0, upper
bound: none)
9/6/2012 9:25:47 PM -- JetInterop batch transaction stats: 209385, 210645, 208991, 209979, 208966, 210052, 211088, 210257, 209946,
210903, 209259 and 210045.
Test\Performance_2012_9_5_20_47_0.blg has 5761 samples.
50
Test\Performance_2012_9_5_20_47_0.xml has 5742 samples queried.
Test\Performance_2012_9_5_20_47_0.html was saved.
9/6/2012 9:26:50 PM -- Verifying database checksums ...
9/7/2012 4:54:16 AM -- C:\dbluns\db1 (100% processed), C:\dbluns\db2 (100% processed), C:\dbluns\db3 (100% processed), C:\dbluns\db4
(100% processed), C:\dbluns\db5 (100% processed), C:\dbluns\db6 (100% processed), C:\dbluns\db7 (100% processed), C:\dbluns\db8 (100%
processed), C:\dbluns\db9 (100% processed), C:\dbluns\db10 (100% processed), C:\dbluns\db11 (100% processed) and C:\dbluns\db12
(100% processed)
9/7/2012 4:54:16 AM -- C:\HUS130_PE104_CB15_SAS7K_ESRP_R10_3GB Mbox_36000Users\Stress
Test\DBChecksum_2012_9_6_21_26_49.blg has 894 samples.
51
Backup Test Result Report: CB15

Database Backup Statistics - All
Database Instance
Database Size (MBytes)
Elapsed Backup Time
MBytes Transferred/sec
Instance4864.1
703177.59
03:08:11
62.27
Instance4864.2
703145.59
03:55:57
49.67
Instance4864.3
703097.59
03:51:34
50.60
Instance4864.4
703217.59
03:49:12
51.13
Instance4864.5
703137.59
03:59:24
48.95
Instance4864.6
703161.59
03:54:40
49.94
Instance4864.7
703209.59
04:00:08
48.81
Instance4864.8
703145.59
03:51:37
50.59
Instance4864.9
703177.59
03:59:59
48.83
Instance4864.10
703193.59
03:51:03
50.72
Instance4864.11
703185.59
03:55:28
49.77
Instance4864.12
703161.59
03:56:48
49.49

Thread Count
6 (per database)
384.0 MB
3072.0 MB
Insert Operations
40%
Delete Operations
20%
Replace Operations
5%
Read Operations
35%
Lazy Commits
70%
52
Instance4864.1

Instance4864.2

Instance4864.3

Instance4864.4

Instance4864.5

Instance4864.6

Instance4864.7

Instance4864.8

Instance4864.9

Instance4864.10

Instance4864.11

Instance4864.12

53
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
Instance4864.1
6.013
0.000
248.957
0.000
262144.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
Instance4864.2
8.124
0.000
198.173
0.000
262144.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
Instance4864.3
8.020
0.000
201.706
0.000
262144.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
Instance4864.4
7.575
0.000
204.258
0.000
262144.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
Instance4864.5
10.698
0.000
195.360
0.000
262144.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
Instance4864.6
8.798
0.000
199.162
0.000
262144.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
Instance4864.7
10.186
0.000
194.165
0.000
262144.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
Instance4864.8
7.762
0.000
201.520
0.000
262144.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
Instance4864.9
12.585
0.000
194.613
0.000
262144.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
Instance4864.10
7.606
0.000
202.236
0.000
262144.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
Instance4864.11
8.504
0.000
198.403
0.000
262144.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
Instance4864.12
8.971
0.000
197.666
0.000
262144.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000

Counter
Average
Minimum
Maximum
% Processor Time
1.497
0.421
2.677
Available MBytes
61207.474
61192.000
61209.000
33555793.015
33555792.000
33555795.000
0.000
0.000
0.000
Pool Nonpaged Bytes
83934188.760
83918848.000
84013056.000
Pool Paged Bytes
200173298.639
199471104.000
201224192.000
0.000
0.000
0.000
54

9/7/2012 10:40:46 AM -- Backing up databases ...
9/7/2012 2:40:54 PM -- Instance4864.1 (100% processed), Instance4864.2 (100% processed), Instance4864.3 (100% processed),
Instance4864.4 (100% processed), Instance4864.5 (100% processed), Instance4864.6 (100% processed), Instance4864.7 (100% processed),
Instance4864.8 (100% processed), Instance4864.9 (100% processed), Instance4864.10 (100% processed), Instance4864.11 (100%
processed) and Instance4864.12 (100% processed)
9/7/2012 2:40:54 PM -- C:\HUS130_PE104_CB15_SAS7K_ESRP_R10_3GB Mbox_36000Users\Database
Backup\DatabaseBackup_2012_9_7_10_40_28.blg has 479 samples.
55
Soft Recovery Test Result Report: CB15

Soft-Recovery Statistics - All
Database Instance
Log files replayed
Elapsed seconds
Instance4864.1
506
1851.6019056
Instance4864.2
503
1785.6761349
Instance4864.3
513
1795.9507225
Instance4864.4
509
1787.4302352
Instance4864.5
509
1780.9118623
Instance4864.6
505
1773.8924609
Instance4864.7
512
1793.9456078
Instance4864.8
513
1787.9302638
Instance4864.9
508
1782.9179771
Instance4864.10
504
1773.8924609
Instance4864.11
501
1768.8821743
Instance4864.12
501
1754.8503717
56
Instance4864.1

Instance4864.2

Instance4864.3

Instance4864.4

Instance4864.5

Instance4864.6

Instance4864.7

Instance4864.8

Instance4864.9

Instance4864.10

Instance4864.11

Instance4864.12

57
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
Instance4864.1
16.257
0.839
263.237
1.635
40894.889
31623.266
6.639
0.000
2.453
0.000
223761.650
0.000
Instance4864.2
15.328
0.785
275.933
1.687
40630.735
32323.186
6.482
0.001
2.531
0.002
228749.228
1.158
Instance4864.3
15.359
0.811
272.394
1.708
40838.484
32472.793
6.557
0.000
2.563
0.000
230292.653
0.000
Instance4864.4
15.287
0.825
277.607
1.708
40632.720
32619.729
6.733
0.001
2.562
0.002
231452.500
1.158
Instance4864.5
15.295
0.850
278.800
1.712
40559.576
32172.218
6.580
0.000
2.568
0.000
228304.248
0.000
Instance4864.6
15.346
0.749
278.408
1.706
40695.373
32320.146
6.499
0.005
2.559
0.002
228747.827
1.166
Instance4864.7
15.299
0.842
276.794
1.710
40740.347
32103.784
6.220
0.001
2.565
0.002
227301.988
1.153
Instance4864.8
15.298
0.768
280.590
1.718
40632.046
32323.186
6.130
0.000
2.577
0.000
229329.212
0.000
Instance4864.9
15.257
0.849
277.636
1.705
40762.823
32396.481
6.352
0.000
2.557
0.000
229316.504
0.000
Instance4864.10
15.266
0.751
280.534
1.702
40745.163
32245.503
6.523
0.001
2.554
0.002
228143.392
1.166
Instance4864.11
15.289
0.802
282.714
1.697
40630.985
32168.128
6.917
0.000
2.545
0.000
227561.938
0.000
Instance4864.12
15.304
0.785
276.238
1.708
40698.455
32314.986
6.540
0.000
2.562
0.000
228769.601
0.000
58

Instance4864.1
37.336
261720.004
Instance4864.2
37.681
261651.970
Instance4864.3
37.931
261674.289
Instance4864.4
37.786
261632.956
Instance4864.5
37.582
261651.787
Instance4864.6
37.365
261702.710
Instance4864.7
37.854
261567.631
Instance4864.8
37.550
261530.188
Instance4864.9
38.044
261605.934
Instance4864.10
37.429
261444.206
Instance4864.11
36.840
261700.682
Instance4864.12
37.257
261592.761
59
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
Instance4864.1
16.257
0.839
300.574
1.635
68325.086
31623.266
6.639
0.000
2.453
0.000
223761.650
0.000
Instance4864.2
15.328
0.785
313.613
1.687
67186.429
32323.186
6.482
0.001
2.531
0.002
228749.228
1.158
Instance4864.3
15.359
0.811
310.325
1.708
67831.144
32472.793
6.557
0.000
2.563
0.000
230292.653
0.000
Instance4864.4
15.287
0.825
315.393
1.708
67110.001
32619.729
6.733
0.001
2.562
0.002
231452.500
1.158
Instance4864.5
15.295
0.850
316.382
1.712
66822.543
32172.218
6.580
0.000
2.568
0.000
228304.248
0.000
Instance4864.6
15.346
0.749
315.773
1.706
66847.168
32320.146
6.499
0.005
2.559
0.002
228747.827
1.166
Instance4864.7
15.299
0.842
314.648
1.710
67306.972
32103.784
6.220
0.001
2.565
0.002
227301.988
1.153
Instance4864.8
15.298
0.768
318.139
1.718
66704.512
32323.186
6.130
0.000
2.577
0.000
229329.212
0.000
Instance4864.9
15.257
0.849
315.680
1.705
67377.942
32396.481
6.352
0.000
2.557
0.000
229316.504
0.000
Instance4864.10
15.266
0.751
317.962
1.702
66724.613
32245.503
6.523
0.001
2.554
0.002
228143.392
1.166
Instance4864.11
15.289
0.802
319.554
1.697
66117.345
32168.128
6.917
0.000
2.545
0.000
227561.938
0.000
Instance4864.12
15.304
0.785
313.495
1.708
66950.619
32314.986
6.540
0.000
2.562
0.000
228769.601
0.000

Counter
Average
Minimum
Maximum
% Processor Time
1.906
0.000
7.263
Available MBytes
58079.083
58000.000
60775.000
33555793.100
33555791.000
33555795.000
0.000
0.000
0.000
Pool Nonpaged Bytes
84188684.270
84156416.000
84496384.000
Pool Paged Bytes
201138122.458
201113600.000
201261056.000
0.000
0.000
0.000

60

9/7/2012 6:44:07 PM -- Generating log files ...
9/7/2012 9:05:58 PM -- C:\logluns\log1 (101.2% generated), C:\logluns\log2 (100.6% generated), C:\logluns\log3 (102.6% generated),
C:\logluns\log4 (101.8% generated), C:\logluns\log5 (101.8% generated), C:\logluns\log6 (101.0% generated), C:\logluns\log7 (102.4%
generated), C:\logluns\log8 (102.6% generated), C:\logluns\log9 (101.6% generated), C:\logluns\log10 (100.8% generated), C:\logluns\log11
(100.2% generated) and C:\logluns\log12 (100.2% generated)
9/7/2012 9:05:58 PM -- JetInterop batch transaction stats: 22247, 22166, 22286, 22336, 22301, 21964, 22459, 22524, 22236, 22252, 22185
and 22033.
9/7/2012 9:06:01 PM -- C:\HUS130_PE104_CB15_SAS7K_ESRP_R10_3GB Mbox_36000Users\Soft
Recovery\Performance_2012_9_7_18_44_1.blg has 566 samples.
61
Recovery\Performance_2012_9_7_18_44_1.xml has 565 samples queried.
Recovery\Performance_2012_9_7_18_44_1.html was saved.
9/7/2012 9:58:01 PM -- Recovering databases ...
9/7/2012 10:28:53 PM -- Instance4864.1 (1851.6019056), Instance4864.2 (1785.6761349), Instance4864.3 (1795.9507225), Instance4864.4
(1787.4302352), Instance4864.5 (1780.9118623), Instance4864.6 (1773.8924609), Instance4864.7 (1793.9456078), Instance4864.8
(1787.9302638), Instance4864.9 (1782.9179771), Instance4864.10 (1773.8924609), Instance4864.11 (1768.8821743) and Instance4864.12
(1754.8503717)
62
Recovery\SoftRecovery_2012_9_7_21_57_55.blg has 459 samples.

Soft Recovery Test Performance Result: CB15

Test Summary
Overall Test Result
Fail
Machine Name
CB15
Test Description
Test Start Time
9/7/2012 6:43:36 PM
Test End Time
9/7/2012 9:06:01 PM
9/7/2012 6:44:22 PM
Collection End Time
9/7/2012 9:05:55 PM
Jetstress Version
14.01.0225.017
ESE Version
14.01.0218.012
Operating System
Performance Log
C:\HUS130_PE104_CB15_SAS7K_ESRP_R10_3GB Mbox_36000Users\Soft Recovery\Performance_2012_9_7_18_44_1.blg
Test Issues
Fail
The process has average database read latencies higher than 20.000 msec.

1013.821
Capacity Percentage
100%
Throughput Percentage
100%
8847996223488
8851829817344
12
63

Thread Count
6 (per database)
384.0 MB
3072.0 MB
Insert Operations
40%
Delete Operations
20%
Replace Operations
5%
Read Operations
35%
Lazy Commits
70%
64
Instance4864.1

Instance4864.2

Instance4864.3

Instance4864.4

Instance4864.5

Instance4864.6

Instance4864.7

Instance4864.8

Instance4864.9

Instance4864.10

Instance4864.11

Instance4864.12

65
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
Instance4864.1
22.291
2.721
50.745
34.424
32768.000
34992.960
0.000
0.510
0.000
29.561
0.000
4470.918
Instance4864.2
20.352
2.467
49.935
33.865
32768.000
35068.739
0.000
0.460
0.000
29.406
0.000
4470.202
Instance4864.3
20.289
2.648
50.055
34.050
32768.000
35121.776
0.000
0.479
0.000
29.712
0.000
4513.226
Instance4864.4
20.318
2.805
50.396
34.315
32768.000
35070.313
0.000
0.461
0.000
29.797
0.000
4471.898
Instance4864.5
20.427
3.143
50.311
34.235
32768.000
35079.946
0.000
0.509
0.000
29.660
0.000
4486.126
Instance4864.6
20.382
3.155
50.025
33.998
32768.000
35062.216
0.000
0.461
0.000
29.435
0.000
4492.151
Instance4864.7
20.313
3.546
50.572
34.487
32768.000
35080.461
0.000
0.463
0.000
29.956
0.000
4464.944
Instance4864.8
20.279
3.774
50.929
34.812
32768.000
35103.538
0.000
0.442
0.000
30.083
0.000
4455.448
Instance4864.9
20.352
4.136
50.253
34.133
32768.000
35057.174
0.000
0.503
0.000
29.541
0.000
4494.783
Instance4864.10
20.329
4.178
50.372
34.227
32768.000
35056.525
0.000
0.453
0.000
29.736
0.000
4430.965
Instance4864.11
20.335
4.437
50.498
34.283
32768.000
35026.632
0.000
0.470
0.000
29.456
0.000
4440.220
Instance4864.12
20.217
4.568
49.484
33.417
32768.000
35097.767
0.000
0.449
0.000
29.075
0.000
4501.394

Counter
Average
Minimum
Maximum
% Processor Time
1.513
0.000
3.171
Available MBytes
58074.648
58030.000
60668.000
33555793.030
33555792.000
33555795.000
0.000
0.000
0.000
Pool Nonpaged Bytes
84353313.470
83886080.000
84582400.000
Pool Paged Bytes
200890165.371
200654848.000
201060352.000
0.000
0.000
0.000
66

9/7/2012 6:44:07 PM -- Generating log files ...
9/7/2012 9:05:58 PM -- C:\logluns\log1 (101.2% generated), C:\logluns\log2 (100.6% generated), C:\logluns\log3 (102.6% generated),
C:\logluns\log4 (101.8% generated), C:\logluns\log5 (101.8% generated), C:\logluns\log6 (101.0% generated), C:\logluns\log7 (102.4%
generated), C:\logluns\log8 (102.6% generated), C:\logluns\log9 (101.6% generated), C:\logluns\log10 (100.8% generated), C:\logluns\log11
(100.2% generated) and C:\logluns\log12 (100.2% generated)
9/7/2012 9:05:58 PM -- JetInterop batch transaction stats: 22247, 22166, 22286, 22336, 22301, 21964, 22459, 22524, 22236, 22252, 22185
and 22033.
Recovery\Performance_2012_9_7_18_44_1.blg has 566 samples.
67
Recovery\Performance_2012_9_7_18_44_1.xml has 565 samples queried.
68
Hitachi Data Systems Corporation 2012. All rights reserved. HITACHI is a trademark or registered trademark of Hitachi, Ltd. Microsoft,
Exchange 2010, and Exchange Server 2010 are trademarks or registered trademarks of Microsoft Corporation. All other trademarks,
service marks, and company names are properties of their respective owners..
Notice: This document is for informational purposes only, and does not set forth any warranty, expressed or implied, concerning any
equipment or service offered or to be offered by Hitachi Data Systems Corporation.
Hitachi Data Systems Corporation 2012. All Rights Reserved. ESRP- 083-00 July 2012
Corporate Headquarters
2845 Lafayette Street,
Santa Clara, California 95050-2639 USA
www.HDS.com
Regional Contact Information

Americas: +1 408 970 1000 or info@hds.com
Europe, Middle East and Africa: +44 (0) 1753 618000 or info.emea@hds.com
Asia Pacific: +852 3189 7900 or hds.marketing.apac@hds.com
69

Hus 130 Dynamically Provisioned 36000 Mailbox Exchange Storage Solution PDF

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Hus 130 Dynamically Provisioned 36000 Mailbox Exchange Storage Solution PDF

Diunggah oleh

Hak Cipta:

Format Tersedia

1

Hitachi Unified Storage 130 Dynamically

Notices and Disclaimer

Hitachi Unified Storage 130 Dynamically

Two six-core Intel Xeon X5690 3.46 GHz CPUs

Microsoft Windows Server 2008 R2 Enterprise

240 2TB 7.2K RPM SAS disks

16 8 Gb/sec paths used

Server processor utilization

Server physical and virtual memory limitations

Resource requirements for other applications

Directory and network service latencies

Network infrastructure limitations

Replication and recovery requirements

Client usage profiles

Targeted Customer Profile

Sixteen Exchange servers (8 tested, 8 simulated for the database copies)

Two Hitachi Unified Storage 130 (one tested)

0.15 IOPS per user (0.18 tested for 20 percent growth)

Hitachi Unified Storage RAID protection against physical failure or loss.

24x7 background database maintenance enabled.

Number of database availability groups (DAGs)

Number of servers per DAG

Number of active mailboxes per server

Number of databases per host

Number of copies per database

Number of mailboxes per database

Total database size for performance testing

% storage capacity used by Exchange database**

Storage model and OS/firmware revision

Number of storage controllers

Number of storage ports

Maximum bandwidth of storage connectivity to host

128 Gb/sec (16 8

Switch type/model/firmware revision

Brocade 5300, Fabric

HBA model and firmware

Number of HBAs per host

2 dual-ported HBA per

Host server type

Hitachi Compute Blade

Total number of disks tested in solution

Maximum number of spindles that can be hosted in the storage

Table 8. Storage Software

HBA QueueTarget setting

HBA QueueDepth setting

Hitachi Dynamic Link

ESE.dll file version

Replication solution name/version

Table 9. Storage Disk Configuration (Mailbox Store Disks)

SAS 2TB 7.2K 5C0C

Raw capacity per disk (GB)

Number of physical disks in test

Total raw storage capacity (GB)

Disk slice size (GB)

Number of slices per LU or number of disks per LU

Total formatted capacity

Storage capacity utilization

Database capacity utilization

Table 10. Storage Disk Configuration (Transaction Log Disks)

SAS 2TB 7.2K 5C0C

Raw capacity per disk (GB)