ibm xiv gen3 storage with 3tb drives:120,000 mailbox resiliency for ms exchange 2010

IBM XIV® Gen3 Storage System Model 2810/114 120,000 Mailbox

Resiliency Exchange 2010 Storage Solution

Tested with: ESRP – Storage Version 3.0 Tested Date: Aug 31, 2011 Authors: Aviad Offeri, David Hartmanii, Betti Poratiii Document version: 1.0

IBM XIV® Storage System Model 2810 60,000 Mailbox Resiliency Exchange 2010 Storage

Solution

Aviad Offer, David Hartman, Betti Porat, Betti Porat

©Copyright IBM Corp.20110831

Content Overview ...................................................................................................... 3 Features ....................................................................................................... 3 Solution Description ....................................................................................... 4 XIV Gen3 Storage System Model 2810 Type 114, with 3TB Drives .................................... 4 IBM System x3650 Servers ............................................................................... 10

Solution Description ..................................................................................... 11 Targeted Customer Profile .......................................................................... 16 Tested Deployment ................................................................................... 17 Simulated Exchange Configuration: .......................................................... 17 Storage Hardware .................................................................................. 18 Storage Software ................................................................................... 19 Storage Disk Configuration (Mailbox Store Disks) ....................................... 19 Storage Disk Configuration (Transactional Log Disks) .................................. 19

Best Practices .............................................................................................. 20 Storage Mailbox Resiliency ....................................................................... 20 Backup strategy ........................................................................................ 21

Contact for Additional Information .................................................................. 21 Test Result Summary ................................................................................... 22 Reliability ................................................................................................. 22 Storage Performance Results ...................................................................... 22 Database Backup/Recovery Performance ...................................................... 27 Database Readonly Performance ............................................................. 27 Transaction Log Recovery/Replay Performance ........................................... 27

Conclusion .................................................................................................. 27 Appendix A. Test Results ............................................................................... 28 Stress Testing ........................................................................................... 28 Performance Testing .................................................................................. 32 Streaming Backup Testing .......................................................................... 37 Soft Recovery Testing ................................................................................ 41


Solution



Overview This document provides information on the IBM XIV Gen3 2810 Storage System storage solution for Microsoft Exchange Server, based the Microsoft Exchange Solution Reviewed Program (ESRP) – Storage program*. For any questions or comments regarding the contents of this document, please see the section titled 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 their storage solutions for Microsoft Exchange Server software. For additional information on the Microsoft ESRP – Storage program, please click: http://technet.microsoft.com/enus/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. Please refer to the IBM disclaimer, located at the end of this document for additional information.

Features This solution implements the new Mailbox Resiliency features in Exchange Server 2010; specifically the database availability group feature. A database availability group (DAG) is a set of up to 16 Microsoft Exchange Server 2010 Mailbox servers that work together to provide automatic databaselevel recovery from a database, server, or network failure. Mailbox servers in a DAG monitor each other for failures. Solutions that implement this feature can deliver a very robust Exchange environment. More information on this feature can be found by visiting: http://technet.microsoft.com/enus/library/dd351172%28EXCHG.140%29.aspx A two DAG solution comprising 24 mailbox servers was created that supported a total of 120,000 mailboxes with a mailbox size of 1.5GB. Each server hosted 5,000 users, and had 8 active databases, with 625 users per database. Within each DAG, there were two copies of every database; one local, and one on another server connected to a second XIV Gen3 storage array. This configuration can provide for both highavailability, and disasterrecovery scenarios. Database replication is handled by the mailbox servers over Ethernet. Two XIV Gen3 frames were used, and the databases and copies were equally distributed across them. A failure of any

http://technet.microsoft.com/en-us/library/dd351172%28EXCHG.140%29.aspx

http://technet.microsoft.com/en-us/exchange/ff182054.aspx


Solution



database will cause the database to mount and become active on whichever server is hosting the database copy, in a manner transparent to the end users.

The solution in this paper features the IBM XIV Gen3 Storage System together with IBM System x3650 Intel based servers. The following sections describe the actual hardware components used in this solution.

Solution Description XIV Gen3 Storage System Model 2810 Type 114, with 3TB Drives As one of the newer members of IBM’s family of storage systems, the XIV Gen3 Storage System is an enterpriseclass array offering superior performance, solidprotection, and incredible ease of manageability. This solution leverages the new XIV Gen3 system with 3TB drives with a usable capacity of 243TB per frame. Exclusive to this storage system is the inherent selfoptimizing gridbased architecture which provides massive parallelism. Massive parallelism design distributes data in parallel across all available storage resources, by harnessing all the processing power available to the system. Due to this design, hot spots (heavily saturated storage components) normally associated with poor storage configuration and/or workload variances, is eliminated. The XIV Gen3 architecture delivers continuous optimal performance and eliminates the need for dubious tuning activities on the storage. Built using industrystandard Intel/Linux components a fully equipped XIV Gen3 Model 2810/114 Storage System is supplied with fifteen data modules, 6 out of those are interface modules. Each module consists of one Intel Westmere® Quadcore 64bit CPU, 24 GB fully buffered RAM, and twelve 3TB SAS 7,200 RPM hard disks. In comparison to FibreChannel based disks, the XIV Gen3 has more disk density allowing for a smaller physical storage footprint, which in turn translates to significantly lower power & cooling requirements. The unique design of the architecture can also yield similar or better performance.


Solution



Hardware Highlights Total Storage Central Processing Units 15 Combined Physical Memory 360GB Raw Storage 480TB CPU to Disk Bandwidth 3000GBps Internal Switching Capacity 600Gbps Fibre Channel Ports (Speed: 2 Gbs, 4 Gbs & 8Gbs )

24 x 8Gbs

iSCSI Gigabit Ethernet Ports 22 UPS 3 Infiniband Switch 2 Disk Hot Spares 3 (9TB) Data Module Hot Spare 1 (36TB) Max Snapshots 12,000 Figure 1 below represents a fully configured XIV Gen3 Storage System:

Figure 1) XIV Gen3 front and rear view (full rack)


Solution



Reliability/Protection By design, the XIV Gen3 Storage System architecture is selfhealing as data in the background is automatically checked for integrity and mirrored to provide data redundancy. Should the XIV Gen3 lose a 3TB disk, the system triggers an event alerting IBM support while rebuilding the faulty disk. The disk rebuild process is transparently handled without user intervention and can finish in as few as 80 minutes when the XIV Gen3’s capacity is 100% allocated and written. Consistent performance is maintained even during the loss of a hard disk. The rebuild time of losing one disk does not degrade performance, unlike other competing storage systems which exhibit a significant degradation in performance. Should a storage subcomponent fail on monolithic storage systems, about 50% (CPU and read/write cache) of performance is lost. This not only impacts productivity, but could have serious implications affecting application performance. Losing an entire data module1 on the XIV Gen3 Storage System would temporarily account for only 1/15th reduced performance. To maintain data redundancy, all data on the storage and memory cache is mirrored. The cache data is never stored in the same data module. This not only provides data cache protection, but eliminates loss of data in case a data module’s power is lost or interrupted. Each data module is supplied with two field replaceable hotswappable power supplies, and three UPS devices provide interim power in the event of interrupted or lost main power. Enough power is provided to allow safe cache destaging and a graceful shutdown of the XIV Gen3 Storage System. The XIV Gen3 Storage System also supports synchronous and asynchronous Remote Mirroring, allowing for replication of data to a remote XIV Gen3 Storage System. Additionally, XIV Gen3 now supports seamless integration with Windows Server 2008 R2 clustering, which enables intelligent, automatic failover/failback using arraybased replication, all within the familiar clustering MMC. Thin Provisioning This feature permits the logical allocation of storage to appear larger than what is physically committed. This provides the ability to resize storage pools and volumes even after defining initial storage sizes. This feature cannot only reduce upfront storage costs by avoiding purchasing needless unused storage, but reduces the hardware and the associated 1 Loss of a data module compared to a data interface module has lesser impact in performance.


Solution



environmental footprint. A larger footprint is typically more expensive because it requires more hard disks, electrical power, cooling requirements, disk expansions enclosures, floor space, and management overhead. Thin provisioning can reduce or eliminate the impact of future storage capacity issues when current storage limits have been reached. This occurs when storage has quickly outgrown original capacities. It can be a difficult task to predict how data will grow as storage usage is often highly dynamic in nature. In an effort to circumvent future capacity issues, storage can be appropriately sized beforehand or resized later. Figure 2 below depicts how to easily resize an XIV Gen3 volume.

Figure 2) Resizing an XIV Gen3 volume.

Important: While thin provisioning enables allocated storage to appear larger than what is physically committed, constant monitoring of current available physical storage space is vital to prevent capacity issues. Storage writes destined to logical capacity not allocated with enough physical storage can hinder performance, delete snapshots, and cause storage operations to fail due to lack of space. Prior to reaching this limit, storage threshold alerts should be configured and enabled to warn administrators of the condition. Regular monitoring of storage events and proactive action can prevent these events from occurring. Another innovative feature is the ability to consume disk space only when actual data is written to the volume. This means that while a LUN may be allocated 100GB of capacity, if only 10GB is in actual use, only 10GB is of physically allocated & reported. This concept is referred to as a volume’s hard or physical utilization. This can result in a significant savings in both space and cost. This differs from traditional storage systems, in which the entire preallocated disk space is flagged as 0’s and marked as used storage. Traditional storage systems quickly outgrow space by immediately preallocating storage due to the inefficient method of marking free space as reserved. Whereas on the XIV Gen3 Storage System it is


Solution



tracked by the system as free space, and can be used for other hosts, thus maximizing overall storage utilization. Note: It is important to realize that this concept differs from that of thin provisioning. Also, this feature does not apply to free space within the EDB file(s). Ease of Management Managing the XIV Gen3 Storage System compared to other storage is markedly different. Typical storage management tasks are eliminated and handled automatically by the XIV Gen3 Storage System including automatic provisioning, selftuning of data placement, read/write cache tuning, selfhealing, automatic rebuilding of failed disk drives, and automatic phasingout or fencing of failed components. The modular, redundant architecture dramatically reduces impact to service levels from such events. In general, storage management can be a daunting task, requiring extensive storage experience and specialized training. These barriers have been removed, as the XIV Gen3 Storage System provides a highly intuitive GUI called XIV Gen3 Storage Management, with a near zero learning curve. A less experienced storage administrator with no XIV Gen3 Storage System experience can allocate storage and map volumes to hosts in few minutes. Storage management tasks take less time, allowing storage to be utilized faster.

