Nimble Storage Exchange ,000-Mailbox Resiliency Storage Solution

Transcription

1 Nimble Stor Exchan 213 1,-Mailbox Reilie Stor Solution Teted with: ESRP Stor Verion. Tet date: May 2, 21 Overview Thi document provide information on Nimble Stor' iscsi tor olution for Microoft Exchan Server, baed on the Microoft Exchan Solution Reviewed Program (ESRP) Stor program*. For any quetion or comment regarding the content of thi document, ee Contact for additional information. *The ESRP Stor program wa developed by Microoft Corporation to provide a common tor teting framework for vendor to provide information on it tor olution for Microoft Exchan Server oftware. For more detail on the Microoft ESRP Stor program, pleae viit: Diclaimer Thi document ha been produced independently of Microoft Corporation. Microoft Corporation exprely diclaim reponibility for, and make no warranty, expre or implied, with repect to, the accuracy of the content of thi document. The information contained in thi document repreent the current view of Nimble Stor on the iue dicued a of the date of publication. Due to changing market condition, it hould not be interpreted to be a commitment on the part of Nimble Stor, and Nimble Stor cannot guarantee the accuracy of any information preented after the date of publication. Feature Thi document decribe the teting of a 1, mailbox reilie (2-copy) databae availability group (DAG) configuration for Exchan Server 213 with a Nimble Stor CS7 tor ytem. Nimble Stor ha developed an entirely new approach to data tor that conver primary and backup tor into one array, dramatically cutting cot and complexity. N I M B L E S T O R A G E : E X C H A N G E S T O R A G E S O L U T I O N 1

2 About Nimble Stor Nimble Stor think that enterprie houldn t compromie on performance, capacity, eae of ue, or price. Nimble Stor olution eamlely cale to enterprie-cla performance and capacity, and offer enhanced backup and diater recovery for tre-free operation and lower TCO. Nimble Adaptive Flah platform deliver adjutable performance to meet the fluctuating need of today enterprie application. Nimble Stor enjoy olid partnerhip with indutry leader like VMware, Microoft, Cico, Citrix, Oracle and CommVault. To learn more about Nimble Stor and Adaptive Flah, viit and follow u on The Nimble Stor Adaptive Flah Platform Eliminate performance and capacity trade-off The peed of flah technology ha made it an eential component of the modern datacenter. But, flah performance uperiority come at a teep price, making it impractical for all but a handful of today enterprie application. Thi force buinee to erect infratructure ilo, reulting in complexity and prawl, to meet their baic performance and capacity requirement. Nimble Stor Adaptive Flah Platform eliminate thi trade-off delivering performance and capacity in the mot efficient way poible. ADAPTIVE FLASH Adaptive Flah allow the dynamic and intellint allocation of tor reource to atify divere and trinnt application demand. Adaptive Flah i baed on CASL, Nimble Stor patented Cache- Accelerated Sequential Layout architecture, and InfoSight, the company automated cloud-baed manment and upport ytem. CASL allow performance and capacity to be caled eamlely and independently to accommodate datacenter growth. InfoSight enure flah will be deployed intellintly to atify the fluctuating requirement of enterprie application, eliminating the wateful overproviioning of tor reource. Adaptive Flah intantly adjut to atify performance-hungry application. Adaptive Flah can: Eliminate tor ilo needed for varying application demand. Do away with diruptive forklift upgrade. Comprehenively protect valuable IT aet. Keep tor infratructure running at peak health with powerful, proactive analytic. N I M B L E S T O R A G E : E X C H A N G E S T O R A G E S O L U T I O N 2

3 Adaptive Flah cutomer realize dramatic benefit, including: An up to 1x reduction in data center footprint, a well a lower power and cooling requirement. A 5x improvement in price/performance veru other traditional or hybrid olution. A 5x increae in application protection compared to the indutry aver. A greater than five-nine level of ytem availability. Solution Decription The following ection outline the Exchan 213 mailbox reilie olution that Nimble Stor implemented to run the ESRP tet. Stor: Nimble Stor CS7 array Dual Stor Controller () 1 Gbp Ethernet port per controller with Jumbo Frame Nimble Operating Sytem TB of Effective Stor Capacity * 8.2 TB of Effective Flah Cache * Link to CS7 Window Server Catalog liting: c23e59a&bCatID=1282 Nimble Stor ES1-AFS (All Flah Expanion Shelf): 16.5 TB of Uable Flah Cache * Nimble Stor ES1-H65 (Capacity Expanion Shelf): 79 TB of Effective Stor Capacity * * Baed on Exchan 213 cutomer aver compreion ratio. N I M B L E S T O R A G E : E X C H A N G E S T O R A G E S O L U T I O N 3

4 (1) Production Virtual Server Window Server 212 R2 Exchan 213 Mailbox Server Role (1) Phyical Server Window Server 212 R2 Hyper-V (1) DAG Virtual Server Window Server 212 R2 Exchan 213 Mailbox Server Role (1) Phyical Server Window Server 212 R2 Hyper-V iscsi Switch Fabric 1 iscsi Switch Fabric 2 Mktg1 (5 ae and 5 ) Mktg2 (DAG Copy) Nimble Stor CS-7 ES1-AFS ES1-H65 Nimble Stor CS-7 ES1-AFS ES1-H65 The primary copy tor i decribed in thi document. The econdary copy tor i configured identically (from the hot on down to the pindle including brand, model, firmware, driver, etc.). The Exchan DAG tor wa configured a follow: 1 Active Mailbox Server and 1 Paive Mailbox Server. 2 Nimble Stor CS7 Array, each with an ES1-AFS and ES1-H65 expanion helf. 5 Active ae, 2, mailboxe per databae. Nimble Stor array ue triple-parity to protect againt drive failure. The Nimble Stor CASL file ytem ue a block checkum to enure data integrity. 2 copie of each databae. N I M B L E S T O R A G E : E X C H A N G E S T O R A G E S O L U T I O N

