HPE StoreVirtual 3200 Storage 1000 Mailbox Resiliency Exchange 2016 Storage Solution

Transcription

1 HPE StoreVirtual 3200 Storage 1000 Mailbox Resiliency Exchange 2016 Storage Solution Technical white paper

2 Technical white paper Contents Introduction... 3 Solution overview... 3 Solution components... 4 HPE StoreVirtual 3200 Storage... 4 HPE StoreVirtual 3200 Management Console... 4 HPE ProLiant DL380 Gen9 Server... 5 HPE StoreFabric SN6000B Fibre Channel Switch... 6 Solution description... 7 Targeted customer profile... 7 Storage configuration... 7 Tested deployment Best practices Test results summary Reliability Storage performance results Database backup and recovery performance Summary Appendix A: Stress testing Microsoft Exchange Jetstress Database sizing and throughput Database configuration Transactional I/O performance Background database maintenance I/O performance Log replication I/O performance Total I/O performance Host system performance Appendix B: Performance testing Microsoft Exchange Jetstress Database sizing and throughput Jetstress system parameters Database configuration Transactional I/O performance Background database maintenance I/O performance Log replication I/O performance Total I/O performance Host system performance Appendix C: Streaming backup testing... 24

3 Technical white paper Microsoft Exchange Jetstress Jetstress system parameters Database configuration Transactional I/O performance Host system performance Appendix D: Soft recovery testing Microsoft Exchange Jetstress Database configuration Transactional I/O performance Background database maintenance I/O performance Total I/O performance Host system performance Resources and additional links... 30