We assume the host attached to the IBM XIV Gen3 is already configured with the vendor specific SAN drivers and is properly zoned in the SAN fabric or a point-to-point connection is used.


Solution



Figure 3 below is a sample screen shot of the XIV Gen3 Storage Management interface.

Figure 3) The highly intuitive XIV Gen3 Storage Management interface A fullfeatured commandline management interface, XCLI is also provided for scripting tasks, management, configuration, and monitoring. Lower Power Consumption The IBM XIV Gen3 Storage System is equipped with highcapacity SAS disks. SAS disk drives provide significantly better GB/$ value than FibreChannel (FC) disks. SAS disks also require less power consumption than FC disks. Since SAS disk drives are generally much higher in capacity than FC disks – this translates to requiring less hard drives, cooling, and power for a given capacity.


Solution



Snapshots A key component of the XIV Gen3 Storage System is the inherent snapshot capabilities which deliver nearinstantaneous volume replicas**. A total of 12,000 snapshots are supported. A snapshot is simply a pointintime image of data used for quick data retrieval purposes. Transportable snapshots are often use for offloaded backups of Exchange databases, which remove the backup load from the production servers. The snapshot method employed by the XIV Gen3 Storage System uses an efficient method called RedirectonWrite. The RedirectonWrite snapshotbased method addresses the typical performance overhead associated with the CopyonWrite or COW snapshotbased method. For example, during a CopyonWrite snapshot operation, new writes destined to target storage must wait until the original data is copied to the snapshot area. This step is eliminated using RedirectonWrite as the new writes are written immediately to the snapshot area resulting in faster snapshots. The RedirectonWrite snapshot method does not impact the source volumes as do CopyonWrite based snapshots. For more information on the XIV Gen3 Storage System visit the IBM website at: http://www.xivstorage.com http://publib.boulder.ibm.com/infocenter/ibmxiv/r2/index.jsp

IBM System x3650 Servers The System x3650 is a rackmount server designed for critical and highperformance computing. For this particular solution, twelve System x3650 model 7979AC1 systems containing 2 quad core e5450 3.0 GHz Intel Xeon CPUs were used. Each System x3650 was equipped with 24 GB of internal memory. Figure 4 below is a view of the System x3650

** Actual snapshot operation times are measured on the IBM XIV. Monitoring of an ad-hoc or scheduled snapshot operation from the TSM or IBM Data Protection interface known as the VSS requester may appear longer as there is additional communication occurring between the requester client and server.

http://www.xivstorage.com/


Solution



Figure 4) System x3650 server Product specifications below list the actual configuration used in this solution. Product Description Description: IBM System x3650 Form Factor/Height Rack/2U Machine Type/Model: 3650 Part Number: 7979MC1 BIOS Build ID: IBM GGE141AUS

Released: 10/8/2008 Revision: 1.12

Processor Dual 3.0 GHz Intel Xeon QuadCore processors

Physical Memory 24 GB Onboard Network Broadcom Gigabit Ethernet:

Model: BCM5708C NetXtreme II GigE Driver Version: 4.4.15.0

Fibre Channel adapter Qlogic® 8Gb dual port Fiber HBA Expansion (PCIe): HBA Driver Version: Storport 9.1.9.25 HBA Bios: 2.02 HBA Firmware Version: 4.03.01 Part Number: QLE2562

For more information on the current System x3650 M3 offering, please visit the following IBM website: http://www03.ibm.com/systems/x/hardware/rack/x3650m3/index.html

Solution Description This solution demonstrates the performance capabilities utilizing two XIV Gen3 Storage System arrays and 24 System x3650 servers supporting a total of 120,000 mailboxes using a target 0.11 IOP profile (0.11 IOP with added 20% headroom – 0.13 as tested). The mailbox size is 1.5 GB.

http://www-03.ibm.com/systems/x/hardware/rack/x3650m3/index.html


Solution



Important: Though this solution was tested using 120,000 mailboxes, additional storage to accommodate snapshots or frequent mailbox move operations may be required for larger transaction log volumes. Carefully review these parameters before finalizing your final target limits. The astested design allows for a single mailbox server or storage array failure. Storage hardware:

2 x XIV Gen3 Storage Systems Model 2810 Type 114 XIV Gen3 Storage System Software Version: 11.0.0 24 GB physical memory/data module Twelve 3TB drives per data module 180 SAS drives (3TB, 7,200 RPM) per array Form Factor: Rackmount Rack Height: 42u

Exchange servers:

24 x System x3650 servers: o 2 quadcore e5450 3Ghz Intel Xeon CPUs o 24 GB RAM/Server

Windows Server 2008 (x64) – Enterprise Edition, R2, Service Pack 1 o .NET Framework 3.5 o Microsoft Multipath I/O

Qlogic 8Gb dualport Fibre HBA Expansion (PCIe): o HBA Driver Version Storport 9.1.9.25 o HBA BIOS: 2.02 o HBA Firmware Version: 4.03.01

XIV Storage System Host Attachment Package for Windows (x64) – Version 1.6

FibreChannel network:

2 –8 Gb Brocade Model BR48000 Fibre Channel switches 8 –FibreChannel Ports (Tested Speed: 8 Gb) 16 FC LC Fibre Channel 50/125 micrometer shortwave cables 16 Multimode cables (20 meters)


Solution



Figure 5 below depicts a highlevel representation of this solution. Note: The FC switches are not diagrammed to keep the overall diagram simplified. The brackets are to imply each FC switch as described in the section above.

Figure 5) ESRP physical configuration.


Solution



SAN Connectivity

As mentioned in the previous sections, the XIV Gen3 Storage System provides SAN connectivity via 24 FC ports or 22 iSCSI Ethernet ports. For this solution, only the Fibre Channel ports are utilized. The rear of the XIV Gen3 Storage System’s patch panel reveals access to all six host interface modules, each of which contains FC port designations 1, 2, 3, and 4. For each Exchange server, a minimum of 6 paths were used to provide SAN connectivity to the XIV Gen3 Storage System. Two FC switches are used to establish 12 physical connections to the XIV Gen3 Storage System. Each switch has six FC ports connected. Each FC switch port is connected to each interface module’s FC port #3 or FC port #1. This provides an FC connection to all FC Interface Modules on the XIV Gen3 Storage System. This configuration provides multiple redundant paths to the XIV Gen3 Storage System and guarantees each host has a path to each host interface module. This allows the hosts to evenly distribute I/O workload across all host interface modules to obtain the best possible performance. For each host to achieve optimal performance, each host FC adapter’s max queue depth was set to 128. Each FC port on each interface module concurrently supports up to 1,400 IOPs. There are a total of 4 FC ports on each interface module. Two of the four are available for target FC connections. The remaining two are reserved for remote replication. To calculate the preferred max queue depth for each host, divide total number of hosts defined in your zone by 1,400. Zoning Layout

The FC ports on each host are connected via both Fibre channel switches. To help provide a starting reference for this test environment refer to how XIV Gen3 host interface modules are connected in each SAN A, and B


Solution



Note: Zone XIV_SERENITY contains all XIV Gen3 host interface modules. Zone Name Switch A Zone

Members Switch B – Zone Members

Serenity_XIV_HOST_20 XIV20 HBA 1 Port 0 XIV_Serenity (port 3)

XIV20 HBA 1 Port 1 XIV_Serenity (port 1)












XIV31 HBA 1 Port 1 XIV_Serenity a (port 1)











Table 1) FC zoning configuration


Solution



Important: Before deploying FC switches into production carefully run 24 hour tests and closely monitor the FC activity for errors. If errors are observed, take action by ensuring that zoning parameters are correctly defined. Not following these guidelines may not guarantee reliable operation of your storage environment and could result in data loss. The XIV Gen3 2810 System Storage array can be found in the Windows Server Catalog here: http://www.windowsservercatalog.com/item.aspx?idItem=8b0f7671f7d32391327cf8d211ac6a29&bCatID=1282 The ESRPStorage 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 scaleup Exchange solution. Other factors which affect the server scalability are: 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, and client usage profiles. All these factors are beyond the scope for ESRPStorage. 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 overall solution was designed toward medium to large organizations that require basic highavailability and disasterrecovery features inherent in a Mailbox Resiliency configuration, while minimizing administration complexity. The System x3650 and XIV Gen3 Storage System offer scaleout flexibility to expand the solution as the Exchange requirements increase in number of users, mailbox size, or server failure tolerance. The target environment profile for this solution includes:

24 Exchange 2010 servers (12 tested) 2 backend storage subsystems (1 tested) 2 DAGs 2 copies/database 120,000 mailboxes 0.13 IOPS user profile (0.11 + 20% headroom)

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

http://www.windowsservercatalog.com/item.aspx?idItem=8b0f7671-f7d3-2391-327c-f8d211ac6a29&bCatID=1282

http://www.windowsservercatalog.com/item.aspx?idItem=8b0f7671-f7d3-2391-327c-f8d211ac6a29&bCatID=1282


Solution



1.5GB mailbox quota 8 Databases per Server 1.7TB maximum database size tested Mailbox Resiliency provides high availability and is the primary data protection mechanism. XIV Gen3 RAID provides for data protection against physical loss/failure

24x7 Background Database Maintenance is utilized

Tested Deployment The following tables summarize the testing environment:

Simulated Exchange Configuration: Number of Exchange mailboxes simulated

120,000

Number of Database Availability Groups (DAGs)

2

Number of servers/DAG 12 Number of active mailboxes/server 5000 Number of databases/host 8 Number of copies/database 2 Number of mailboxes/database 625 Simulated profile: I/O’s per second per mailbox (IOPS, include 20% headroom)

0.13 (0.11 with 20% headroom tested)

Database LUN size 2TB Log LUN size 300GB Total database size for performance testing (per XIV Gen3 frame)

188TB

% storage capacity used by Exchange database**

78%

**Storage performance characteristics change based upon the utilization percentage 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. Actual (hard) capacity used will vary due to the way the XIV Gen3 Storage System physically allocates disk space. See the previous section for further information on how XIV Gen3 allocates & tracks physical disk space.


Solution



Storage Hardware Storage Connectivity (Fiber Channel, SAS, SATA, iSCSI)

SAS

Storage model and OS/firmware revision

XIV Gen3 Storage System Model:2810 Machine type 114 XIV Gen3 Storage System Code Version 11.0.0