5 The ESRP-Stor program focue on tor olution teting to addre performance and reliability iue with tor deign. However, tor i not the only factor to take into conideration when deigning a cale up Exchan olution. Other factor which affect the erver calability are: erver proceor utilization, erver phyical and virtual memory limitation, reource requirement for other application, directory and network ervice latencie, network infratructure limitation, replication and recovery requirement, and client u profile. All thee factor are beyond the cope for ESRP- Stor. Therefore, the number of mailboxe hoted per erver a part of the teted configuration may not necearily be viable for ome cutomer deployment. For more information on identifying and addreing performance bottleneck in an Exchan ytem, pleae refer to Microoft' Troublehooting Microoft Exchan Server Performance, available at Tarted Cutomer Profile The Nimble Stor olution for a mid to lar-ized Enterprie Exchan environment i deigned to upport: 1, Mailboxe 2 Server (1 Active, 1 Paive).11 IOPS / Mailbox (.526 IOPS / Mailbox achieved for 8% headroom) 1, MB per mailbox 2 x 7 background databae maintenance enabled Providing controller capacity for replication and dik recontruction Permitting pace for backup and retore uing Nimble Stor Snaphot Backup technology Mailbox Reilie (2-Copy) N I M B L E S T O R A G E : E X C H A N G E S T O R A G E S O L U T I O N 5

6 Teted Deployment The following table ummarize the teting environment: Simulated Exchan Configuration: Number of Exchan mailboxe imulated 1, Number of ae Availability Group (DAG) 2 Number of erver/dag 1 Number of active mailboxe/erver 1, Number of databae/hot 5 (5 Total) Number of copie/databae 2 Number of mailboxe/databae 2, Simulated profile: per econd per mailbox (IOPS, include at leat 2% headroom).11 IOPS / Mailbox (.526 IOPS / Mailbox achieved for 8% headroom) ae LUN ize 2.8 TB LUN ize 25 GB Total databae ize for performance teting 1 TB % tor capacity ued by Exchan 9% databae** **Stor performance characteritic chan baed on the percent utilization of the individual dik. Tet that ue a mall percent of the tor (~25%) may exhibit reduced throughput if the tor capacity utilization i ignificantly increaed beyond what i teted in thi paper. Stor Hardware Stor Connectivity (Fiber Channel, SAS, SATA, iscsi SAN iscsi) Stor model and OS/firmware reviion CS7 Nimble OS Stor cache GB NVDIMM Cache (), plu 8 GB RAM Cache, plu 3.2 TB Flah Cache () Number of tor controller 2 Number of tor port () 1 Gbp Ethernet per Controller Maximum bandwidth of tor connectivity to Gbp hot Switch type/model/firmware reviion Extreme Summit X67-8x-FB 1 Gigabit Ethernet Switch HBA model and firmware Silicom PE21G2SPI9-XR v:1. Jumbo Frame enabled Number of HBA /hot 2 Total number of dik teted in olution 12 HDD and Flah SSD Cache drive per array 8 Flah SSD Cache drive in AFS 15 HDD and 1 Flah Cache drive per Maximum number of pindle can be hoted in the tor helf 8 HDD and 1 Flah SSD Cache drive per tor cluter N I M B L E S T O R A G E : E X C H A N G E S T O R A G E S O L U T I O N 6

7 Stor Software HBA driver Intel 1 Gbp PCIe v HBA QueueTart Setting N/A HBA QueueDepth Setting 512 Multi-Pathing Nimble Operating Sytem 2.1.2, Window MPIO Hot OS Window 212 R2 HyperV Guet OS Window 212 R2 ESE.dll file verion Replication olution name/verion N/A for Exchan 213 DAG Solution Stor Dik Configuration (Mailbox Store/ Dik) Dik type, peed and firmware reviion SAS and SATA 7,2 RPM SATA Flah SSD Cache Raw capacity per dik (GB) HDD: 3 TB Flah SSD Cache: 8 GB Number of phyical dik in tet HDD: 27 Flah SSD Cache: 13 Total raw tor capacity (GB) HDD: 81 TB Flah SSD Cache: 1. TB Nimble native 61.2% compreion Exchan 213 data HDD: 139 TB effective Flah Cache: 2.7 TB effective Dik lice ize (GB) N/A Number of lice per LUN or number of dik per 27 Dik for both databae and log file LUN Raid level RAID 6 *** Total formatted capacity 112 TB Stor capacity utilization**** 138% (Formatted Capacity / Raw Capacity) 8.5% (Formatted Capacity / Effective Capacity) ae capacity utilization**** 128% (ae & Size / Raw Capacity) 7.8% (ae & Size / Effective Capacity) ***Nimble' CASL file ytem ue a performance optimized RAID6 cheme that greatly reduce the rebuild time of traditional RAID6 implementation. CASL intellintly decide which drive ector to rebuild (for example only populated data block are rebuilt and not empty drive pace). A a reult a lightly loaded array can rebuild a whole 1TB drive in about hour, and a 2TB drive in about 7 hour. If the drive i not full the rebuild time would be proportionally horter. So a half full drive 2TB drive would only take 3.5 hour to rebuild on a lightly loaded ytem. When the tor array i very buy, rebuild time can take lonr to reduce performance late for active application. **** Nimble Stor array ue real-time compreion algorithm that provide 61.2% aver capacity aving over raw dik ize for Exchan 213 databae. Thu, uable capacity i larr than the raw capacity of the tor and repreent a more realitic expectation for izing than raw capacity. Thee compreion metric are collected acro Nimble Stor cutomer bae that ue Exchan 213. N I M B L E S T O R A G E : E X C H A N G E S T O R A G E S O L U T I O N 7