4 Technical white paper Page 3 Introduction This document provides information about the HPE StoreVirtual 3200 Storage and HP ProLiant DL360 Gen9 Server solution for Microsoft Exchange Server 2016, based on the Microsoft Exchange Solution Reviewed Program (ESRP) Storage program. The ESRP Storage program was developed by Microsoft Corporation as a Microsoft Exchange Server program to facilitate third-party storage testing and solution publishing for Exchange Server. For more information about the Microsoft ESRP Storage program, go to Tested with ESRP Storage Version 4.0 Test Date: March 2017 Disclaimer HPE produced this document independently of Microsoft Corporation. Microsoft Corporation expressly disclaims responsibility for, and makes no warranty, expressed or implied, with respect to the accuracy of the contents of this document. Solution overview This solution implements the Database Availability Group (DAG) mailbox resiliency feature found in Microsoft Exchange Server This feature is the base component of the high availability and site resilience framework built into Exchange. A DAG is a group of up to 16 mailbox servers that hosts a set of databases and provides database-level recovery from failures that affect individual servers or databases. This document describes a tested configuration for deploying Microsoft Exchange Server 2016 (Exchange) in a 1000-user, mailbox-resilient environment. The performance results and best practices outlined in this document provide tested guidelines for configuring Exchange with HPE StoreVirtual 3200 Storage (HPE SV3200), HPE ProLiant DL380 Generation9 (Gen9) Server, and HPE Smart Array P441 Controller in a Storage Area Network (SAN) solution. This solution used a single DAG to support 1000 mailboxes, each with a 5 GB mailbox capacity and a work profile of 200 messages sent and received for each user, each day. To provide mailbox resiliency, there are four copies of each database in an Active/Active environment; two copies located at the primary site and two copies located at the secondary site. Microsoft s preferred architecture for Exchange Server 2016 is an Active/Active site deployment with active and passive databases equally distributed across the primary and secondary data centers. In this four-copy configuration, the recommendation is that the primary data center and secondary data center balance the user access equally across sites during normal operations. All four servers in the DAG host active databases supporting 1000 users across both sites. We tested the worst-case scenario with one server running all active databases with BitLocker enabled, using Microsoft s Resilient File System (ReFS). The performance results outlined in this paper are from the testing of a single building block at the secondary site. See Test results summary for more information. HPE Sizer for Microsoft Exchange Server 2016 HPE has developed the HPE Sizer for Microsoft Exchange Server 2016 to assist customers with proper server and storage sizing for their Exchange Server 2016 deployments. The algorithms developed and implemented in this tool originate from extensive testing of Exchange Server 2016 server roles and technologies, HPE s familiarity with Microsoft Exchange Server 2016, and our in-depth knowledge of server CPU, memory, and I/O subsystems. Designed to simplify configuration across a broad range of deployments, this tool is free to download and use. For more information, go to HPE Sizer for Microsoft Exchange Server 2016 ( In addition to the HPE Sizer, HPE recommends that customers use the Microsoft Exchange Mailbox Server Role Requirements Calculator. If this calculator is used as a starting point, it can be imported or read into the HP Sizer using the Load Exchange calculator button.

5 Technical white paper Page 4 Solution components This section describes the components of the HPE StoreVirtual Storage solution for 1000 mailbox resiliency with Exchange Server HPE StoreVirtual 3200 Storage HPE StoreVirtual 3200 Storage (HPE SV3200), shown in Figure 1, is a dual-controller hardware platform focused on low cost and ease of deployment for the small and midsize market. The HPE SV3200 provides high availability (HA) storage in a single enclosure and is an ideal entry-level storage platform for Exchange 2016 messaging solutions. The storage system (storage array) starts with a 2U array enclosure with dual storage controllers with either 25 SFF drive bays or 12 LFF drive bays. The storage system can scale up by adding drives and supports up to three external disk enclosures, increasing the maximum storage capacity to 288 TB when using LFF 6 TB disk drives. Each storage controller supports host connectivity with either two 1GbE ports, four 1GbE ports, two 10GbE ports, two 8 Gb Fibre Channel ports, or two 16 Gb Fibre Channel ports. The HPE SV3200 ships with HPE LeftHand OS 13 Key features 2U dual controller system highly available in the minimal configuration capable of surviving a single controller fault. Ability to select Network RAID 0 or RAID 10 to meet a variety of application needs. SFF and LFF enclosures with flexible drive configurations (SAS HDDs, MDL-SAS HDDs, SAS SSDs). Variety of host connectivity options: 4P/16 Gb FC, 4P/8 Gb FC, 4P/10GbE (SFP+), 8P/1GbE, 4P/1GbE. Redundant, hot-pluggable, and hot-swappable components (storage controller, disks, power supplies, fan modules). Scale up add drives to an existing array enclosure or add up to three drive enclosures to an array enclosure. 12 Gb SAS (array enclosure, disk enclosure, drives). Simple storage management through a web-based user interface. Note These key features of the StoreVirtual 3200 are not recommended for most Microsoft Exchange 2016 deployments: Adaptive Optimization features using two tiers of storage Thin provisioning Figure 1. HPE StoreVirtual 3200 Storage HPE StoreVirtual 3200 Management Console Unlike previous HPE StoreVirtual VSA and HPE ProLiant-based StoreVirtual solutions that used the Centralized Management Console (CMC), HPE StoreVirtual 3200 storage uses the HPE StoreVirtual 3200 Management Console (SVMC), as shown in Figure 2. The SVMC is a built-in, web-based interface that is run from the storage controllers in the management group and manages all the storage systems in that management group. The SVMC interface offers a look and feel similar to the HPE 3PAR StoreServ Management Console (SSMC) and HPE OneView, eliminating infrastructure complexity with automation simplicity.

6 Technical white paper Page 5 Key features Comprehensive, consolidated management with an improved user experience suited for desktops and laptops, as well as tablets. Management through a web-based user interface (no need to install management software on a local PC or workstation). Overview dashboard provides at-a-glance health, capacity, performance, and trending data. 1 Figure 2. HPE StoreVirtual 3200 Management Console HPE ProLiant DL380 Gen9 Server The HPE ProLiant DL380 Gen9 Server, shown in Figure 3, delivers the best performance and expandability in the HPE 2-processor (2P) rack portfolio. Reliability, serviceability, and near-continuous availability, backed by a comprehensive warranty, make it ideal for any environment. Key features Purpose-built for flexibility, efficiency, and manageability Designed to adapt to the needs of any environment from the large enterprise to the remote office or branch office (ROBO) customer. Growing messaging solutions Remove bottlenecks and improve the performance of Microsoft Exchange deployments. Future-proof design with flexible options Choose the features and functions needed now; add more as necessary, as business needs grow; the modular chassis, networking, and controller designs allow for easy upgrades. Pay for what is needed, when it is needed. Industry-leading performance and energy-efficiency Deliver faster business results and quicker returns on investment. DL380 Gen9 supports industry standard Intel Xeon E v3 and E v4 processors with up to 22 cores, 12G SAS, and HPE DDR4 Smart Memory bundled with high-efficiency redundant HPE Flexible Slot Power Supplies. 1 For more information about HPE StoreVirtual Storage and the HPE StoreVirtual Management Console, go to

7 Technical white paper Page 6 Figure 3. HPE ProLiant DL380 Gen9 Server HPE StoreFabric SN6000B Fibre Channel Switch The HPE SN6000B Fibre Channel Switch meets the demands of hyper-scale, private cloud storage environments by delivering market-leading 16 Gb Fibre Channel technology and capabilities that support highly virtualized environments. Designed to enable maximum flexibility and investment protection, the HPE SN6000B Switch is configurable in 24, 36, or 48 ports and supports 4, 8, 10, or 16 Gbps speeds in an efficiently designed 1U package. The HPE SN6000B Switch also provides a simplified deployment process and a point-and-click user interface making it both powerful and easy to use. The HPE SN6000B Switch offers low-cost access to industry-leading Storage Area Network (SAN) technology while providing pay-as-you-grow scalability to meet the needs of an evolving storage environment. Figure 4. HPE SN6000B Fibre Channel Switch Key features and benefits Delivers 16 Gbps performance with up to 48 ports in an energy-efficient, 1U form factor, providing maximum flexibility for diverse deployment and cooling strategies. Features Ports on Demand (PoD) capabilities for fast, easy, and cost-effective scaling from 24 to 48 ports in 12-port increments. Provides a flexible, simple, and easy-to-use SAN solution with industry-leading technology. Supports highly virtualized, private cloud storage with multi-tenancy and non-stop operations. Offers best-in-class port density and scalability for midrange enterprise SAN switches, along with redundant, hot-pluggable components and non-disruptive software upgrades. Metro cloud connectivity features including integrated DWDM and dark fiber support (optional license). In-flight compression and encryption included providing efficient link utilization and security. Yields exceptional price/performance value, exceeding comparable Ethernet storage-based alternatives.

8 Technical white paper Page 7 Solution description As described in Solution components on page 4, this solution is designed with two HPE SV3200 Storage systems for a 1,000 user Exchange 2016 deployment, and with high availability through Exchange 2016 DAG copies, using four active servers in the solution. Mailbox resiliency data protection is provided by configuring multiple database copies on a minimum of two HPE SV3200 Storage systems. Only one HPE SV3200 Storage system was included in the testing described in this document. This document provides best practices to help administrators implement an Exchange deployment with the environment below. Targeted customer profile A single Database Availability Group (DAG) deployment with two mailbox servers in the primary site and two mailbox servers in the secondary site, for a total of four mailbox servers across the entire solution. 1,000 mailbox users (250 user mailboxes per server). Exchange 2016 profile of 0.16 IOPS workload per user (200 messages sent and received per user, per day). 5 GB mailbox size. Four copies of each mailbox database (one active and three passive). Twelve databases per server (six active and six passive). Background Database Maintenance (BDM) enabled in testing. Designed for server and site resiliency. 24 6TB 12G SAS 7.2K Large Form Factor (LFF) (3.5-inch) Dual Port MDL hard drives per array for the Exchange databases and transaction logs. Storage configuration This solution uses the HPE SV3200 in the building block and contains one LFF storage system and three LFF disk enclosures. The storage system and disk enclosures each contain (12) 6 TB LFF disk drives for a total of (48) disk drives or 288 TB of raw storage capacity before RAID. The cache memory of SV3200 is 1 GB. The cache algorithm uses internal tuning, but it is not user configurable. The Exchange databases, logs, and restore volumes reside on the disk drives. The drive enclosures are connected to the array enclosure using an asymmetric cabling scheme. The cabling scheme is shown in Figure 5. The HPE StoreVirtual 3200 Storage cabling view maintains the high availability of the disk enclosures and is the only supported cabling scheme.

9 Technical white paper Page 8 Figure 5. HPE StoreVirtual 3200 Storage cabling view Figure 5. Callouts 1. Array enclosure 4. Disk enclosure 3 2. Disk enclosure 1 5. Primary and secondary paths (16 Gb FC) 3. Disk enclosure 2 6. Primary and secondary paths (12 Gb SAS) HPE Smart Storage Administrator HPE Smart Storage Administrator (HPE SSA) is the main tool for configuring arrays on HPE Smart Array Controllers. HPE SSA exists in three interface formats: the HPE SSA GUI, the HPE SSA CLI, and HPE SSA Scripting. All formats provide support for configuration tasks. For more information, refer to the following: HPE Smart Storage Administrator Scripting Cookbook HPE Smart Array Controllers User Guide for HP ProLiant Gen9 Servers

10 Technical white paper Page 9 Mailbox configuration primary site operational Figure 6 shows a fully functional scenario using four servers in the DAG hosting active and passive databases from two HPE SV3200 Storage systems, one per data center. In a data center failover scenario, the two servers in the SDC are able to serve all the databases. 1,000 mailbox users IOPS workload per user (200 messages sent and received per user, per day, with an additional 20% headroom). 5 GB mailbox size. Four copies of each mailbox database (one active / three passive). Twelve databases per server (six active and six passive). 24 6TB 12G SAS 7.2K LFF (3.5-inch) Dual Port MDL hard drives. Designed for server and site resiliency. Background Database Maintenance (BDM) enabled. Figure 6. Exchange building block for primary data center (duplicated in secondary data center)

11 Technical white paper Page 10 Mailbox configuration Primary site offline and single server failure at secondary data site (planned or unplanned) Figure 7 shows the tested mailbox layout for active database copies when the primary site and one of the servers in the secondary data center (SDC) site are unavailable due to a planned or unplanned event. This solution demonstrates the worst-case scenario with one host in the SDC hosting 22 active databases, with the following requirements: 1,000 mailbox users IOPS workload per user (200 messages sent and received per user, per day, with an additional 20% headroom). 5 GB mailbox size. Primary site s database copies and one of the two servers at the secondary site are unavailable due to a planned or unplanned event. The mailbox server in the secondary site hosts 12 database copies all active. Background Database Maintenance (BDM) enabled. Figure 7: Primary site unavailable and single server failure at secondary site

12 Technical white paper Page 11 Tested deployment The following tables summarize the tested environment. Table 1. Simulated Exchange environment Number of Exchange mailboxes simulated 1,000 (5 GB mailbox size Number of Database Availability Groups (DAGs) 1 Number of active mailbox servers per DAG Number of active mailboxes per server Number of databases per server 12 Number of copies per database Number of active mailboxes per database 63 Simulated profile: I/O operations per second per mailbox (IOPS, include 20% headroom) Database and Log LUN size per database Total database size for performance testing Background database maintenance (BDM) 4 (1 hosting active mailboxes in test) 1,000 (tested scenario) 4 (2 at primary / 2 at secondary) TB GB Tested with 24/7 BDM enabled % formatted storage capacity used by Exchange database 1.7% GB / GB (Total database size /Total formatted capacity) Table 2. Storage hardware Storage platform Product model HPE StoreVirtual 3200 Storage HPE SV3200 OS version 13.5 Number of storage systems/type 1/LFF Number of disk enclosures/type 2/LFF Number of disk drives/type 48/6 TB 12G SAS 7.2K LFF MDL HDD Number of host ports used in solution/type 4 x 16 Gbps Fibre Channel HPE SV3200 storage cluster Number of storage pools 1 Number of volumes per server 12 database and log volumes Provisioning Fully provisioned Hardware RAID RAID 10 (databases and logs volumes) Network RAID RAID 10 Cache memory size 1 GB Number of host physical servers 2 Product model HPE ProLiant DL380 Gen9 Rack Server CPU 2 x Intel Xeon E v3 Memory 256 GB Number of type of drives 2 x 800 GB 12G SAS SSD Fibre Channel HBA 2 x SN1100E 16 Gbps 2P FC HBA Ethernet HBA 2 x 530SFP+ 10 Gbps 2P Adapter 1 x 366FLR 1 Gbps 4P Adapter Operating system Microsoft Windows Server 2012 R2 (Server Core Installation)

13 Technical white paper Page 12 Number of virtual guest servers (VMs) 2 CPU Memory Disk Host bus adaptors Operating system 8 v CPU 64 GB 400 GB 16 Gbps Fibre Channel Microsoft Windows Server 2012 R2 (data center) Table 3. Storage disk configuration (mailbox and log disks) Disk type, speed, and firmware version Raw capacity for each disk (TB) Number of physical disks in test 12 Total raw storage capacity (TB) HP 6 TB 12G SAS 7.2K LFF (3.5in) Dual Port MDL Firmware Version: HPD2 6 TB 72 TB* RAID level & Set Size RAID 10 Stripe Size (KiB) 256 Total formatted capacity (GB) GB Storage capacity utilization 17.06% GB /72 TB (Formatted capacity/ Total Raw capacity) Database capacity utilization 0.29% 214.2GB /72 GB (Total database size / Total Raw capacity) * Capacity of drives, and therefore the raw data capacity of the disk array, which is based on 1KB = 1000 bytes, not on 1024 bytes. This means that 1GB equals 1,000,000,000 bytes, not 1,073,741,824 bytes. Best practices When deploying Exchange, it is important to not only size for storage capacity but to also consider the storage performance demands. Validating that the storage subsystem is capable of supporting the anticipated and future workload minimizes the risk of the disk subsystem becoming an I/O bottleneck. Exchange Server is a disk-intensive application. For Exchange 2016 best practices on storage design from Microsoft, go to Based on the testing run using the ESRP framework, we recommend the following to improve storage performance: Drivers and firmware Ensure that firmware and drivers for all hardware in the solution are up-to-date. For more information, go to Physical Drive Write Cache Unlike controller-level cache, individual drive write caches are not protected. If the server loses power, or a hot plug drive is physically removed from the array during operations, unwritten data in the physical drives write caches will be lost. HPE recommends disabling Physical Drive Write Cache on the HPE Smart Array P441 Controller. For more information, go to Accelerator Ratio and Flash-Backed Write Cache (FBWC) HPE recommends setting 75 percent write cache and 25 percent read cache (battery-backed cache).

14 Technical white paper Page 13 Jetstress Before installing Exchange Server 2016, test your storage solution with Jetstress to ensure it is configured properly and meets your requirements. To download Jetstress, go to Mailbox database copies HPE recommends 4 database copies, 2 in each datacenter. Stripe size For Exchange deployments, HPE recommends using a strip size of 256 KB or larger for your selected RAID level. The strip size was configured for 256 KB for this solution testing. For more information, go to RAID level Database volumes used in this solution were configured as follows: Hardware RAID - RAID 10 (databases and logs volumes), Network RAID - RAID 10. BitLocker Drive Encryption BitLocker Drive Encryption provides considerable protection for data volumes. For more information about Windows BitLocker, go to Windows Volumes For best performance, format the Windows volumes with 64 KB allocation unit size with ReFS file system. Test results summary This section provides a high-level summary of the test data from the ESRP and a reference to the detailed HTML reports, generated by the ESRP testing framework. For solutions that use a uniform building block style, in which each building block is independent and isolated, ESRP requires testing only one building block. For this solution, a building block consisted of one HP ProLiant DL360 Gen9 Server and one HP D3600 Disk Enclosure, with 11 x 6 TB LFF SAS drives hosting all 4,000 mailboxes. Reliability Reliability testing exercises the storage with the maximum sustainable Exchange I/O load for 24 hours. The goal is to verify that the storage can handle the maximum I/O load for an extended period of time. Both log and database files are analyzed for integrity after the stress test to confirm that no database or log corruption occurred. After running the 24-hour test, we found no errors reported in the event log for the storage reliability testing and no errors reported for the checksum process. Storage performance results Storage performance testing exercises the storage with the maximum sustainable Exchange I/O load for two hours. The test measures storage I/O response times under the maximum sustainable Exchange I/O load. The following data is the sum of all logical disk I/Os and an average of all logical disk I/O latency in the two-hour test duration. This solution design is an Exchange deployment with a single DAG. The DAG has two mailbox servers in the primary site and two mailbox servers in the disaster recovery site. Ideally, the two servers in the disaster recovery site should host all active mailboxes when the primary site is offline (planned or unplanned.) Table 4 shows the worst-case scenario when one server is running all four databases. Table 4. Performance results Database I/O Necessary Disk Transfers/sec* 160 Database Disk Transfers/sec 377

15 Technical white paper Page 14 Database Disk Reads/sec 224 Database Disk Writes/sec 154 Average Database Disk Read Latency (ms) Average Database Disk Write Latency (ms) 7.3 Transaction Log I/O Log Disk Writes/sec 40 Average Log Disk Write Latency (ms) 3.32 * This data represents the total IOPS necessary to satisfy the IOPS for all mailboxes in the solution. Database backup and recovery performance This section contains two test reports. The first report measures the sequential read rate of the database files; the second report measures the recovery/replay performance (playing transaction logs into the database). The tests measure the read rates and log replay rates with all mailboxes under concurrent or simultaneous load. Database read-only performance This test measures the maximum backup rate for Volume Shadow Copy Service (VSS) aware backup applications. The following table shows the average and the sum of the database reads. Table 5. Maximum backup rate for Volume Shadow Copy Service (VSS) aware backup applications Average MB read/sec per database MB read/sec total Transaction log recovery and replay performance This test measures the maximum rate that log files can play against the databases. The following table shows the average rate for log files played. Each log file is 1 MB in size. Table 6: Maximum log file rate Average number of log files played 505 Average time to play one log file (sec) 2.2

16 Technical white paper Page 15 Summary The information in this technical white paper highlights the tested performance results and configuration best practices for an Exchange solution supporting 1,000 5 GB mailboxes and a 0.16 IOPS workload for each user (200 messages sent and received per user). The tested solution included an HPE SV3200 Storage with 24 6TB 7.2K LFF SAS drives for the mailbox database storage and transaction logs and 12 database volumes encrypted using BitLocker Drive Encryption. The test results demonstrated in this document are summarized below. Test results The HPE SV3200 Storage subsystem was capable of an aggregate 377 disk transfers per second, contains the necessary capacity to support 1,000 Exchange users with 5 GB mailboxes, and provides additional performance headroom. The test results and data presented in this document are from the ESRP test framework. Test results are only a guide; administrators should test their solution to make sure it meets requirements for their specific environment. Note The ESRP program is not a benchmarking program. The tests do not measure the maximum throughput for a given solution. Rather, program focus is on producing recommendations from vendors for Exchange Server storage solutions. Data presented in this document should not be used for direct comparisons among solutions. Appendix A: Stress testing Microsoft Exchange Jetstress 2013 Table 7. Microsoft Exchange Jetstress 2013 Test Summary Overall Test Result Machine Name Pass VM1 Test Description Test Start Time Test End Time Collection Start Time Collection End Time 5/15/ :22:28 AM 5/16/2017 1:43:43 PM 5/15/ :44:32 AM 5/16/ :44:26 AM Jetstress Version ESE Version Operating System Windows Server 2012 R2 data center ( ) Performance Log C:\Program Files\Exchange Jetstress\My_TEST\24_HRS_TEST_TC6\Stress_2017_5_15_11_23_6.blg Database sizing and throughput Table 8. Database sizing and throughput Achieved Transactional I/O per Second Target Transactional I/O per Second 160 Initial Database Size (bytes)

17 Technical white paper Page 16 Final Database Size (bytes) Database Files (Count) 12 Jetstress system parameters Table 9. Jetstress system parameters Thread Count 6 Minimum Database Cache Maximum Database Cache MB MB Insert Operations 40% Delete Operations 20% Replace Operations 5% Read Operations 35% Lazy Commits 70% Run Background Database Maintenance Number of Copies per Database True 4 Database configuration Table 10. Database configuration Instance Instance Instance Instance Instance Instance Instance Instance Instance Log path: C:\DBLG1 Database: C:\DBLG1\Jetstress edb Log path: C:\DBLG2 Database: C:\DBLG2\Jetstress edb Log path: C:\DBLG3 Database: C:\DBLG3\Jetstress edb Log path: C:\DBLG4 Database: C:\DBLG4\Jetstress edb Log path: C:\DBLG5 Database: C:\DBLG5\Jetstress edb Log path: C:\DBLG6 Database: C:\DBLG6\Jetstress edb Log path: C:\DBLG7 Database: C:\DBLG7\Jetstress edb Log path: C:\DBLG8 Database: C:\DBLG8\Jetstress edb Log path: C:\DBLG9 Database: C:\DBLG9\Jetstress edb Instance Log path: C:\DBLG10 Database: C:\DBLG10\Jetstress edb Instance Log path: C:\DBLG11 Database: C:\DBLG11\Jetstress edb Instance Log path: C:\DBLG12 Database: C:\DBLG12\Jetstress edb

18 Technical white paper Page 17 Transactional I/O performance Figure 8. Transactional I/O performance Background database maintenance I/O performance Figure 9. Background database maintenance I/O performance Log replication I/O performance Figure 10. Log replication I/O performance

19 Technical white paper Page 18 Total I/O performance Figure 11. Total I/O performance Host system performance Figure 12. Host system performance Test log 5/15/ :22:28 AM -- Preparing for testing... 5/15/ :22:41 AM -- Attaching databases... 5/15/ :22:41 AM -- Preparations for testing are complete. 5/15/ :22:41 AM -- Starting transaction dispatch.. 5/15/ :22:42 AM -- Database cache settings: (minimum: MB, maximum: 3.0 GB) 5/15/ :22:42 AM -- Database flush thresholds: (start: 30.7 MB, stop: 61.4 MB) 5/15/ :23:06 AM -- Database read latency thresholds: (average: 20 msec/read, maximum: 200 msec/read). 5/15/ :23:06 AM -- Log write latency thresholds: (average: 10 msec/write, maximum: 200 msec/write). 5/15/ :23:09 AM -- Operation mix: Sessions 6, Inserts 40%, Deletes 20%, Replaces 5%, Reads 35%, Lazy Commits 70%. 5/15/ :23:09 AM -- Performance logging started (interval: ms). 5/15/ :23:09 AM -- Attaining prerequisites: 5/15/ :44:32 AM -- \MSExchange Database(JetstressWin)\Database Cache Size, Last: (lower bound: , upper bound: none) 5/16/ :44:33 AM -- Performance logging has ended. 5/16/2017 1:43:04 PM -- JetInterop batch transaction stats: 98701, 98701, 98701, 98700, 98700, 98700, 98700, 98700, 98700, 98700, and /16/2017 1:43:04 PM -- Dispatching transactions ends. 5/16/2017 1:43:04 PM -- Shutting down databases... 5/16/2017 1:43:43 PM -- Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete) and Instance (complete) 5/16/2017 1:43:43 PM -- C:\Program Files\Exchange Jetstress\My_TEST\24_HRS_TEST_TC6\Stress_2017_5_15_11_23_6.blg has 5824 samples. 5/16/2017 1:43:43 PM -- Creating test report... 5/16/2017 1:44:42 PM -- Instance has 10.5 for I/O Database Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Writes Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Reads Average Latency.

20 Technical white paper Page 19 5/16/2017 1:44:42 PM -- Instance has 10.6 for I/O Database Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Writes Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 10.6 for I/O Database Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Writes Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 10.5 for I/O Database Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Writes Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 10.6 for I/O Database Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Writes Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 10.6 for I/O Database Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Writes Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 10.6 for I/O Database Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Writes Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 10.6 for I/O Database Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Writes Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 10.5 for I/O Database Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Writes Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 10.7 for I/O Database Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Writes Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 10.6 for I/O Database Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Writes Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 10.6 for I/O Database Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Writes Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Reads Average Latency. 5/16/2017 1:44:42 PM -- Test has 0 Maximum Database Page Fault Stalls/sec. 5/16/2017 1:44:42 PM -- The test has 0 Database Page Fault Stalls/sec samples higher than 0. 5/16/2017 1:44:42 PM -- C:\Program Files\Exchange Jetstress\My_TEST\24_HRS_TEST_TC6\Stress_2017_5_15_11_23_6.xml has 5738 samples queried. Appendix B: Performance testing Microsoft Exchange Jetstress 2013 Table 11: Microsoft Exchange Jetstress 2013 Overall Test Result Machine Name Pass VM1 Test Description Test Start Time Test End Time 5/4/2017 3:12:31 PM 5/5/2017 9:43:40 AM Collection Start Time 5/4/2017 3:34:54 PM Collection End Time 5/4/2017 5:34:43 PM

21 Technical white paper Page 20 Jetstress Version ESE Version Operating System Windows Server 2012 R2 data center ( ) Performance Log C:\Program Files\Exchange Jetstress\My_TEST\2_HRS_TEST_TC6\Performance_2017_5_4_15_13_10.blg Database sizing and throughput Table 12: Database sizing and throughput Achieved Transactional I/O per Second Target Transactional I/O per Second 160 Initial Database Size (bytes) Final Database Size (bytes) Database Files (Count) 12 Jetstress system parameters Table 13: Jetstress system parameters Thread Count 6 Minimum Database Cache Maximum Database Cache MB 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 4 Database configuration Table 14: Database configuration Instance Instance Instance Instance Instance Instance Log path: C:\DBLG1 Database: C:\DBLG1\Jetstress edb Log path: C:\DBLG2 Database: C:\DBLG2\Jetstress edb Log path: C:\DBLG3 Database: C:\DBLG3\Jetstress edb Log path: C:\DBLG4 Database: C:\DBLG4\Jetstress edb Log path: C:\DBLG5 Database: C:\DBLG5\Jetstress edb Log path: C:\DBLG6 Database: C:\DBLG6\Jetstress edb

22 Technical white paper Page 21 Instance Instance Instance Log path: C:\DBLG7 Database: C:\DBLG7\Jetstress edb Log path: C:\DBLG8 Database: C:\DBLG8\Jetstress edb Log path: C:\DBLG9 Database: C:\DBLG9\Jetstress edb Instance Log path: C:\DBLG10 Database: C:\DBLG10\Jetstress edb Instance Log path: C:\DBLG11 Database: C:\DBLG11\Jetstress edb Instance Log path: C:\DBLG12 Database: C:\DBLG12\Jetstress edb Transactional I/O performance Figure 13. Transactional I/O performance Background database maintenance I/O performance Figure 14. Background database maintenance I/O performance

23 Technical white paper Page 22 Log replication I/O performance Figure 15. Log replication I/O performance Total I/O performance Figure 16. Total I/O performance Host system performance Figure 17. Host system performance Test log 5/15/ :22:28 AM -- Preparing for testing... 5/15/ :22:41 AM -- Attaching databases... 5/15/ :22:41 AM -- Preparations for testing are complete. 5/15/ :22:41 AM -- Starting transaction dispatch.. 5/15/ :22:42 AM -- Database cache settings: (minimum: MB, maximum: 3.0 GB) 5/15/ :22:42 AM -- Database flush thresholds: (start: 30.7 MB, stop: 61.4 MB)

24 Technical white paper Page 23 5/15/ :23:06 AM -- Database read latency thresholds: (average: 20 msec/read, maximum: 200 msec/read). 5/15/ :23:06 AM -- Log write latency thresholds: (average: 10 msec/write, maximum: 200 msec/write). 5/15/ :23:09 AM -- Operation mix: Sessions 6, Inserts 40%, Deletes 20%, Replaces 5%, Reads 35%, Lazy Commits 70%. 5/15/ :23:09 AM -- Performance logging started (interval: ms). 5/15/ :23:09 AM -- Attaining prerequisites: 5/15/ :44:32 AM -- \MSExchange Database(JetstressWin)\Database Cache Size, Last: (lower bound: , upper bound: none) 5/16/ :44:33 AM -- Performance logging has ended. 5/16/2017 1:43:04 PM -- JetInterop batch transaction stats: 98701, 98701, 98701, 98700, 98700, 98700, 98700, 98700, 98700, 98700, and /16/2017 1:43:04 PM -- Dispatching transactions ends. 5/16/2017 1:43:04 PM -- Shutting down databases... 5/16/2017 1:43:43 PM -- Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete) and Instance (complete) 5/16/2017 1:43:43 PM -- C:\Program Files\Exchange Jetstress\My_TEST\24_HRS_TEST_TC6\Stress_2017_5_15_11_23_6.blg has 5824 samples. 5/16/2017 1:43:43 PM -- Creating test report... 5/16/2017 1:44:42 PM -- Instance has 10.5 for I/O Database Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Writes Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 10.6 for I/O Database Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Writes Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 10.6 for I/O Database Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Writes Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 10.5 for I/O Database Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Writes Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 10.6 for I/O Database Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Writes Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 10.6 for I/O Database Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Writes Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 10.6 for I/O Database Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Writes Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 10.6 for I/O Database Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Writes Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 10.5 for I/O Database Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Writes Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 10.7 for I/O Database Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Writes Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 10.6 for I/O Database Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Writes Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 10.6 for I/O Database Reads Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Writes Average Latency. 5/16/2017 1:44:42 PM -- Instance has 3.5 for I/O Log Reads Average Latency. 5/16/2017 1:44:42 PM -- Test has 0 Maximum Database Page Fault Stalls/sec. 5/16/2017 1:44:42 PM -- The test has 0 Database Page Fault Stalls/sec samples higher than 0. 5/16/2017 1:44:42 PM -- C:\Program Files\Exchange Jetstress\My_TEST\24_HRS_TEST_TC6\Stress_2017_5_15_11_23_6.xml has 5738 samples queried.