Storage cache 360GB Number of storage controllers 6 Number of storage ports 24 Maximum bandwidth of storage connectivity to host

96Gbit (12 X 8Gb)

Switch type/model/firmware revision 2 Brocade 48000 (64 Ports) (8Gb) Switch Firmware Version: 6.1.0

HBA model and firmware Storage: Emulex 8GB FC PCI Express Adapter: Model: LPE12002 Fibre Channel Operation Speed: 2, 4 & 8Gbps) HBA Firmware Version: Firmware image's version: U3D200X7r3 (2/3/2011) Host: Qlogic QLE2562 8Gb dualport FC HBA (PCIe)

Number of HBA’s/host 2 Host server type 24 x IBM System x3650 servers each

with two quadcore 3.0 GHz Intel Xeon processors

Total number of disks tested in solution

180

Maximum number of spindles can be hosted in the storage

180


Solution



Storage Software HBA driver Qlogic Storport 9.1.9.25 HBA QueueTarget Setting Default HBA QueueDepth Setting 128 MultiPathing Microsoft Multipath I/O (Native to

Windows Server 2008), round robin mode

Host OS Windows Server 2008 R2 – Enterprise Edition SP1 (6.1.7601.65536)

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

SAS, 7,200 RPM

Raw capacity per disk (GB) 3.0TB Number of physical disks in test 180 Total raw storage capacity (GB) Actual: 480TB Net: 243TB Disk slice size (GB) N/A Number of slices per LUN or number of disks per LUN

180

Raid level RAID X (IBM XIV Gen3 RAID) Total formatted capacity 188TB Storage capacity utilization 78% Database capacity utilization 75%

Storage Disk Configuration (Transactional Log Disks)2 Disk type, speed and firmware revision

SAS, 7,200 RPM

Raw capacity per disk (GB) 3.0TB Number of Spindles in test 180 Total raw storage capacity (GB) Actual: 480TB Net: 243TB Disk slice size (GB) N/A Number of slices per LUN or number of disks per LUN

180

Raid level RAID X (IBM XIV Gen3 RAID)

2 Utilizes same disks as Mailbox Store Databases


Solution



Total formatted capacity 188TB

Best Practices Exchange server is a diskintensive application. Based on the testing run using the ESRP framework, we recommend the following to improve the storage performance. For Exchange 2010 guidance on storage design, please visit: http://technet.microsoft.com/enus/library/dd346703.aspx

Storage - Mailbox Resiliency 1. To accurately size final formatted volume size on the XIV Gen3 Storage System, stage the target volume size prior to implementing. By default, the minimum volume extent size is created in blocks of 17 GB. To get close to target volume size, divide the target size by extent size of 17 GB. For example, if the target volume size is 650 GB, divide 650/17 = 38 Extents (equals to about 646 GB). After partitioning, and formatting volume, the final size will be reduced even more. Factor in another 17 GB, to compensate for the filesystem overhead. 646 GB + 17 GB will provide 663 GB unformatted drive space. Format the newly created volume and check the available or free space to determine if this meets target needs. Otherwise, increase or reduce the volume to get a more accurate target size.

Note: "* 1GB=1000MB, 1MB=1000KB, 1KB=1000 bytes" 663GB translated is actually 663x1000x1000x1000/1024/1024/1024 = 617GB on windows.

2. For optimal performance, format the database volumes using a 64k Windows allocation unit size. The volumes used to store log data can be formatted using default allocation unit size, as there are no significant gains increasing this from the default value.

3. Increasing the Queue Depth setting on the HBA Fibre Controller may increase overall IOPS. Refer to your manufacturer’s HBA documentation for detailed support on how this value can be modified.

4. Increasing the number of FC HBA’s can provide additional IOPS and resiliency options. Make sure to not define more than 24 paths to the storage, as this the current limit at this time.

5. We strongly recommend implementing Mailbox Resiliency. This allows for using a fewer number of larger LUNS for your databases and yields significantly increased storage performance. Designing your Exchange XIV Gen3 storage configuration with fewer and larger LUNs is often preferable, and we have observed performance and capacity increases on the order of 25% when configured in this manner.

http://technet.microsoft.com/en-us/library/dd346703.aspx


Solution



6. Troubleshooting any latency on the XIV Gen3 Storage System can be monitored via standard tools such as Microsoft Performance Monitor or the XIV Gen3 Storage System monitoring tools. These tools can help determine where and when the heaviest disk I/O patterns are occurring, and what the data transfer rates are, which helps identify and isolate potential I/O bottlenecks.

7. Assuming all storage components are functioning, balanced, and configured correctly, most Exchange Server 2010 storage latency issues are caused by an insufficient number of disks for a given I/O load. The number of IOPS hitting a given drive can be measured using the Performance Monitor Logical Disk object, Disk Transfers/sec counter. The average disk latency should be less than 20ms, with the maximum value no higher than 100ms. Disk latency can be measured using the Performance Monitor Logical Disk object, Avg Disk sec/Read. Since the XIV Gen3 Storage System uses all 180 disks for I/O, and is dynamically selftuning, this concern is all but eliminated versus conventional storage systems.

8. During our testing, the storage subsystems were dedicated to the Exchange Server workload. Sharing the storage with other applications may negatively impact Exchange I/O performance.

9. This solution used two database copies, which afford a mailbox resiliency level of one server failure. We generally recommend no more than two copies, given the modular, redundant design of the XIV Gen3 Storage System coupled with RAIDX protection.

10.To obviate the need for a lagged database copy, consider deploying a solution that leverages XIV Gen3’s instantaneous hardwarebased FlashCopy capabilities, such as Tivoli Storage FlashCopy Manager.

11.For performance tips and bestpractice guidelines on the XIV Gen3 Storage System, please visit IBM Techdocs.

12.For detailed technical information on the XIV Gen3 Storage System, please visit IBM Redbooks.

Planning and monitoring your Exchange storage solution based on these guidelines will help ensure optimal client response times, allow room for growth, and avoid potential performance issues.

Backup strategy N/A

Contact for Additional Information For additional information regarding the IBM storage components used in this solution, please visit: https://www912.ibm.com/ssg/tsfeedback.nsf/feedback?OpenForm

https://www-912.ibm.com/ssg/tsfeedback.nsf/feedback?OpenForm

http://www-01.ibm.com/software/tivoli/products/storage-flashcopy-mgr/

http://w3-03.ibm.com/support/techdocs/atsmastr.nsf/WebDocs/?Search&Query=%5bHTMLDocumentName=WM*%5d+AND+%28xiv%29&Start=1&Count=50&SearchOrder=1&SearchMax=10000

http://www.redbooks.ibm.com/cgi-bin/searchsite.cgi?query=XIV


Solution



Test Result Summary This section provides a high level summary of the test data from the ESRP test runs and the links 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 designed to check storage system reliability; these tests run for 24 hours. The goal is to verify that the storage can handle high Exchange I/O load for an extended period of time. Both the log and database files are analyzed for integrity after the stress test to ensure that no database and/or log corruption has occurred. The following list provides an overview: (clicking on the underlined word will display the html report generated after the reliability test runs)

There were no errors reported in the saved eventlog file. 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 the maximum sustainable Exchange type of I/O for 2 hours. The test is designed to show how long it takes for the storage to respond to an I/O under load. The data below is the sum of all of the logical disk I/O’s and average of all the logical disks I/O latency in the 2 hour test duration. Each server is listed separately and the aggregate numbers across all servers are 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.


Solution



Server 1: XIV23 Database I/O Database Disks Transfers/sec 1296.098 Database Disks Reads/sec 800.943 Database Disks Writes/sec 495.154 Average Database Disk Read Latency (ms)

17.754875

Average Database Disk Write Latency (ms)

2.205

Transaction Log I/O Log Disks Writes/sec 461.318 Average Log Disk Write Latency (ms) 0.5435 Server 2: XIV25 Database I/O Database Disks Transfers/sec 1157.052 Database Disks Reads/sec 708.588 Database Disks Writes/sec 448.463 Average Database Disk Read Latency (ms)

15.620625


1.43225


17.700875


2.1865

Transaction Log I/O Log Disks Writes/sec 463.007 Average Log Disk Write Latency (ms) 0.541125


Solution



Server 4: XIV121 Database I/O Database Disks Transfers/sec 1304.274 Database Disks Reads/sec 805.783 Database Disks Writes/sec 498.493 Average Database Disk Read Latency (ms)

17.74675


2.141625


17.6505


2.06125


17.66275


2.104125

Transaction Log I/O Log Disks Writes/sec 467.357 Average Log Disk Write Latency (ms) 0.533375 Server 7: XIV31 Database I/O Database Disks Transfers/sec 1308.36 Database Disks Reads/sec 808.958


Solution



Database Disks Writes/sec 499.402 Average Database Disk Read Latency (ms)

17.698625


2.12775


17.458625


1.846625


17.666875


2.06475


17.66325


2.098625


Solution




17.595125


1.96975

Transaction Log I/O Log Disks Writes/sec 469 Average Log Disk Write Latency (ms) 0.545625 Server 12: XIV24 Database I/O Database Disks Transfers/sec 1323.702 Database Disks Reads/sec 817.797 Database Disks Writes/sec 505.906 Average Database Disk Read Latency (ms)

17.6175


2.082625

Transaction Log I/O Log Disks Writes/sec 471.796 Average Log Disk Write Latency (ms) 0.515875 Aggregate Performance across all servers Metrics: The sum of I/O’s across servers in solution and the average latency across all servers in solution. Database I/O Database Disks Transfers/sec 15599.391 Database Disks Reads/sec 9630.066 Database Disks Writes/sec 5959.325 Average Database Disk Read Latency (ms)

17.486646


2.02673958

Transaction Log I/O Log Disks Writes/sec 5562.495


Solution



Average Log Disk Write Latency (ms) 0.526635

Database Backup/Recovery Performance There are two tests reports in this section. The first one is to measure the sequential read rate of the database files, and the second is to measure the recovery/replay performance (playing transaction logs into the database).

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. MB read/sec per database 66.20625 MB read/sec total per server 529.65

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. Average time to play one Log file (sec) 1.560762