8 Bet Practice Exchan erver i a dik-intenive application. Baed on the teting run uing the ESRP framework, we would recommend the following to improve the tor performance. For Exchan 213 bet practice on tor deign, pleae viit Nimble Stor provide an auto-tuning tor olution that lever flah cache and greatly reduce the amount of effort to ize and layout Exchan mailtore. Core Stor 1. Thi olution architecture wa deigned to how the maximum Exchan performance capability of a Nimble Stor array. Environment maller than 1, mailboxe routinely hare Nimble Stor array with other application uch a SQL Server and SharePoint. 2. Separate Exchan ae and volume ince they have different performance characteritic and will tune differently. Ue the Nimble OS performance policie for Exchan ae and Exchan when creating the repective volume. 3. Nimble Stor array automatically proviion tor from a pool of high-denity dik protected by triple-parity and are intellintly accelerated uing NVDIMMM, DRAM and Flah SSD Cache. Nimble' CASL File Sytem lever thee tor technologie natively to automatically provide performance dramatically higher than traditional tiered tor architecture. Therefore, you do not need to pend extenive time proviioning tor uch that legacy tor architecture require. Nimble doe thi phyical proviioning automatically for you to enure both maximum performance and maximum capacity at the ame time. Pleae contact Nimble Stor for further detail on our ground breaking CASL file ytem.. Pleae conult the "Nimble Stor Bet Practice Guide for Exchan" for current implementation bet practice. Backup trategy Nimble Stor provide the firt converd tor platform that combine primary tor and backup tor in the ame architecture. Virtually all enterprie tor ytem provide the ability to take naphot, or point-in-time copie of data. Snaphot provide a very fat and efficient way to recover from uer error and application crahe. However, enterprie are uually limited to keeping at mot a few day worth of naphot on dik, becaue toring multiple naphot can conume lar amount of expenive and limited primary tor capacity. Thi mandate backing up primary data to a eparate dik-baed backup ytem frequently in order to tore 6-9 day worth of backup. CASL enable intant, application-conitent backup on the ame array with very efficient backup capacity optimization. It capture compreed, incremental naphot of the primary data on low-cot drive at pre-configured interval. Thee backup are both extremely fat (on the order of milliecond) N I M B L E S T O R A G E : E X C H A N G E S T O R A G E S O L U T I O N 8

9 and non-diruptive, becaue they do not impact application or tor performance. It therefore become feaible for enterprie to capture frequent backup paced jut minute apart (intead of the typical daily backup), enabling much finer recovery point objective (RPO) and improving data protection. The Nimble approach ignificantly reduce cot by eliminating the need for a eparate backup tier. It alo eliminate the complexity and adminitrative overhead of managing maive data copie between tier. Finally, it enable much fater retore, with recovery time objective (RTO) meaured in econd intead of hour in the event of application corruption or uer error, further improving application availability. Contact for additional information Nimble Stor, Inc. 211 River Oak Parkway San Joe, CA 9513 Main: Support: 877-3NIMBLE ( ) info@nimbletor.com Sale To learn more about Nimble Stor breakthrough technology or to chedule a briefing, pleae contact our technical ale team: Sale: 877-3NIMBLE ( ) ale@nimbletor.com N I M B L E S T O R A G E : E X C H A N G E S T O R A G E S O L U T I O N 9

10 Tet Reult Summary Thi ection provide a high level ummary of the tet data from ESRP and the link to the detailed html report which are nerated by ESRP teting framework. Pleae click on the underlined heading below to view the html report for each tet. Reliability A number of tet in the framework are to check Reliability tet run for 2 hour. The goal i to verify the tor can handle high IO load for a long period of time. Both log and databae file will be analyzed for integrity after the tre tet to enure no databae/log corruption. The following lit provide an overview: (click on the underlined word will how the html report after the reliability tet run) There were no error reported in any of the Event collected for the reliability tet. There were no error reported during the databae and log checkum proce. Stor Performance Reult The Primary Stor performance teting i deigned to exercie the tor with maximum utainable Exchan type of IO for 2 hour. The tet i to how how long it take for the tor to repond to an IO under load. The data below i the um of all of the logical dik and aver of all the logical dik late in the 2 hour tet duration. Each erver i lited eparately and the aggregate number acro all erver i lited a well. N I M B L E S T O R A G E : E X C H A N G E S T O R A G E S O L U T I O N 1