25 Technical white paper Page 24 Appendix C: Streaming backup testing Microsoft Exchange Jetstress 2013 Database Backup Test Result Report Database Backup Statistics All Figure 18. Microsoft Exchange Jetstress 2013 Jetstress system parameters Table 15: Jetstress system parameters Thread Count 6 Minimum Database Cache MB Maximum Database Cache MB Insert Operations 40% Delete Operations 20% Replace Operations 5% Read Operations 35% Lazy Commits 70% Database configuration Table 16: Database configuration Instance Instance Instance Log path: C:\DB1 Database: C:\DB1\Jetstress edb Log path: C:\DB2 Database: C:\DB2\Jetstress edb Log path: C:\DB3 Database: C:\DB3\Jetstress edb

26 Technical white paper Page 25 Instance Instance Instance Instance Instance Instance Log path: C:\DB4 Database: C:\DB4\Jetstress edb Log path: C:\DB5 Database: C:\DB5\Jetstress edb Log path: C:\DB6 Database: C:\DB6\Jetstress edb Log path: C:\DB7 Database: C:\DB7\Jetstress edb Log path: C:\DB8 Database: C:\DB8\Jetstress edb Log path: C:\DB9 Database: C:\DB9\Jetstress edb Instance Log path: C:\DB10 Database: C:\DB10\Jetstress edb Instance Log path: C:\DB11 Database: C:\DB11\Jetstress edb Instance Log path: C:\DB12 Database: C:\DB12\Jetstress edb Transactional I/O performance Figure 19. Transactional I/O performance Host system performance Figure 20. Host system performance