Conclusion This testing validates this Exchange ESRP – Storage submission for the IBM XIV Gen3 Storage System under the stated configuration parameters, and demonstrates that this storage array is an ideal repository for Exchange Server 2010 data. The new availability of 3TB SAS drives within the XIV Gen3 platform aligns well with Microsoft’s desire for larger mailbox capacities. These drives also allow for a smaller environmental footprint, increasing the storage density envelope without create sprawl. The larger storage capacities tested here also highlight the scalable performance of XIV Gen3’s modular design & controller architecture. Testing also confirmed the enormous benefits of the new cache size support of 240GB The incredible ease of management, advanced data distribution technology, selftuning capability, and automatic (and extremely quick) drive rebuild capability offer Exchange administrators and storage architects new tools to deliver a robust, yet easily managed Exchange storage solution. Advanced features such as copy services, thin provisioning, full MPIO & VSS support offer additional flexibility and support in terms of performance, availability, quick backup/recovery, and ensure optimal, efficient usage of the storage subsystem with minimal fuss.


Solution



This document was developed by storage solution providers, and reviewed by the Microsoft Exchange Product team. The test results/data presented in this document are based on the tests introduced in the ESRP test framework. Customers should not quote the data directly for his/her predeployment verification. It is still necessary to go through the requisite exercises to validate the storage design for a specific customer environment. ESRP program is not designed to be a benchmarking program; tests are not designed to obtain the maximum throughput for a giving solution. Rather, it is focused on producing recommendations from vendors for the Exchange application. So the data presented in this document should not be used for direct comparisons among the differing vendor solutions.

Appendix A. Test Results This section contains Jetstress reports for Stress, Performance, Streaming Backup, and Soft Recovery. All server test results were reviewed by Microsoft, and had similar performance results. We include the results from only one of the servers here, to make this section more readable.

Stress Testing Server 1: XIV24 Stress Test Result Report Test Summary Overall Test Result Pass Machine Name XIV24 Test Description Test Start Time 8/27/2011 6:57:47 PM Test End Time 8/28/2011 7:01:05 PM Collection Start Time 8/27/2011 7:01:02 PM Collection End Time 8/28/2011 7:00:57 PM Jetstress Version 14.01.0225.017 Ese Version 14.00.0639.019 Operating System Windows Server 2008 R2 Enterprise Service Pack 1

(6.1.7601.65536) Performance Log C:\Program Files\Exchange

Jetstress\Gen3ESRP3TB\Performance_2011_8_27_18_58_5.blg Database Sizing and Throughput Achieved Transactional I/O per Second 1308.736 Target Transactional I/O per Second 1000 Initial Database Size (bytes) 7868707766272


Solution



Final Database Size (bytes) 7916816433152 Database Files (Count) 8 Jetstress System Parameters Thread Count 7 (per database) Minimum Database Cache 256.0 MB Maximum Database Cache 2048.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 Instance1208.1 Log Path: L:\1

Database: F:\1\Jetstress001001.edb

Instance1208.2 Log Path: L:\2 Database: F:\2\Jetstress002001.edb

Instance1208.3 Log Path: L:\3 Database: G:\1\Jetstress003001.edb


Instance1208.5 Log Path: L:\5 Database: H:\1\Jetstress005001.edb


Instance1208.7 Log Path: L:\7 Database: I:\1\Jetstress007001.edb


Transactional I/O Performance MSExcha I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O


Solution



nge Database ==> Instances

Database Reads Average Latency (msec)

Database Writes Average Latency (msec)

Database Reads/sec

Database Writes/sec

Database Reads Average Bytes

Database Writes Average Bytes

Log Reads Average Latency (msec)

Log Writes Average Latency (msec)

Log Reads/sec

Log Writes/sec

Log Reads Average Bytes

Log Writes Average Bytes

Instance1208.1

17.922 2.557

99.971 63.71

4 33876.015

35616.62 0 0.51 0

54.878 0

4598.335

Instance1208.2

18.005 2.558

99.954 63.72

5 33830.059

35628.27 0 0.51 0

55.027 0

4600.956

Instance1208.3

18.028 2.238

99.525 63.39

3 33847.292

35615.8 0 0.51 0

54.776 0

4606.01

Instance1208.4

18.022 2.238

99.971 63.72

1 33826.793

35627.13 0 0.51 0

55.032 0

4601.905

Instance1208.5

18.069 1.835

100.051

63.809 33823.398

35615.44 0 0.51 0 55.08 0

4595.61

Instance1208.6

18.028 1.835 99.84

63.638 33833.656

35613.88 0 0.51 0

54.872 0

4597.904

Instance1208.7

18.044 1.67

99.951 63.71

4 33844.596

35626.63 0

0.511 0

54.999 0

4592.4

Instance1208.8 18.02 1.675

100.017

63.741 33859.572

35622.17 0

0.511 0

55.009 0

4601.569

Background Database Maintenance I/O Performance MSExchange Database ==> Instances

Database Maintenance IO Reads/sec

Database Maintenance IO Reads Average Bytes

Instance1208.1 31.399 261723.73 Instance1208.2 31.418 261733.75 Instance1208.3 31.401 261733.377 Instance1208.4 31.406 261743.944 Instance1208.5 31.41 261737.446 Instance1208.6 31.403 261744.104 Instance1208.7 31.404 261727.131 Instance1208.8 31.404 261729.266 Log Replication I/O Performance MSExchange Database ==> Instances I/O Log Reads/sec I/O Log Reads Average Bytes Instance1208.1 1.022 232393.35 Instance1208.2 1.026 232489.395 Instance1208.3 1.022 232522.197


Solution



Instance1208.4 1.026 232438.479 Instance1208.5 1.025 232496.338 Instance1208.6 1.022 232355.443 Instance1208.7 1.024 232365.829 Instance1208.8 1.026 232344.251 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

Instance1208.1

17.922 2.557

131.371

63.714 88334.824

35616.62

11.715 0.51 1.022

54.878 232393.4

4598.335

Instance1208.2

18.005 2.558

131.372

63.725 88334.432

35628.27

11.919 0.51 1.026

55.027 232489.4

4600.956

Instance1208.3

18.028 2.238

130.926

63.393 88503.126

35615.8

11.69 0.51 1.022

54.776 232522.2

4606.01

Instance1208.4

18.022 2.238

131.377

63.721 88311.122

35627.13

12.027 0.51 1.026

55.032 232438.5

4601.905

Instance1208.5

18.069 1.835

131.461

63.809 88278.137

35615.44

12.174 0.51 1.025 55.08

232496.3

4595.61

Instance1208.6

18.028 1.835

131.243

63.638 88365.979

35613.88

11.958 0.51 1.022

54.872 232355.4

4597.904

Instance1208.7

18.044 1.67

131.355

63.714 88326.263

35626.63

12.086 0.511 1.024

54.999 232365.8

4592.4

Instance1208.8 18.02 1.675

131.421

63.741 88310.854

35622.17

11.809 0.511 1.026

55.009 232344.3

4601.569

Host System Performance Counter Average Minimum Maximum % Processor Time 10.786 6.542 13.071 Available MBytes 20617.206 20595 20707 Free System Page Table Entries 33555320.8 33555309 33555826 Transition Pages RePurposed/sec 0.000 0.000 0.000 Pool Nonpaged Bytes 56594561.6 56279040 56836096 Pool Paged Bytes 100133109 97992704 110641152


Solution



Database Page Fault Stalls/sec 0.000 0.000 0.000 Test Log 8/27/2011 6:57:47 PM Jetstress testing begins ... 8/27/2011 6:57:47 PM Preparing for testing ... 8/27/2011 6:57:56 PM Attaching databases ... 8/27/2011 6:57:56 PM Preparations for testing are complete. 8/27/2011 6:57:56 PM Starting transaction dispatch .. 8/27/2011 6:57:56 PM Database cache settings: (minimum: 256.0 MB, maximum: 2.0 GB) 8/27/2011 6:57:56 PM Database flush thresholds: (start: 20.5 MB, stop: 40.9 MB) 8/27/2011 6:58:05 PM Database read latency thresholds: (average: 20 msec/read, maximum: 100 msec/read). 8/27/2011 6:58:05 PM Log write latency thresholds: (average: 10 msec/write, maximum: 100 msec/write). 8/27/2011 6:58:14 PM Operation mix: Sessions 7, Inserts 40%, Deletes 20%, Replaces 5%, Reads 35%, Lazy Commits 70%. 8/27/2011 6:58:14 PM Performance logging started (interval: 15000 ms). 8/27/2011 6:58:14 PM Attaining prerequisites: 8/27/2011 7:01:02 PM \MSExchange Database(JetstressWin)\Database Cache Size, Last: 1944084000.0 (lower bound: 1932735000.0, upper bound: none) 8/28/2011 7:01:03 PM Performance logging has ended. 8/28/2011 7:01:03 PM JetInterop batch transaction stats: 424066, 424858, 423094, 425001, 425237, 423053, 424278 and 424054. 8/28/2011 7:01:04 PM Dispatching transactions ends. 8/28/2011 7:01:04 PM Shutting down databases ... 8/28/2011 7:01:05 PM Instance1208.1 (complete), Instance1208.2 (complete), Instance1208.3 (complete), Instance1208.4 (complete), Instance1208.5 (complete), Instance1208.6 (complete), Instance1208.7 (complete) and Instance1208.8 (complete) 8/28/2011 7:01:05 PM C:\Program Files\Exchange Jetstress\Gen3ESRP3TB\Performance_2011_8_27_18_58_5.blg has 5762 samples. 8/28/2011 7:01:05 PM Creating test report ... 8/28/2011 7:01:45 PM Instance1208.1 has 17.9 for I/O Database Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.1 has 0.5 for I/O Log Writes Average Latency. 8/28/2011 7:01:45 PM Instance1208.1 has 0.5 for I/O Log Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.2 has 18.0 for I/O Database Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.2 has 0.5 for I/O Log Writes Average Latency. 8/28/2011 7:01:45 PM Instance1208.2 has 0.5 for I/O Log Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.3 has 18.0 for I/O Database Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.3 has 0.5 for I/O Log Writes Average Latency. 8/28/2011 7:01:45 PM Instance1208.3 has 0.5 for I/O Log Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.4 has 18.0 for I/O Database Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.4 has 0.5 for I/O Log Writes Average Latency. 8/28/2011 7:01:45 PM Instance1208.4 has 0.5 for I/O Log Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.5 has 18.1 for I/O Database Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.5 has 0.5 for I/O Log Writes Average Latency. 8/28/2011 7:01:45 PM Instance1208.5 has 0.5 for I/O Log Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.6 has 18.0 for I/O Database Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.6 has 0.5 for I/O Log Writes Average Latency. 8/28/2011 7:01:45 PM Instance1208.6 has 0.5 for I/O Log Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.7 has 18.0 for I/O Database Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.7 has 0.5 for I/O Log Writes Average Latency. 8/28/2011 7:01:45 PM Instance1208.7 has 0.5 for I/O Log Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.8 has 18.0 for I/O Database Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.8 has 0.5 for I/O Log Writes Average Latency.