11 Individual Server Metric: The um of acro Stor Group and the aver late acro all Stor Group on a per erver bai. Hot 1 ae ae Dik Tranfer/ec, ae Dik /ec 3, ae Dik /ec 1, ae Dik (m) ae Dik (m) Tranaction Dik /ec 66.8 Dik (m) Hot 2 ae ae Dik Tranfer/ec, ae Dik /ec ae Dik /ec ae Dik (m) ae Dik (m) Tranaction Dik /ec Dik (m) Hot 3 ae ae Dik Tranfer/ec, ae Dik /ec 3,28.58 ae Dik /ec 1, ae Dik (m) 2.86 ae Dik (m) Tranaction Dik /ec Dik (m) Hot ae ae Dik Tranfer/ec,52.12 ae Dik /ec 3,3.73 ae Dik /ec 1,58.8 ae Dik (m) ae Dik (m) Tranaction Dik /ec Dik (m) N I M B L E S T O R A G E : E X C H A N G E S T O R A G E S O L U T I O N 11

12 Hot 5 ae ae Dik Tranfer/ec, ae Dik /ec 3, ae Dik /ec 1,6.71 ae Dik (m) ae Dik (m).666 Tranaction Dik /ec Dik (m) 1.36 Hot 6 ae ae Dik Tranfer/ec,98.52 ae Dik /ec 3,3.58 ae Dik /ec 1,6.62 ae Dik (m) ae Dik (m) Tranaction Dik /ec Dik (m) 1.28 Hot 7 ae ae Dik Tranfer/ec,56.53 ae Dik /ec 3,82.72 ae Dik /ec 1,77.81 ae Dik (m) 2.75 ae Dik (m) Tranaction Dik /ec Dik (m) 1.36 Hot 8 ae ae Dik Tranfer/ec, ae Dik /ec 3, ae Dik /ec 1,63.55 ae Dik (m) ae Dik (m) 2.62 Tranaction Dik /ec Dik (m) N I M B L E S T O R A G E : E X C H A N G E S T O R A G E S O L U T I O N 12

13 Hot 9 ae ae Dik Tranfer/ec, ae Dik /ec 3, ae Dik /ec 1,8.969 ae Dik (m) ae Dik (m).12 Tranaction Dik /ec Dik (m) Hot 1 ae ae Dik Tranfer/ec,93.53 ae Dik /ec ae Dik /ec ae Dik (m) ae Dik (m) Tranaction Dik /ec Dik (m) Aggregate Performance acro all erver Metric: The um of acro erver in olution and the aver late acro all erver in olution. ae ae Dik Tranfer/ec 6, ae Dik /ec 31, ae Dik /ec 15,19.38 ae Dik (m) ae Dik (m) Tranaction Dik /ec 6, Dik (m) ae Backup/Recovery Performance There are two tet report in thi ection. The firt one i to meaure the equential read rate of the databae file, and the econd i to meaure the recovery/replay performance (playing tranaction log in to the databae). ae -only Performance The tet i to meaure the maximum rate at which databae could be backed up via VSS. The following table how the aver rate for a ingle databae file. N I M B L E S T O R A G E : E X C H A N G E S T O R A G E S O L U T I O N 13

14 Hot 1 MB read/ec per databae 9.98 MB read/ec total per erver Hot 2 MB read/ec per databae MB read/ec total per erver Hot 3 MB read/ec per databae MB read/ec total per erver Hot MB read/ec per databae 9.92 MB read/ec total per erver Hot 5 MB read/ec per databae 9.69 MB read/ec total per erver 28.5 Hot 6 MB read/ec per databae 3.1 MB read/ec total per erver Hot 7 MB read/ec per databae MB read/ec total per erver Hot 8 MB read/ec per databae MB read/ec total per erver Hot 9 MB read/ec per databae 53.2 MB read/ec total per erver Hot 1 MB read/ec per databae 51.3 MB read/ec total per erver N I M B L E S T O R A G E : E X C H A N G E S T O R A G E S O L U T I O N 1