27 Technical white paper Page 26 Test log 4/12/2017 9:48:19 AM -- Preparing for testing... 4/12/2017 9:48:32 AM -- Attaching databases... 4/12/2017 9:48:32 AM -- Preparations for testing are complete. 4/12/2017 9:48:47 AM -- Performance logging started (interval: ms). 4/12/2017 9:48:47 AM -- Backing up databases... 4/12/2017 9:57:48 AM -- Performance logging has ended. 4/12/2017 9:57:48 AM -- Instance (100% processed), Instance (100% processed), Instance (100% processed), Instance (100% processed), Instance (100% processed), Instance (100% processed), Instance (100% processed), Instance (100% processed), Instance (100% processed), Instance (100% processed), Instance (100% processed) and Instance (100% processed) 4/12/2017 9:57:48 AM -- C:\Program Files\Exchange Jetstress\My_TEST\DB_Backup\DatabaseBackup_2017_4_12_9_48_32.blg has 35 samples. 4/12/2017 9:57:48 AM -- Creating test report... Appendix D: Soft recovery testing Microsoft Exchange Jetstress 2013 Soft Recovery Test Result Report Soft-Recovery Statistics - All Figure 21. Microsoft Exchange Jetstress 2013 Database configuration Table 17: Database configuration Instance Instance Instance Instance Instance Instance Log path: C:\DB1 Database: C:\DB1\Jetstress edb Log path: C:\DB2 Database: C:\DB2\Jetstress edb Log path: C:\DB3 Database: C:\DB3\Jetstress edb Log path: C:\DB4 Database: C:\DB4\Jetstress edb Log path: C:\DB5 Database: C:\DB5\Jetstress edb Log path: C:\DB6 Database: C:\DB6\Jetstress edb