Solution



8/28/2011 7:01:45 PM Instance1208.8 has 0.5 for I/O Log Reads Average Latency. 8/28/2011 7:01:45 PM Test has 0 Maximum Database Page Fault Stalls/sec. 8/28/2011 7:01:45 PM The test has 0 Database Page Fault Stalls/sec samples higher than 0. 8/28/2011 7:01:45 PM C:\Program Files\Exchange Jetstress\Gen3ESRP3TB\Performance_2011_8_27_18_58_5.xml has 5750 samples queried.

Performance Testing Server 1: XIV24 Performance Test Result Report Test Summary Overall Test Result Pass Machine Name XIV24 Test Description Test Start Time 8/27/2011 9:12:11 AM Test End Time 8/27/2011 11:16:05 AM Collection Start Time 8/27/2011 9:16:02 AM Collection End Time 8/27/2011 11:15:49 AM Jetstress Version 14.01.0225.017 Ese Version 14.00.0639.019 Operating System Windows Server 2008 R2 Enterprise Service Pack 1

(6.1.7601.65536) Performance Log C:\Program Files\Exchange

Jetstress\Gen3ESRP3TB\Performance_2011_8_27_9_12_29.blg Database Sizing and Throughput Achieved Transactional I/O per Second 1323.702 Target Transactional I/O per Second 1000 Initial Database Size (bytes) 7864370855936 Final Database Size (bytes) 7868707766272 Database Files (Count) 8 Jetstress System Parameters Thread Count 7 (per database) Minimum Database Cache 256.0 MB Maximum Database Cache 2048.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


Solution



Database Configuration Instance1208.1 Log Path: L:\1









Transactional I/O Performance MSExchange Database ==> Instances









I/O Log Reads/sec

I/O Log Writes/sec



Instance1208.1

17.545 2.594

102.265

63.257 33753.996

37057.21 0

0.513 0

58.752 0

4631.439

Instance1208.2

17.607 2.579

102.707

63.525 33843.157

37056.74 0

0.517 0

59.331 0

4627.456

Instance1208.3

17.629 2.248

102.599

63.499 33814.582

37102.18 0

0.516 0

59.151 0

4653.879

Instance1 17.63 2.26 102.6 63.54 33921 3708 0 0.51 0 58.98 0 4666.


Solution



208.4 3 88 7 .032 7.97 3 8 31 Instance1208.5

17.647 1.841

101.498

62.775 33660.839

37104.27 0

0.515 0

58.728 0

4641.792

Instance1208.6

17.615 1.84

102.201

63.281 33733.502

37080.99 0

0.521 0

58.968 0

4665.228

Instance1208.7

17.605 1.644

101.537

62.677 33678.447

37134.17 0

0.515 0

58.601 0

4670.542

Instance1208.8

17.659 1.655

102.302

63.345 33810.663

37098.48 0

0.517 0

59.277 0

4631.522




Instance1208.1 31.381 261736.66 Instance1208.2 31.407 261686.903 Instance1208.3 31.399 261696.664 Instance1208.4 31.376 261697.16 Instance1208.5 31.416 261677.487 Instance1208.6 31.417 261723.016 Instance1208.7 31.402 261730.26 Instance1208.8 31.389 261688.068 Log Replication I/O Performance MSExchange Database ==> Instances I/O Log Reads/sec I/O Log Reads Average Bytes Instance1208.1 1.103 232533.141 Instance1208.2 1.114 232545.55 Instance1208.3 1.117 232491.144 Instance1208.4 1.117 232551.459 Instance1208.5 1.105 232512.64 Instance1208.6 1.117 232515.6 Instance1208.7 1.113 232541.117 Instance1208.8 1.114 232523.155 Total I/O Performance MSExchange Database ==> Instances

I/O Database Reads Average Latency

I/O Database Writes Average Latency





I/O Log Reads Average Latency (mse

I/O Log Writes Average Latency (mse

I/O Log Reads/sec

I/O Log Writes/sec




Solution



(msec)

(msec)

c) c)

Instance1208.1

17.545 2.594

133.646

63.257 87286.47

37057.21

10.984 0.513 1.103

58.752 232533.1

4631.439

Instance1208.2

17.607 2.579

134.114

63.525 87199.862

37056.74

12.044 0.517 1.114

59.331 232545.6

4627.456

Instance1208.3

17.629 2.248

133.998

63.499 87212.836

37102.18

10.946 0.516 1.117

59.151 232491.1

4653.879

Instance1208.4

17.633 2.26

134.064

63.547 87228.402

37087.97

11.472 0.513 1.117

58.988 232551.5

4666.31

Instance1208.5

17.647 1.841

132.914

62.775 87555.758

37104.27

11.425 0.515 1.105

58.728 232512.6

4641.792

Instance1208.6

17.615 1.84

133.618

63.281 87340.01

37080.99

11.109 0.521 1.117

58.968 232515.6

4665.228

Instance1208.7

17.605 1.644

132.938

62.677 87547.335

37134.17

11.575 0.515 1.113

58.601 232541.1

4670.542

Instance1208.8

17.659 1.655

133.691

63.345 87313.405

37098.48

10.689 0.517 1.114

59.277 232523.2

4631.522

Host System Performance Counter Average Minimum Maximum % Processor Time 10.747 9.177 12.435 Available MBytes 20657.395 20640 20813 Free System Page Table Entries 33555313.9 33555291 33555314 Transition Pages RePurposed/sec 0.000 0.000 0.000 Pool Nonpaged Bytes 55656063.2 55070720 55865344 Pool Paged Bytes 95681080.7 95617024 95838208 Database Page Fault Stalls/sec 0.000 0.000 0.000 Test Log 8/27/2011 12:41:38 AM Preparing for testing ... 8/27/2011 12:41:38 AM Creating F:\1\Jetstress001001.edb. 8/27/2011 12:41:38 AM Database cache settings: (minimum: 32.0 MB, maximum: 256.0 MB) 8/27/2011 12:41:38 AM Database flush thresholds: (start: 2.5 MB, stop: 5.1 MB) 8/27/2011 3:20:52 AM 100.0% of 915.5 GB complete (312887610 records inserted). 8/27/2011 3:20:52 AM 100.0% of 915.5 GB complete (312887685 records inserted). 8/27/2011 3:20:53 AM Duplicating 7 databases: 8/27/2011 8:35:52 AM 100.0% of 6.3 TB complete (6.3 TB duplicated). 8/27/2011 8:36:00 AM Attaching databases ... 8/27/2011 8:36:00 AM Preparations for testing are complete. 8/27/2011 9:12:11 AM Jetstress testing begins ... 8/27/2011 9:12:11 AM Preparing for testing ... 8/27/2011 9:12:20 AM Attaching databases ... 8/27/2011 9:12:20 AM Preparations for testing are complete. 8/27/2011 9:12:20 AM Starting transaction dispatch .. 8/27/2011 9:12:20 AM Database cache settings: (minimum: 256.0 MB, maximum: 2.0 GB) 8/27/2011 9:12:20 AM Database flush thresholds: (start: 20.5 MB, stop: 40.9 MB)


Solution



8/27/2011 9:12:29 AM Database read latency thresholds: (average: 20 msec/read, maximum: 100 msec/read). 8/27/2011 9:12:29 AM Log write latency thresholds: (average: 10 msec/write, maximum: 100 msec/write). 8/27/2011 9:12:38 AM Operation mix: Sessions 7, Inserts 40%, Deletes 20%, Replaces 5%, Reads 35%, Lazy Commits 70%. 8/27/2011 9:12:38 AM Performance logging started (interval: 15000 ms). 8/27/2011 9:12:38 AM Attaining prerequisites: 8/27/2011 9:16:02 AM \MSExchange Database(JetstressWin)\Database Cache Size, Last: 1936450000.0 (lower bound: 1932735000.0, upper bound: none) 8/27/2011 11:16:03 AM Performance logging has ended. 8/27/2011 11:16:03 AM JetInterop batch transaction stats: 38718, 38939, 38912, 38954, 39021, 39158, 38703 and 38941. 8/27/2011 11:16:03 AM Dispatching transactions ends. 8/27/2011 11:16:03 AM Shutting down databases ... 8/27/2011 11:16:05 AM Instance1208.1 (complete), Instance1208.2 (complete), Instance1208.3 (complete), Instance1208.4 (complete), Instance1208.5 (complete), Instance1208.6 (complete), Instance1208.7 (complete) and Instance1208.8 (complete) 8/27/2011 11:16:05 AM C:\Program Files\Exchange Jetstress\Gen3ESRP3TB\Performance_2011_8_27_9_12_29.blg has 492 samples. 8/27/2011 11:16:05 AM Creating test report ... 8/27/2011 11:16:09 AM Instance1208.1 has 17.5 for I/O Database Reads Average Latency. 8/27/2011 11:16:09 AM Instance1208.1 has 0.5 for I/O Log Writes Average Latency. 8/27/2011 11:16:09 AM Instance1208.1 has 0.5 for I/O Log Reads Average Latency. 8/27/2011 11:16:09 AM Instance1208.2 has 17.6 for I/O Database Reads Average Latency. 8/27/2011 11:16:09 AM Instance1208.2 has 0.5 for I/O Log Writes Average Latency. 8/27/2011 11:16:09 AM Instance1208.2 has 0.5 for I/O Log Reads Average Latency. 8/27/2011 11:16:09 AM Instance1208.3 has 17.6 for I/O Database Reads Average Latency. 8/27/2011 11:16:09 AM Instance1208.3 has 0.5 for I/O Log Writes Average Latency. 8/27/2011 11:16:09 AM Instance1208.3 has 0.5 for I/O Log Reads Average Latency. 8/27/2011 11:16:09 AM Instance1208.4 has 17.6 for I/O Database Reads Average Latency. 8/27/2011 11:16:09 AM Instance1208.4 has 0.5 for I/O Log Writes Average Latency. 8/27/2011 11:16:09 AM Instance1208.4 has 0.5 for I/O Log Reads Average Latency. 8/27/2011 11:16:09 AM Instance1208.5 has 17.6 for I/O Database Reads Average Latency. 8/27/2011 11:16:09 AM Instance1208.5 has 0.5 for I/O Log Writes Average Latency. 8/27/2011 11:16:09 AM Instance1208.5 has 0.5 for I/O Log Reads Average Latency. 8/27/2011 11:16:09 AM Instance1208.6 has 17.6 for I/O Database Reads Average Latency. 8/27/2011 11:16:09 AM Instance1208.6 has 0.5 for I/O Log Writes Average Latency. 8/27/2011 11:16:09 AM Instance1208.6 has 0.5 for I/O Log Reads Average Latency. 8/27/2011 11:16:09 AM Instance1208.7 has 17.6 for I/O Database Reads Average Latency. 8/27/2011 11:16:09 AM Instance1208.7 has 0.5 for I/O Log Writes Average Latency. 8/27/2011 11:16:09 AM Instance1208.7 has 0.5 for I/O Log Reads Average Latency. 8/27/2011 11:16:09 AM Instance1208.8 has 17.7 for I/O Database Reads Average Latency. 8/27/2011 11:16:09 AM Instance1208.8 has 0.5 for I/O Log Writes Average Latency. 8/27/2011 11:16:09 AM Instance1208.8 has 0.5 for I/O Log Reads Average Latency. 8/27/2011 11:16:09 AM Test has 0 Maximum Database Page Fault Stalls/sec. 8/27/2011 11:16:09 AM The test has 0 Database Page Fault Stalls/sec samples higher than 0. 8/27/2011 11:16:09 AM C:\Program Files\Exchange Jetstress\Gen3ESRP3TB\Performance_2011_8_27_9_12_29.xml has 478 samples queried.