15 Tranaction Recovery/Replay Performance The tet i to meaure the maximum rate at which the log file can be played againt the databae. The following table how the aver rate for 5 log file played in a ingle tor group. Each log file i 1 MB in ize. Hot 1 time to play one file (e.687 Hot 2 time to play one file (e.657 Hot 3 time to play one file (e.6 Hot time to play one file (e.67 Hot 5 time to play one file (e.67 Hot 6 time to play one file (e.77 Hot 7 time to play one file (e.72 Hot 8 time to play one file (e.715 Hot 9 time to play one file (e.682 Hot 1 time to play one file (e.711 N I M B L E S T O R A G E : E X C H A N G E S T O R A G E S O L U T I O N 15

16 Concluion Thi report demontrate Nimble Stor' ability to eaily meet the performance need of a 1, mailbox Exchan 213 implementation for 15 aver me per mailbox per day (.11 IOPS) and 1,2 MB per mailbox. The CS7 platform can cale to greater mailbox denity uing additional flah SSD caching drive and expanion helve. Nimble' CASL file ytem provide adaptive flah technology by combining high-denity tor with flah SSD to enable groundbreaking performance within a mall rack form factor. The Nimble Stor architecture alo provide additional pace for highly-efficient redirect on write naphot to provide fat full backup of Exchan uing Microoft VSS and Nimble Protection Manr. Thi document i developed by Nimble Stor, and reviewed by Microoft Exchan Product team. The tet reult/data preented in thi document i baed on the tet introduced in the ESRP tet framework. Cutomer hould not quote the data directly for hi/her pre-deployment verification. It i till neceary to go through the exercie to validate the tor deign for a pecific cutomer environment. ESRP program i not deigned to be a benchmarking program; tet are not deigned to tting the maximum throughput for a giving olution. Rather, it i focued on producing recommendation from vendor for Exchan application. So the data preented in thi document hould not be ued for direct comparion among the olution. Nimble Stor provide complete izing information for Exchan Server deployment through it ytem engineer. Contact your local Nimble Stor ale office for additional information. N I M B L E S T O R A G E : E X C H A N G E S T O R A G E S O L U T I O N 16

17 Appendix A - Tet Reult Thi ection provide repreentative tet reult from one of the ten Exchan erver under tet: Hot 1 (ESRP). It i alo repreentative of each erver' tet reult, which are virtually identical. 2-Hour Stre Tet Reult Microoft Exchan Jettre 213 Stre Tet Reult Report Tet Summary Overall Tet Reult Machine Name Tet Decription Tet Start Time Tet End Time Pa NS-ESRP1 5/16/21 11:53:57 PM 5/18/21 12:7:18 AM Collection Start Time 5/16/21 11:5:2 PM Collection End Time 5/17/21 11:5:29 PM Jettre Verion ESE Verion Operating Sytem Window Server 212 R2 Standard ( ) Performance C:\Uer\Adminitrator\Document\Stre_21_5_16_23_5_8.blg ae Sizing and Throughput Achieved Tranactional per Second Tart Tranactional per Second 11 Initial ae Size (byte) Final ae Size (byte) ae File (Count) 5 Jettre Sytem Parameter Thread Count 16 Minimum ae Cache Maximum ae Cache Inert Operation % Delete Operation 2% Replace Operation 5% Operation 35% Lazy Commit 7% Run Background ae Maintenance True Number of Copie per ae 2 ae Configuration Intance path: F:\ 16. MB 128. MB N I M B L E S T O R A G E : E X C H A N G E S T O R A G E S O L U T I O N 17

18 ae: E:\Jettre11.edb Intance path: H:\ ae: G:\Jettre21.edb Intance path: J:\ ae: I:\Jettre31.edb Intance2176. path: L:\ ae: K:\Jettre1.edb Intance path: N:\ ae: M:\Jettre51.edb Tranactional Performance MSExcha n ae ==> Intance Intance Intance Intance Intance Intance bae a n cy (me bae a n cy (me ae /ec ae /ec ae a Byte ae a Byte (me..... Writ e /ec (me /ec Byte..... a Byte Background ae Maintenance Performance MSExchan ae ==> Intance ae Maintenance IO /ec Intance Intance Intance Intance Intance ae Maintenance IO Byte Replication Performance MSExchan ae ==> Intance /ec Byte Intance N I M B L E S T O R A G E : E X C H A N G E S T O R A G E S O L U T I O N 18

19 Intance Intance Intance Intance Total Performance MSExcha n ae ==> Intance Intance Intance Intance Intance Intance bae n cy (me bae n cy (me ae /ec ae /ec ae a Byte ae a Byte Rea d (m e Writ e (m e /ec /ec ag e Byte a Byte Hot Sytem Performance Counter Minimum Maximum % Proceor Time Available MByte Free Sytem P Table Entrie Tranition P RePurpoed/ec Pool Nonpd Byte Pool Pd Byte ae P Fault Stall/ec... Tet 5/16/21 11:53:57 PM -- Preparing for teting... 5/16/21 11:5:3 PM -- Attaching databae... 5/16/21 11:5:3 PM -- Preparation for teting are complete. 5/16/21 11:5:3 PM -- Starting tranaction dipatch.. 5/16/21 11:5:3 PM -- ae cache etting: (minimum: 16. MB, maximum: 1.2 GB) 5/16/21 11:5:3 PM -- ae fluh threhold: (tart: 12.8 MB, top: 25.6 MB) 5/16/21 11:5:8 PM -- ae read late threhold: (aver: 2 mec/read, maximum: 2 mec/read). 5/16/21 11:5:8 PM -- write late threhold: (aver: 1 mec/write, maximum: 2 mec/write). 5/16/21 11:5:1 PM -- Operation mix: Seion 16, Inert %, Delete 2%, Replace 5%, 35%, Lazy Commit 7%. 5/16/21 11:5:1 PM -- Performance logging tarted (interval: 15 m). N I M B L E S T O R A G E : E X C H A N G E S T O R A G E S O L U T I O N 19

20 5/16/21 11:5:1 PM -- Attaining prerequiite: 5/16/21 11:5:2 PM -- \MSExchan ae(jettrewin)\ae Cache Size, Lat: (lower bound: , upper bound: none) 5/17/21 11:5:3 PM -- Performance logging ha ended. 5/18/21 12:7:15 AM -- JetInterop batch tranaction tat: , , , and /18/21 12:7:15 AM -- Dipatching tranaction end. 5/18/21 12:7:15 AM -- Shutting down databae... 5/18/21 12:7:18 AM -- Intance (complete), Intance (complete), Intance (complete), Intance2176. (complete) and Intance (complete) 5/18/21 12:7:18 AM -- C:\Uer\Adminitrator\Document\Stre_21_5_16_23_5_8.blg ha 575 ample. 5/18/21 12:7:18 AM -- Creating tet report... 5/18/21 12:7: AM -- Intance ha 2.9 for ae. 5/18/21 12:7: AM -- Intance ha 1. for. 5/18/21 12:7: AM -- Intance ha 1. for. 5/18/21 12:7: AM -- Intance ha 2.5 for ae. 5/18/21 12:7: AM -- Intance ha 1. for. 5/18/21 12:7: AM -- Intance ha 1. for. 5/18/21 12:7: AM -- Intance ha 2.5 for ae. 5/18/21 12:7: AM -- Intance ha 1. for. 5/18/21 12:7: AM -- Intance ha 1. for. 5/18/21 12:7: AM -- Intance2176. ha 2.5 for ae. 5/18/21 12:7: AM -- Intance2176. ha 1.3 for. 5/18/21 12:7: AM -- Intance2176. ha 1.3 for. 5/18/21 12:7: AM -- Intance ha 2.6 for ae. 5/18/21 12:7: AM -- Intance ha 1.3 for. 5/18/21 12:7: AM -- Intance ha 1.3 for. 5/18/21 12:7: AM -- Tet ha Maximum ae P Fault Stall/ec. 5/18/21 12:7: AM -- The tet ha ae P Fault Stall/ec ample higher than. 5/18/21 12:7: AM -- C:\Uer\Adminitrator\Document\Stre_21_5_16_23_5_8.xml ha 572 ample queried. N I M B L E S T O R A G E : E X C H A N G E S T O R A G E S O L U T I O N 2

21 2-Hour Stre Tet Reult Microoft Exchan Jettre 213 Performance Tet Reult Report Tet Summary Overall Tet Reult Pa Machine Name NS-ESRP1 Tet Decription Tet Start Time 5/8/21 12::28 PM Tet End Time 5/8/21 3:8:36 PM Collection Start Time Collection End Time Jettre Verion 5/8/21 12:5:26 PM 5/8/21 2:5:25 PM ESE Verion Operating Sytem Performance Window Server 212 R2 Standard ( ) C:\Uer\Adminitrator\Document\Performance_21_5_8_12 39.blg ae Sizing and Throughput Achieved Tranactional per Second Tart Tranactional per Second 11 Initial ae Size (byte) Final ae Size (byte) ae File (Count) 5 Jettre Sytem Parameter Thread Count 16 Minimum ae Cache Maximum ae Cache Inert Operation % Delete Operation 2% Replace Operation 5% Operation 35% Lazy Commit 7% Run Background ae Maintenance True Number of Copie per ae MB 128. MB ae Configuration Intance72.1 path: F:\ ae: E:\Jettre11.edb N I M B L E S T O R A G E : E X C H A N G E S T O R A G E S O L U T I O N 21

22 Intance72.2 path: H:\ ae: G:\Jettre21.edb Intance72.3 path: J:\ ae: I:\Jettre31.edb Intance72. path: L:\ ae: K:\Jettre1.edb Intance72.5 path: N:\ ae: M:\Jettre51.edb Tranactional Performance MSExcha n a e ==> Intance Intance 72.1 Intance 72.2 Intance 72.3 Intance 72. Intance 72.5 bae a n cy (me bae a n cy (me ae /ec ae /ec ae a Byte ae a Byte Background ae Maintenance Performance MSExchan ae ==> Intance (me..... ae Maintenance IO /ec Writ e /ec (me /ec Intance Intance Intance Intance Intance Byte..... ae Maintenance IO Byte a Byte Replication Performance MSExchan ae ==> Intance /ec Byte Intance Intance Intance N I M B L E S T O R A G E : E X C H A N G E S T O R A G E S O L U T I O N 22

23 Intance Intance Total Performance MSExch an a e ==> Intance Intance 72.1 Intance 72.2 Intance 72.3 Intance 72. Intance 72.5 bae n cy (me bae n cy (me ae /ec ae /ec ae a Byte ae a Byte Rea d (m e Writ e (m e /ec /ec ag e Byte Hot Sytem Performance Counter Minimum Maximum % Proceor Time Available MByte a Byte Free Sytem P Table Entrie Tranition P RePurpoed/ec... Pool Nonpd Byte Pool Pd Byte ae P Fault Stall/ec... Tet 5/8/21 12::28 PM -- Preparing for teting... 5/8/21 12::3 PM -- Attaching databae... 5/8/21 12::3 PM -- Preparation for teting are complete. 5/8/21 12::3 PM -- Starting tranaction dipatch.. 5/8/21 12::3 PM -- ae cache etting: (minimum: 16. MB, maximum: 1.2 GB) 5/8/21 12::3 PM -- ae fluh threhold: (tart: 12.8 MB, top: 25.6 MB) 5/8/21 12::39 PM -- ae read late threhold: (aver: 2 mec/read, maximum: 1 mec/read). 5/8/21 12::39 PM -- write late threhold: (aver: 1 mec/write, maximum: 1 mec/write). 5/8/21 12::1 PM -- Operation mix: Seion 16, Inert %, Delete 2%, Replace 5%, 35%, Lazy Commit 7%. 5/8/21 12::1 PM -- Performance logging tarted (interval: 15 m). 5/8/21 12::1 PM -- Attaining prerequiite: 5/8/21 12:5:26 PM -- \MSExchan ae(jettrewin)\ae Cache Size, Lat: (lower bound: , upper bound: none) N I M B L E S T O R A G E : E X C H A N G E S T O R A G E S O L U T I O N 23

24 5/8/21 2:5:27 PM -- Performance logging ha ended. 5/8/21 3:8:3 PM -- JetInterop batch tranaction tat: , , , and /8/21 3:8:3 PM -- Dipatching tranaction end. 5/8/21 3:8:3 PM -- Shutting down databae... 5/8/21 3:8:36 PM -- Intance72.1 (complete), Intance72.2 (complete), Intance72.3 (complete), Intance72. (complete) and Intance72.5 (complete) 5/8/21 3:8:36 PM -- C:\Uer\Adminitrator\Document\Performance_21_5_8_12 39.blg ha 82 ample. 5/8/21 3:8:36 PM -- Creating tet report... 5/8/21 3:8:38 PM -- Intance72.1 ha 2. for ae. 5/8/21 3:8:38 PM -- Intance72.1 ha 1.2 for. 5/8/21 3:8:38 PM -- Intance72.1 ha 1.2 for. 5/8/21 3:8:38 PM -- Intance72.2 ha 2. for ae. 5/8/21 3:8:38 PM -- Intance72.2 ha 1.2 for. 5/8/21 3:8:38 PM -- Intance72.2 ha 1.2 for. 5/8/21 3:8:38 PM -- Intance72.3 ha 2. for ae. 5/8/21 3:8:38 PM -- Intance72.3 ha 1.2 for. 5/8/21 3:8:38 PM -- Intance72.3 ha 1.2 for. 5/8/21 3:8:38 PM -- Intance72. ha 2. for ae. 5/8/21 3:8:38 PM -- Intance72. ha 1.2 for. 5/8/21 3:8:38 PM -- Intance72. ha 1.2 for. 5/8/21 3:8:38 PM -- Intance72.5 ha 2. for ae. 5/8/21 3:8:38 PM -- Intance72.5 ha 1.2 for. 5/8/21 3:8:38 PM -- Intance72.5 ha 1.2 for. 5/8/21 3:8:38 PM -- Tet ha Maximum ae P Fault Stall/ec. 5/8/21 3:8:38 PM -- The tet ha ae P Fault Stall/ec ample higher than. 5/8/21 3:8:38 PM -- C:\Uer\Adminitrator\Document\Performance_21_5_8_12 39.xml ha 79 ample queried. ae Backup Tet Reult Microoft Exchan Jettre 213 ae backup Tet Reult Report ae Backup Statitic - All ae Intance ae Size (MByte) Elaped Backup Time Intance :3: Intance :29: Intance :28: Intance :26: Intance :27:38 5. Avg 9.98 Sum Jettre Sytem Parameter Thread Count 16 MByte Tranferred/ec N I M B L E S T O R A G E : E X C H A N G E S T O R A G E S O L U T I O N 2

25 Minimum ae Cache 16. MB Maximum ae Cache 128. MB Inert Operation % Delete Operation 2% Replace Operation 5% Operation 35% Lazy Commit 7% ae Configuration Intance path: F:\ ae: E:\Jettre11.edb Intance path: H:\ ae: G:\Jettre21.edb Intance path: J:\ ae: I:\Jettre31.edb Intance2176. path: L:\ ae: K:\Jettre1.edb Intance path: N:\ ae: M:\Jettre51.edb Tranactional Performance MSExcha n ae ==> Intance Intance Intance Intance Intance Intance bae a n cy (me bae a n cy (me ae /ec ae /ec a e ag e Byte bae a Byte (me Writ e /ec (me..... /ec Byte Hot Sytem Performance Counter Minimum Maximum % Proceor Time Writ e Byte..... N I M B L E S T O R A G E : E X C H A N G E S T O R A G E S O L U T I O N 25

26 Available MByte Free Sytem P Table Entrie Tranition P RePurpoed/ec Pool Nonpd Byte Pool Pd Byte ae P Fault Stall/ec... Tet 5/18/21 2::2 PM -- Preparing for teting... 5/18/21 2::7 PM -- Attaching databae... 5/18/21 2::7 PM -- Preparation for teting are complete. 5/18/21 2::5 PM -- Performance logging tarted (interval: 3 m). 5/18/21 2::5 PM -- Backing up databae... 5/19/21 1:31:3 AM -- Performance logging ha ended. 5/19/21 1:31:3 AM -- Intance (1% proceed), Intance (1% proceed), Intance (1% proceed), Intance2176. (1% proceed) and Intance (1% proceed) 5/19/21 1:31:3 AM -- C:\Uer\Adminitrator\Document\aeBackup_21_5_18_1 7.blg ha 1379 ample. 5/19/21 1:31:3 AM -- Creating tet report... Soft Recovery Tet Reult Microoft Exchan Jettre 213 SoftRecovery Tet Reult Report Soft-Recovery Statitic - All ae Intance file replayed Elaped econd Intance Intance Intance Intance Intance Avg Sum ae Configuration Intance path: F:\ ae: E:\Jettre11.edb Intance path: H:\ ae: G:\Jettre21.edb Intance path: J:\ N I M B L E S T O R A G E : E X C H A N G E S T O R A G E S O L U T I O N 26

27 ae: I:\Jettre31.edb Intance2176. path: L:\ ae: K:\Jettre1.edb Intance path: N:\ ae: M:\Jettre51.edb Tranactional Performance MSExch an a e ==> Intanc e Intanc e Intanc e Intanc e Intanc e2176. Intanc e bae (me bae Writ e (me bae /ec bae /ec ae a Byte ae a Byte Rea d Ave r (m e Writ e /ec Ave r (m e /ec..... a Byte Writ e Ave r Byt e..... Background ae Maintenance Performance MSExchan ae ==> Intance ae Maintenance IO /ec Intance Intance Intance Intance Intance ae Maintenance IO Byte Total Performance MSExcha n ae ==> Intance bae n cy bae n cy ae /ec ae /ec ae a Byte ae a Byte Rea d (m Writ e (m /ec /ec ag e Byte Writ e Byte N I M B L E S T O R A G E : E X C H A N G E S T O R A G E S O L U T I O N 27

28 Intance Intance (me (me e e Intance Intance Intance Hot Sytem Performance Counter Minimum Maximum % Proceor Time Available MByte Free Sytem P Table Entrie Tranition P RePurpoed/ec Pool Nonpd Byte Pool Pd Byte ae P Fault Stall/ec... Tet 5/19/21 12:2:27 PM -- Preparing for teting... 5/19/21 12:2:33 PM -- Attaching databae... 5/19/21 12:2:33 PM -- Preparation for teting are complete. 5/19/21 12:2:33 PM -- Starting tranaction dipatch.. 5/19/21 12:2:33 PM -- ae cache etting: (minimum: 16. MB, maximum: 1.2 GB) 5/19/21 12:2:33 PM -- ae fluh threhold: (tart: 12.8 MB, top: 25.6 MB) 5/19/21 12:2:38 PM -- ae read late threhold: (aver: 2 mec/read, maximum: 1 mec/read). 5/19/21 12:2:38 PM -- write late threhold: (aver: 1 mec/write, maximum: 1 mec/write). 5/19/21 12:2:39 PM -- Operation mix: Seion 16, Inert %, Delete 2%, Replace 5%, 35%, Lazy Commit 7%. 5/19/21 12:2:39 PM -- Performance logging tarted (interval: 15 m). 5/19/21 12:2:39 PM -- Generating log file... 5/19/21 12:26:33 PM -- F:\ (1.% nerated), H:\ (11.% nerated), J:\ (1.2% nerated), L:\ (11.% nerated) and N:\ (12.2% nerated) 5/19/21 12:26:3 PM -- Performance logging ha ended. 5/19/21 12:26:3 PM -- JetInterop batch tranaction tat: 21777, 21777, 21777, and /19/21 12:26:3 PM -- Dipatching tranaction end. 5/19/21 12:26:3 PM -- Shutting down databae... 5/19/21 12:26:37 PM -- Intance (complete), Intance (complete), Intance (complete), Intance2176. (complete) and Intance (complete) 5/19/21 12:26:37 PM -- C:\Uer\Adminitrator\Document\Performance_21_5_19_12_2_38.blg ha 95 ample. 5/19/21 12:26:37 PM -- Creating tet report... 5/19/21 12:26:38 PM -- Intance ha 2. for ae. 5/19/21 12:26:38 PM -- Intance ha 1.2 for. 5/19/21 12:26:38 PM -- Intance ha 1.2 for. N I M B L E S T O R A G E : E X C H A N G E S T O R A G E S O L U T I O N 28

29 5/19/21 12:26:38 PM -- Intance ha 2. for ae. 5/19/21 12:26:38 PM -- Intance ha 1.2 for. 5/19/21 12:26:38 PM -- Intance ha 1.2 for. 5/19/21 12:26:38 PM -- Intance ha 2. for ae. 5/19/21 12:26:38 PM -- Intance ha 1.2 for. 5/19/21 12:26:38 PM -- Intance ha 1.2 for. 5/19/21 12:26:38 PM -- Intance2176. ha 2. for ae. 5/19/21 12:26:38 PM -- Intance2176. ha 1.2 for. 5/19/21 12:26:38 PM -- Intance2176. ha 1.2 for. 5/19/21 12:26:38 PM -- Intance ha 2. for ae. 5/19/21 12:26:38 PM -- Intance ha 1.2 for. 5/19/21 12:26:38 PM -- Intance ha 1.2 for. 5/19/21 12:26:38 PM -- Tet ha Maximum ae P Fault Stall/ec. 5/19/21 12:26:38 PM -- The tet ha ae P Fault Stall/ec ample higher than. 5/19/21 12:26:38 PM -- C:\Uer\Adminitrator\Document\Performance_21_5_19_12_2_38.xml ha 9 ample queried. 5/19/21 12:26:38 PM -- C:\Uer\Adminitrator\Document\Performance_21_5_19_12_2_38.html wa aved. 5/19/21 12:27:31 PM -- Performance logging tarted (interval: m). 5/19/21 12:27:31 PM -- Recovering databae... 5/19/21 12:33:26 PM -- Performance logging ha ended. 5/19/21 12:33:26 PM -- Intance ( ), Intance ( ), Intance ( ), Intance2176. ( ) and Intance ( ) 5/19/21 12:33:26 PM -- C:\Uer\Adminitrator\Document\SoftRecovery_21_5_19_12_27_28.blg ha 87 ample. 5/19/21 12:33:26 PM -- Creating tet report... Nimble Stor, Inc. 211 River Oak Parkway, San Joe, CA 9513 Tel: ; info@nimbletor.com 21 Nimble Stor Inc. N I M B L E S T O R A G E : E X C H A N G E S T O R A G E S O L U T I O N 29