28 Technical white paper Page 27 Instance Instance Instance Log path: C:\DB7 Database: C:\DB7\Jetstress edb Log path: C:\DB8 Database: C:\DB8\Jetstress edb Log path: C:\DB9 Database: C:\DB9\Jetstress edb Instance Log path: C:\DB10 Database: C:\DB10\Jetstress edb Instance Log path: C:\DB11 Database: C:\DB11\Jetstress edb Instance Log path: C:\DB12 Database: C:\DB12\Jetstress edb Transactional I/O performance Figure 22. Transactional I/O performance Background database maintenance I/O performance Figure 23. Background database maintenance I/O performance

29 Technical white paper Page 28 Total I/O performance Figure 24. Total I/O performance Host system performance Figure 25. Host system performance Test log Test Log4/12/ :48:32 AM -- Preparing for testing... 4/12/ :48:44 AM -- Attaching databases... 4/12/ :48:44 AM -- Preparations for testing are complete. 4/12/ :48:44 AM -- Starting transaction dispatch.. 4/12/ :48:45 AM -- Database cache settings: (minimum: MB, maximum: 3.0 GB) 4/12/ :48:45 AM -- Database flush thresholds: (start: 30.7 MB, stop: 61.4 MB) 4/12/ :49:03 AM -- Database read latency thresholds: (average: 20 msec/read, maximum: 100 msec/read). 4/12/ :49:03 AM -- Log write latency thresholds: (average: 10 msec/write, maximum: 100 msec/write). 4/12/ :49:05 AM -- Operation mix: Sessions 6, Inserts 40%, Deletes 20%, Replaces 5%, Reads 35%, Lazy Commits 70%. 4/12/ :49:05 AM -- Performance logging started (interval: ms). 4/12/ :49:05 AM -- Generating log files... 4/12/2017 3:17:50 PM -- C:\DB1 (100.6% generated), C:\DB2 (101.6% generated), C:\DB3 (100.6% generated), C:\DB4 (100.8% generated), C:\DB5 (101.6% generated), C:\DB6 (100.6% generated), C:\DB7 (100.8% generated), C:\DB8 (100.6% generated), C:\DB9 (101.2% generated), C:\DB10 (100.2% generated), C:\DB11 (100.2% generated) and C:\DB12 (100.6% generated) 4/12/2017 3:17:50 PM -- Performance logging has ended. 4/12/2017 3:17:51 PM -- JetInterop batch transaction stats: 17704, 17704, 17704, 17704, 17704, 17704, 17704, 17704, 17703, 17703, and /12/2017 3:17:51 PM -- Dispatching transactions ends. 4/12/2017 3:17:51 PM -- Shutting down databases... 4/12/2017 3:18:29 PM -- Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete), Instance (complete) and Instance (complete) 4/12/2017 3:18:29 PM -- C:\Program Files\Exchange Jetstress\My_TEST\Soft_Recovery\Performance_2017_4_12_10_49_3.blg has 1072 samples. 4/12/2017 3:18:29 PM -- Creating test report... 4/12/2017 3:18:36 PM -- Instance has 11.4 for I/O Database Reads Average Latency. 4/12/2017 3:18:36 PM -- Instance has 3.7 for I/O Log Writes Average Latency. 4/12/2017 3:18:36 PM -- Instance has 3.7 for I/O Log Reads Average Latency. 4/12/2017 3:18:36 PM -- Instance has 11.3 for I/O Database Reads Average Latency. 4/12/2017 3:18:36 PM -- Instance has 3.7 for I/O Log Writes Average Latency. 4/12/2017 3:18:36 PM -- Instance has 3.7 for I/O Log Reads Average Latency. 4/12/2017 3:18:36 PM -- Instance has 11.4 for I/O Database Reads Average Latency. 4/12/2017 3:18:36 PM -- Instance has 3.7 for I/O Log Writes Average Latency. 4/12/2017 3:18:36 PM -- Instance has 3.7 for I/O Log Reads Average Latency. 4/12/2017 3:18:36 PM -- Instance has 11.4 for I/O Database Reads Average Latency. 4/12/2017 3:18:36 PM -- Instance has 3.7 for I/O Log Writes Average Latency. 4/12/2017 3:18:36 PM -- Instance has 3.7 for I/O Log Reads Average Latency.