Solution



Streaming Backup Testing Server 1: XIV24 Microsoft Exchange Server Jetstress Database backup Test Result Report Database Backup Statistics All Database Instance Database Size (MBytes) Elapsed Backup Time MBytes Transferred/sec Instance1208.1 943730.09 3:57:36 66.19 Instance1208.2 943746.09 3:58:37 65.91 Instance1208.3 943738.09 3:57:13 66.3 Instance1208.4 943770.09 3:57:13 66.31 Instance1208.5 943754.09 3:57:05 66.34 Instance1208.6 943754.09 3:57:05 66.34 Instance1208.7 943730.09 3:57:36 66.19 Instance1208.8 943746.09 3:58:37 65.91 Jetstress System Parameters Thread Count 7 (per database) Minimum Database Cache 256.0 MB Maximum Database Cache 2048.0 MB Insert Operations 40% Delete Operations 20% Replace Operations 5% Read Operations 35% Lazy Commits 70% Database Configuration Instance1208.1 Log Path: L:\1





Instance1208.5 Log Path: L:\5


Solution



Database: H:\1\Jetstress005001.edb













I/O Log Reads/sec

I/O Log Writes/sec



Instance1208.1 5.493 0 265.017 0 262144 0 0 0 0 0 0 0 Instance1208.2 5.429 0 263.323 0 262144 0 0 0 0 0 0 0 Instance1208.3 6.557 0 265.263 0 262144 0 0 0 0 0 0 0 Instance1208.4 5.393 0 265.256 0 262144 0 0 0 0 0 0 0 Instance1208.5 6.546 0 265.415 0 262144 0 0 0 0 0 0 0 Instance1208.6 5.39 0 265.455 0 262144 0 0 0 0 0 0 0 Instance1208.7 6.543 0 265.647 0 262144 0 0 0 0 0 0 0 Instance1208.8 5.385 0 265.626 0 262144 0 0 0 0 0 0 0 Host System Performance Counter Average Minimum Maximum % Processor Time 13.534 11.519 14.565 Available MBytes 22747.04 22737 22759 Free System Page Table Entries 33555344.1 33555313 33555826


Solution



Transition Pages RePurposed/sec 0.000 0.000 0.000 Pool Nonpaged Bytes 56589759.5 56524800 56725504 Pool Paged Bytes 104954708 104947712 104996864 Database Page Fault Stalls/sec 0.000 0.000 0.000 Test Log 8/27/2011 6:57:47 PM Jetstress testing begins ... 8/27/2011 6:57:47 PM Preparing for testing ... 8/27/2011 6:57:56 PM Attaching databases ... 8/27/2011 6:57:56 PM Preparations for testing are complete. 8/27/2011 6:57:56 PM Starting transaction dispatch .. 8/27/2011 6:57:56 PM Database cache settings: (minimum: 256.0 MB, maximum: 2.0 GB) 8/27/2011 6:57:56 PM Database flush thresholds: (start: 20.5 MB, stop: 40.9 MB) 8/27/2011 6:58:05 PM Database read latency thresholds: (average: 20 msec/read, maximum: 100 msec/read). 8/27/2011 6:58:05 PM Log write latency thresholds: (average: 10 msec/write, maximum: 100 msec/write). 8/27/2011 6:58:14 PM Operation mix: Sessions 7, Inserts 40%, Deletes 20%, Replaces 5%, Reads 35%, Lazy Commits 70%. 8/27/2011 6:58:14 PM Performance logging started (interval: 15000 ms). 8/27/2011 6:58:14 PM Attaining prerequisites: 8/27/2011 7:01:02 PM \MSExchange Database(JetstressWin)\Database Cache Size, Last: 1944084000.0 (lower bound: 1932735000.0, upper bound: none) 8/28/2011 7:01:03 PM Performance logging has ended. 8/28/2011 7:01:03 PM JetInterop batch transaction stats: 424066, 424858, 423094, 425001, 425237, 423053, 424278 and 424054. 8/28/2011 7:01:04 PM Dispatching transactions ends. 8/28/2011 7:01:04 PM Shutting down databases ... 8/28/2011 7:01:05 PM Instance1208.1 (complete), Instance1208.2 (complete), Instance1208.3 (complete), Instance1208.4 (complete), Instance1208.5 (complete), Instance1208.6 (complete), Instance1208.7 (complete) and Instance1208.8 (complete) 8/28/2011 7:01:05 PM C:\Program Files\Exchange Jetstress\Gen3ESRP3TB\Performance_2011_8_27_18_58_5.blg has 5762 samples. 8/28/2011 7:01:05 PM Creating test report ... 8/28/2011 7:01:45 PM Instance1208.1 has 17.9 for I/O Database Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.1 has 0.5 for I/O Log Writes Average Latency. 8/28/2011 7:01:45 PM Instance1208.1 has 0.5 for I/O Log Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.2 has 18.0 for I/O Database Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.2 has 0.5 for I/O Log Writes Average Latency. 8/28/2011 7:01:45 PM Instance1208.2 has 0.5 for I/O Log Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.3 has 18.0 for I/O Database Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.3 has 0.5 for I/O Log Writes Average Latency. 8/28/2011 7:01:45 PM Instance1208.3 has 0.5 for I/O Log Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.4 has 18.0 for I/O Database Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.4 has 0.5 for I/O Log Writes Average Latency. 8/28/2011 7:01:45 PM Instance1208.4 has 0.5 for I/O Log Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.5 has 18.1 for I/O Database Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.5 has 0.5 for I/O Log Writes Average Latency. 8/28/2011 7:01:45 PM Instance1208.5 has 0.5 for I/O Log Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.6 has 18.0 for I/O Database Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.6 has 0.5 for I/O Log Writes Average Latency. 8/28/2011 7:01:45 PM Instance1208.6 has 0.5 for I/O Log Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.7 has 18.0 for I/O Database Reads Average Latency.


Solution



8/28/2011 7:01:45 PM Instance1208.7 has 0.5 for I/O Log Writes Average Latency. 8/28/2011 7:01:45 PM Instance1208.7 has 0.5 for I/O Log Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.8 has 18.0 for I/O Database Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.8 has 0.5 for I/O Log Writes Average Latency. 8/28/2011 7:01:45 PM Instance1208.8 has 0.5 for I/O Log Reads Average Latency. 8/28/2011 7:01:45 PM Test has 0 Maximum Database Page Fault Stalls/sec. 8/28/2011 7:01:45 PM The test has 0 Database Page Fault Stalls/sec samples higher than 0. 8/28/2011 7:01:45 PM C:\Program Files\Exchange Jetstress\Gen3ESRP3TB\Performance_2011_8_27_18_58_5.xml has 5750 samples queried. 8/28/2011 7:01:45 PM C:\Program Files\Exchange Jetstress\Gen3ESRP3TB\Performance_2011_8_27_18_58_5.html was saved. 8/28/2011 7:01:46 PM Performance logging started (interval: 30000 ms). 8/28/2011 7:01:46 PM Verifying database checksums ... 8/28/2011 11:39:08 PM F: (100% processed), G: (100% processed), H: (100% processed) and I: (100% processed) 8/28/2011 11:39:08 PM Performance logging has ended. 8/28/2011 11:39:08 PM C:\Program Files\Exchange Jetstress\Gen3ESRP3TB\DBChecksum_2011_8_28_19_1_45.blg has 554 samples. 8/28/2011 11:39:11 PM C:\Program Files\Exchange Jetstress\Gen3ESRP3TB\DBChecksum_2011_8_28_19_1_45.html was saved. 8/28/2011 11:39:11 PM Verifying log checksums ... 8/28/2011 11:39:19 PM L:\1 (13 logs processed), L:\2 (13 logs processed), L:\3 (12 logs processed), L:\4 (14 logs processed), L:\5 (14 logs processed), L:\6 (13 logs processed), L:\7 (13 logs processed) and L:\8 (13 logs processed) 8/28/2011 11:39:19 PM C:\Program Files\Exchange Jetstress\Gen3ESRP3TB\Application_2011_8_28_23_39_19.evt is saved. 8/28/2011 11:39:19 PM C:\Program Files\Exchange Jetstress\Gen3ESRP3TB\System_2011_8_28_23_39_19.evt is saved. 8/28/2011 11:39:19 PM C:\Program Files\Exchange Jetstress\Gen3ESRP3TB\XmlConfig_2011_8_28_23_39_19.xml was saved. 8/28/2011 11:39:19 PM Jetstress testing has ended. 8/29/2011 2:54:06 PM Jetstress testing begins ... 8/29/2011 2:54:06 PM Preparing for testing ... 8/29/2011 2:54:15 PM Attaching databases ... 8/29/2011 2:54:15 PM Preparations for testing are complete. 8/29/2011 2:54:27 PM Performance logging started (interval: 30000 ms). 8/29/2011 2:54:27 PM Backing up databases ... 8/29/2011 6:53:05 PM Performance logging has ended. 8/29/2011 6:53:05 PM Instance1208.1 (100% processed), Instance1208.2 (100% processed), Instance1208.3 (100% processed), Instance1208.4 (100% processed), Instance1208.5 (100% processed), Instance1208.6 (100% processed), Instance1208.7 (100% processed) and Instance1208.8 (100% processed) 8/29/2011 6:53:05 PM C:\Program Files\Exchange Jetstress\Gen3ESRP3TB\DatabaseBackup_2011_8_29_14_54_15.blg has 476 samples. 8/29/2011 6:53:05 PM Creating test report ...

Soft Recovery Testing Server 1: XIV24 Microsoft Exchange Server Jetstress SoftRecovery Test Result Report SoftRecovery Statistics All Database Instance Log files replayed Elapsed seconds


Solution



Instance1208.1 501 746.539311 Instance1208.2 501 748.660915 Instance1208.3 506 748.395715 Instance1208.4 503 747.069712 Instance1208.5 503 747.334913 Instance1208.6 506 748.130514 Instance1208.1 501 746.539311 Instance1208.2 501 748.660915 Database Configuration Instance1208.1 Log Path: L:\1










I/O Database Reads Average Latency

I/O Database Writes Average Latency





I/O Log Reads Average Latency (mse

I/O Log Writes Average Latency (mse

I/O Log Reads/sec

I/O Log Writes/sec




Solution



(msec)

(msec)

c) c)

Instance1208.1

34.548 0.771

961.716 4.051

37067.962

32233.74

20.622

0.004 6.077 0.004

228707.1

2.783

Instance1208.2

35.997 0.896

934.529 4.033

37154.178

32236.63

21.557

0.002 6.056 0.016

228679.2

2.768

Instance1208.3

35.779 1.226

928.205 4.075

37102.009

32233.74

19.81 0 6.113 0

228693.1 0

Instance1208.4

36.362 1.354

931.461 4.051

37677.436

32055.65

16.318 0 6.077 0

227392.7 0

Instance1208.5 36.16 0.864

913.386 4.059

36731.575

32411.83

22.966 0 6.089 0

229907.2 0

Instance1208.6

34.919 0.723

946.696 4.067

37128.514

32233.74

24.087 0 6.101 0

228669.5 0

Instance1208.7 35 0.822

960.809 4.11

36997.1 32233.74

18.309 0 6.166 0

228731.6 0

Instance1208.8

36.324 1.162

914.242 4.013

37814.937

32059.5

23.731 0 6.019 0

227471.1 0




Instance1208.1 30.635 261761.697 Instance1208.2 30.971 261796.314 Instance1208.3 30.543 261771.757 Instance1208.4 30.599 261777.047 Instance1208.5 30.857 261806.407 Instance1208.6 30.466 261818.993 Instance1208.7 30.809 261845.724 Instance1208.8 30.654 261811.524 Total I/O Performance MSExchange Database ==> Instances









I/O Log Reads/sec

I/O Log Writes/sec



Instance1 34.54 0.771 992.3 4.051 44004 3223 20.6 0.00 6.077 0.004 2287 2.78


Solution



208.1 8 51 .57 3.74 22 4 07.1 3 Instance1208.2

35.997 0.896 965.5 4.033

44360.093

32236.63

21.557

0.002 6.056 0.016

228679.2

2.768

Instance1208.3

35.779 1.226

958.748 4.075

44259.46

32233.74

19.81 0 6.113 0

228693.1 0

Instance1208.4

36.362 1.354

962.06 4.051

44805.04

32055.65

16.318 0 6.077 0

227392.7 0

Instance1208.5 36.16 0.864

944.243 4.059

44086.754

32411.83

22.966 0 6.089 0

229907.2 0

Instance1208.6

34.919 0.723

977.163 4.067

44134.029

32233.74

24.087 0 6.101 0

228669.5 0

Instance1208.7 35 0.822

991.619 4.11

43983.121

32233.74

18.309 0 6.166 0

228731.6 0

Instance1208.8

36.324 1.162

944.896 4.013

45081.688

32059.5

23.731 0 6.019 0

227471.1 0

Host System Performance Counter Average Minimum Maximum % Processor Time 15.808 6.54 28.682 Available MBytes 20645.602 20569 22477 Free System Page Table Entries 33555316.7 33555313 33555826 Transition Pages RePurposed/sec 0.000 0.000 0.000 Pool Nonpaged Bytes 64412198.5 57589760 65224704 Pool Paged Bytes 106046827 106029056 106106880 Database Page Fault Stalls/sec 0.000 0.000 0.000 Test Log 8/27/2011 6:57:47 PM Jetstress testing begins ... 8/27/2011 6:57:47 PM Preparing for testing ... 8/27/2011 6:57:56 PM Attaching databases ... 8/27/2011 6:57:56 PM Preparations for testing are complete. 8/27/2011 6:57:56 PM Starting transaction dispatch .. 8/27/2011 6:57:56 PM Database cache settings: (minimum: 256.0 MB, maximum: 2.0 GB) 8/27/2011 6:57:56 PM Database flush thresholds: (start: 20.5 MB, stop: 40.9 MB) 8/27/2011 6:58:05 PM Database read latency thresholds: (average: 20 msec/read, maximum: 100 msec/read). 8/27/2011 6:58:05 PM Log write latency thresholds: (average: 10 msec/write, maximum: 100 msec/write). 8/27/2011 6:58:14 PM Operation mix: Sessions 7, Inserts 40%, Deletes 20%, Replaces 5%, Reads 35%, Lazy Commits 70%. 8/27/2011 6:58:14 PM Performance logging started (interval: 15000 ms). 8/27/2011 6:58:14 PM Attaining prerequisites: 8/27/2011 7:01:02 PM \MSExchange Database(JetstressWin)\Database Cache Size, Last: 1944084000.0 (lower bound: 1932735000.0, upper bound: none) 8/28/2011 7:01:03 PM Performance logging has ended. 8/28/2011 7:01:03 PM JetInterop batch transaction stats: 424066, 424858, 423094, 425001,


Solution



425237, 423053, 424278 and 424054. 8/28/2011 7:01:04 PM Dispatching transactions ends. 8/28/2011 7:01:04 PM Shutting down databases ... 8/28/2011 7:01:05 PM Instance1208.1 (complete), Instance1208.2 (complete), Instance1208.3 (complete), Instance1208.4 (complete), Instance1208.5 (complete), Instance1208.6 (complete), Instance1208.7 (complete) and Instance1208.8 (complete) 8/28/2011 7:01:05 PM C:\Program Files\Exchange Jetstress\Gen3ESRP3TB\Performance_2011_8_27_18_58_5.blg has 5762 samples. 8/28/2011 7:01:05 PM Creating test report ... 8/28/2011 7:01:45 PM Instance1208.1 has 17.9 for I/O Database Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.1 has 0.5 for I/O Log Writes Average Latency. 8/28/2011 7:01:45 PM Instance1208.1 has 0.5 for I/O Log Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.2 has 18.0 for I/O Database Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.2 has 0.5 for I/O Log Writes Average Latency. 8/28/2011 7:01:45 PM Instance1208.2 has 0.5 for I/O Log Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.3 has 18.0 for I/O Database Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.3 has 0.5 for I/O Log Writes Average Latency. 8/28/2011 7:01:45 PM Instance1208.3 has 0.5 for I/O Log Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.4 has 18.0 for I/O Database Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.4 has 0.5 for I/O Log Writes Average Latency. 8/28/2011 7:01:45 PM Instance1208.4 has 0.5 for I/O Log Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.5 has 18.1 for I/O Database Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.5 has 0.5 for I/O Log Writes Average Latency. 8/28/2011 7:01:45 PM Instance1208.5 has 0.5 for I/O Log Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.6 has 18.0 for I/O Database Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.6 has 0.5 for I/O Log Writes Average Latency. 8/28/2011 7:01:45 PM Instance1208.6 has 0.5 for I/O Log Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.7 has 18.0 for I/O Database Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.7 has 0.5 for I/O Log Writes Average Latency. 8/28/2011 7:01:45 PM Instance1208.7 has 0.5 for I/O Log Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.8 has 18.0 for I/O Database Reads Average Latency. 8/28/2011 7:01:45 PM Instance1208.8 has 0.5 for I/O Log Writes Average Latency. 8/28/2011 7:01:45 PM Instance1208.8 has 0.5 for I/O Log Reads Average Latency. 8/28/2011 7:01:45 PM Test has 0 Maximum Database Page Fault Stalls/sec. 8/28/2011 7:01:45 PM The test has 0 Database Page Fault Stalls/sec samples higher than 0. 8/28/2011 7:01:45 PM C:\Program Files\Exchange Jetstress\Gen3ESRP3TB\Performance_2011_8_27_18_58_5.xml has 5750 samples queried. 8/28/2011 7:01:45 PM C:\Program Files\Exchange Jetstress\Gen3ESRP3TB\Performance_2011_8_27_18_58_5.html was saved. 8/28/2011 7:01:46 PM Performance logging started (interval: 30000 ms). 8/28/2011 7:01:46 PM Verifying database checksums ... 8/28/2011 11:39:08 PM F: (100% processed), G: (100% processed), H: (100% processed) and I: (100% processed) 8/28/2011 11:39:08 PM Performance logging has ended. 8/28/2011 11:39:08 PM C:\Program Files\Exchange Jetstress\Gen3ESRP3TB\DBChecksum_2011_8_28_19_1_45.blg has 554 samples. 8/28/2011 11:39:11 PM C:\Program Files\Exchange Jetstress\Gen3ESRP3TB\DBChecksum_2011_8_28_19_1_45.html was saved. 8/28/2011 11:39:11 PM Verifying log checksums ... 8/28/2011 11:39:19 PM L:\1 (13 logs processed), L:\2 (13 logs processed), L:\3 (12 logs processed), L:\4 (14 logs processed), L:\5 (14 logs processed), L:\6 (13 logs processed), L:\7 (13 logs processed) and L:\8 (13 logs processed) 8/28/2011 11:39:19 PM C:\Program Files\Exchange Jetstress\Gen3ESRP3TB\Application_2011_8_28_23_39_19.evt is saved. 8/28/2011 11:39:19 PM C:\Program Files\Exchange


Solution