30 Technical white paper Page 29 4/12/2017 3:18:36 PM -- Instance has 11.4 for I/O Database Reads Average Latency. 4/12/2017 3:18:36 PM -- Instance has 3.7 for I/O Log Writes Average Latency. 4/12/2017 3:18:36 PM -- Instance has 3.7 for I/O Log Reads Average Latency. 4/12/2017 3:18:36 PM -- Instance has 11.4 for I/O Database Reads Average Latency. 4/12/2017 3:18:36 PM -- Instance has 3.7 for I/O Log Writes Average Latency. 4/12/2017 3:18:36 PM -- Instance has 3.7 for I/O Log Reads Average Latency. 4/12/2017 3:18:36 PM -- Instance has 11.3 for I/O Database Reads Average Latency. 4/12/2017 3:18:36 PM -- Instance has 3.8 for I/O Log Writes Average Latency. 4/12/2017 3:18:36 PM -- Instance has 3.8 for I/O Log Reads Average Latency. 4/12/2017 3:18:36 PM -- Instance has 11.8 for I/O Database Reads Average Latency. 4/12/2017 3:18:36 PM -- Instance has 3.2 for I/O Log Writes Average Latency. 4/12/2017 3:18:36 PM -- Instance has 3.2 for I/O Log Reads Average Latency. 4/12/2017 3:18:36 PM -- Instance has 11.8 for I/O Database Reads Average Latency. 4/12/2017 3:18:36 PM -- Instance has 3.3 for I/O Log Writes Average Latency. 4/12/2017 3:18:36 PM -- Instance has 3.3 for I/O Log Reads Average Latency. 4/12/2017 3:18:36 PM -- Instance has 11.9 for I/O Database Reads Average Latency. 4/12/2017 3:18:36 PM -- Instance has 3.3 for I/O Log Writes Average Latency. 4/12/2017 3:18:36 PM -- Instance has 3.3 for I/O Log Reads Average Latency. 4/12/2017 3:18:36 PM -- Instance has 11.9 for I/O Database Reads Average Latency. 4/12/2017 3:18:36 PM -- Instance has 3.3 for I/O Log Writes Average Latency. 4/12/2017 3:18:36 PM -- Instance has 3.3 for I/O Log Reads Average Latency. 4/12/2017 3:18:36 PM -- Instance has 11.8 for I/O Database Reads Average Latency. 4/12/2017 3:18:36 PM -- Instance has 3.2 for I/O Log Writes Average Latency. 4/12/2017 3:18:36 PM -- Instance has 3.2 for I/O Log Reads Average Latency. 4/12/2017 3:18:36 PM -- Test has 0 Maximum Database Page Fault Stalls/sec. 4/12/2017 3:18:36 PM -- The test has 0 Database Page Fault Stalls/sec samples higher than 0. 4/12/2017 3:18:36 PM -- C:\Program Files\Exchange Jetstress\My_TEST\Soft_Recovery\Performance_2017_4_12_10_49_3.xml has 1071 samples queried. 4/12/2017 3:18:37 PM -- C:\Program Files\Exchange Jetstress\My_TEST\Soft_Recovery\Performance_2017_4_12_10_49_3.html was saved. 4/13/2017 8:23:21 AM -- Performance logging started (interval: 4000 ms). 4/13/2017 8:23:21 AM -- Recovering databases... 4/13/2017 8:43:06 AM -- Performance logging has ended. 4/13/2017 8:43:06 AM -- Instance ( ), Instance ( ), Instance ( ), Instance ( ), Instance ( ), Instance ( ), Instance ( ), Instance ( ), Instance ( ), Instance ( ), Instance ( ) and Instance ( ) 4/13/2017 8:43:08 AM -- C:\Program Files\Exchange Jetstress\My_TEST\Soft_Recovery\SoftRecovery_2017_4_13_8_23_15.blg has 293 samples. 4/13/2017 8:43:08 AM -- Creating test report...