Jetstress\Gen3ESRP3TB\System_2011_8_28_23_39_19.evt is saved. 8/28/2011 11:39:19 PM C:\Program Files\Exchange Jetstress\Gen3ESRP3TB\XmlConfig_2011_8_28_23_39_19.xml was saved. 8/28/2011 11:39:19 PM Jetstress testing has ended. 8/29/2011 2:54:06 PM Jetstress testing begins ... 8/29/2011 2:54:06 PM Preparing for testing ... 8/29/2011 2:54:15 PM Attaching databases ... 8/29/2011 2:54:15 PM Preparations for testing are complete. 8/29/2011 2:54:27 PM Performance logging started (interval: 30000 ms). 8/29/2011 2:54:27 PM Backing up databases ... 8/29/2011 6:53:05 PM Performance logging has ended. 8/29/2011 6:53:05 PM Instance1208.1 (100% processed), Instance1208.2 (100% processed), Instance1208.3 (100% processed), Instance1208.4 (100% processed), Instance1208.5 (100% processed), Instance1208.6 (100% processed), Instance1208.7 (100% processed) and Instance1208.8 (100% processed) 8/29/2011 6:53:05 PM C:\Program Files\Exchange Jetstress\Gen3ESRP3TB\DatabaseBackup_2011_8_29_14_54_15.blg has 476 samples. 8/29/2011 6:53:05 PM Creating test report ... 8/29/2011 6:53:08 PM C:\Program Files\Exchange Jetstress\Gen3ESRP3TB\DatabaseBackup_2011_8_29_14_54_15.html was saved. 8/29/2011 6:53:08 PM C:\Program Files\Exchange Jetstress\Gen3ESRP3TB\Application_2011_8_29_18_53_8.evt is saved. 8/29/2011 6:53:08 PM C:\Program Files\Exchange Jetstress\Gen3ESRP3TB\System_2011_8_29_18_53_8.evt is saved. 8/29/2011 6:53:08 PM C:\Program Files\Exchange Jetstress\Gen3ESRP3TB\XmlConfig_2011_8_29_18_53_8.xml was saved. 8/29/2011 6:53:08 PM Jetstress testing has ended. 8/30/2011 5:32:25 AM Jetstress testing begins ... 8/30/2011 5:32:25 AM Preparing for testing ... 8/30/2011 5:32:33 AM Attaching databases ... 8/30/2011 5:32:33 AM Preparations for testing are complete. 8/30/2011 5:32:33 AM Starting transaction dispatch .. 8/30/2011 5:32:33 AM Database cache settings: (minimum: 256.0 MB, maximum: 2.0 GB) 8/30/2011 5:32:33 AM Database flush thresholds: (start: 20.5 MB, stop: 40.9 MB) 8/30/2011 5:32:43 AM Database read latency thresholds: (average: 20 msec/read, maximum: 100 msec/read). 8/30/2011 5:32:43 AM Log write latency thresholds: (average: 10 msec/write, maximum: 100 msec/write). 8/30/2011 5:32:47 AM Operation mix: Sessions 7, Inserts 40%, Deletes 20%, Replaces 5%, Reads 35%, Lazy Commits 70%. 8/30/2011 5:32:47 AM Performance logging started (interval: 15000 ms). 8/30/2011 5:32:47 AM Generating log files ... 8/30/2011 6:40:09 AM L:\1 (100.4% generated), L:\2 (100.4% generated), L:\3 (101.4% generated), L:\4 (100.8% generated), L:\5 (100.8% generated), L:\6 (101.4% generated), L:\7 (102.0% generated) and L:\8 (100.2% generated) 8/30/2011 6:40:09 AM Performance logging has ended. 8/30/2011 6:40:09 AM JetInterop batch transaction stats: 21833, 21869, 21599, 21763, 21908, 21627, 21955 and 21824. 8/30/2011 6:40:09 AM Dispatching transactions ends. 8/30/2011 6:40:09 AM Shutting down databases ... 8/30/2011 6:40:11 AM Instance1208.1 (complete), Instance1208.2 (complete), Instance1208.3 (complete), Instance1208.4 (complete), Instance1208.5 (complete), Instance1208.6 (complete), Instance1208.7 (complete) and Instance1208.8 (complete) 8/30/2011 6:40:11 AM C:\Program Files\Exchange Jetstress\Gen3ESRP3TB\Performance_2011_8_30_5_32_43.blg has 269 samples.


Solution



8/30/2011 6:40:11 AM Creating test report ... 8/30/2011 6:40:12 AM Instance1208.1 has 20.0 for I/O Database Reads Average Latency. 8/30/2011 6:40:12 AM Instance1208.1 has 0.5 for I/O Log Writes Average Latency. 8/30/2011 6:40:12 AM Instance1208.1 has 0.5 for I/O Log Reads Average Latency. 8/30/2011 6:40:12 AM Instance1208.2 has 20.2 for I/O Database Reads Average Latency. 8/30/2011 6:40:12 AM Instance1208.2 has 0.5 for I/O Log Writes Average Latency. 8/30/2011 6:40:12 AM Instance1208.2 has 0.5 for I/O Log Reads Average Latency. 8/30/2011 6:40:12 AM Instance1208.3 has 20.3 for I/O Database Reads Average Latency. 8/30/2011 6:40:12 AM Instance1208.3 has 0.5 for I/O Log Writes Average Latency. 8/30/2011 6:40:12 AM Instance1208.3 has 0.5 for I/O Log Reads Average Latency. 8/30/2011 6:40:12 AM Instance1208.4 has 20.3 for I/O Database Reads Average Latency. 8/30/2011 6:40:12 AM Instance1208.4 has 0.5 for I/O Log Writes Average Latency. 8/30/2011 6:40:12 AM Instance1208.4 has 0.5 for I/O Log Reads Average Latency. 8/30/2011 6:40:12 AM Instance1208.5 has 20.3 for I/O Database Reads Average Latency. 8/30/2011 6:40:12 AM Instance1208.5 has 0.5 for I/O Log Writes Average Latency. 8/30/2011 6:40:12 AM Instance1208.5 has 0.5 for I/O Log Reads Average Latency. 8/30/2011 6:40:12 AM Instance1208.6 has 20.3 for I/O Database Reads Average Latency. 8/30/2011 6:40:12 AM Instance1208.6 has 0.5 for I/O Log Writes Average Latency. 8/30/2011 6:40:12 AM Instance1208.6 has 0.5 for I/O Log Reads Average Latency. 8/30/2011 6:40:12 AM Instance1208.7 has 20.3 for I/O Database Reads Average Latency. 8/30/2011 6:40:12 AM Instance1208.7 has 0.5 for I/O Log Writes Average Latency. 8/30/2011 6:40:12 AM Instance1208.7 has 0.5 for I/O Log Reads Average Latency. 8/30/2011 6:40:12 AM Instance1208.8 has 20.3 for I/O Database Reads Average Latency. 8/30/2011 6:40:12 AM Instance1208.8 has 0.5 for I/O Log Writes Average Latency. 8/30/2011 6:40:12 AM Instance1208.8 has 0.5 for I/O Log Reads Average Latency. 8/30/2011 6:40:12 AM Test has 0 Maximum Database Page Fault Stalls/sec. 8/30/2011 6:40:12 AM The test has 0 Database Page Fault Stalls/sec samples higher than 0. 8/30/2011 6:40:12 AM C:\Program Files\Exchange Jetstress\Gen3ESRP3TB\Performance_2011_8_30_5_32_43.xml has 268 samples queried. 8/30/2011 6:40:12 AM C:\Program Files\Exchange Jetstress\Gen3ESRP3TB\Performance_2011_8_30_5_32_43.html was saved. 8/30/2011 6:40:17 AM Performance logging started (interval: 4000 ms). 8/30/2011 6:40:17 AM Recovering databases ... 8/30/2011 6:52:47 AM Performance logging has ended. 8/30/2011 6:52:47 AM Instance1208.1 (746.5393112), Instance1208.2 (748.6609149), Instance1208.3 (748.3957145), Instance1208.4 (747.0697121), Instance1208.5 (747.3349126), Instance1208.6 (748.130514), Instance1208.7 (746.2741107) and Instance1208.8 (750.2521177) 8/30/2011 6:52:47 AM C:\Program Files\Exchange Jetstress\Gen3ESRP3TB\SoftRecovery_2011_8_30_6_40_12.blg has 186 samples. 8/30/2011 6:52:47 AM Creating test report ...


Solution



Copyright© 2010 by International Business Machines Corporation.

This document could include technical inaccuracies or typographical errors. IBM may make changes, improvements or alterations to the products, programs and services described in this document, including termination of such products, programs and services, at any time and without notice. Any statements regarding IBM’s future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. The information contained in this document is current as of the initial date of publication only, and IBM shall have no responsibility to update such information.

Performance data for IBM and nonIBM products and services contained in this document was derived under specific operating and environmental conditions. The actual results obtained by any party implementing any such products or services will depend on a large number of factors specific to such party’s operating environment and may vary significantly. IBM makes no representation that these results can be expected or obtained in any implementation of any such products or services.

THE INFORMATION IN THIS DOCUMENT IS PROVIDED “ASIS” WITHOUT ANY WARRANTY, EITHER EXPRESS OR IMPLIED. IBM EXPRESSLY DISCLAIMS ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR INFRINGEMENT.

References in this document to IBM products, programs, or services does not imply that IBM intends to make such products, programs or services available in all countries in which IBM operates or does business. Any reference to an IBM program or product in this document is not intended to state or imply that only that program or product may be used. Any functionally equivalent program or product, that does not infringe upon IBM’s intellectual property rights, may be used instead. It is the user’s responsibility to evaluate and verify the operation of any nonIBM product, program or service.

The provision of the information contained herein is not intended to, and does not grant any right or license under any IBM patents or copyrights. Inquiries regarding patent or copyright licenses should be made, in writing, to:

IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 105041785 U.S.A.

IBM, the IBM logo, System x, XIV, XIV Gen3, and System Storage are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries or both.

Microsoft, Windows, and Exchange Server are trademarks of Microsoft Corporation in the United States, other countries or both. i IBM Systems & Technology Group, Littleton, MA, [email protected] ii IBM Systems & Technology Group, Raleigh, NC, [email protected]

mailto:[email protected]?subject=XIV%20ESRP

mailto:[email protected]?subject=XIV%20ESRP


Solution



iii IBM Systems & Technology Group, Littleton, MA, [email protected]

mailto:[email protected]

ibm xiv gen3 storage with 3tb drives:120,000 mailbox resiliency for ms exchange 2010

Technology

storage solution

esrp storage version

gen3 storage systemmodel

mailboxresiliency exchange

mailboxresiliency aviadoffer

tested date

betti poratiiidocument

david hartmanii