Home
%3CLINGO-SUB%20id%3D%22lingo-sub-609300%22%20slang%3D%22en-US%22%3EExchange%20Team%20blog%20is%20moving%20to%20a%20new%20home%20soon!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-609300%22%20slang%3D%22en-US%22%3E%3CP%3E%3C%2FP%3E%3CP%3EEHLO!%3C%2FP%3E%3CP%3EAs%20we%20hinted%20in%20our%20%3CA%20href%3D%22https%3A%2F%2Fblogs.technet.microsoft.com%2Fexchange%2F2019%2F02%2F09%2F15-years%2F%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3E15%20year%20blogoversary%3C%2FA%3E%20post%2C%20this%20blog%20will%20be%20moving%20to%20a%20new%20home%20soon.%20Here%20is%20what%20you%20can%20expect%3A%3CUL%3E%3CLI%3EOur%20new%20home%20will%20be%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fcustom%2Fpage%2Fpage-id%2FBlogs%22%20target%3D%22_blank%22%3EMicrosoft%20Tech%20Community%2C%20Blogs%20section%3C%2FA%3E%20(there%20will%20be%20%E2%80%9CExchange%E2%80%9D%20in%20the%20list%20once%20all%20is%20said%20and%20done%2C%20with%20its%20own%20unique%20URL)%3C%2FLI%3E%3CLI%3EWe%20have%20done%20a%20lot%20of%20cleanup%20of%20our%2015%20years%20of%20content%20already%3B%20generally%20speaking%20%E2%80%93%20if%20it%20is%20live%20on%20the%20blog%20today%2C%20it%20will%20migrate%20over.%20We%20did%20not%20try%20to%20delete%20%E2%80%98legacy%E2%80%99%20content%2C%20rather%20get%20rid%20of%20stuff%20that%20is%20obviously%20not%20relevant%20anymore%20(like%20that%20Exchange%205.5%20Webcast%20announcement%20from%2014%20years%20ago)%3C%2FLI%3E%3CLI%3EYes%2C%20we%20will%20be%20migrating%20post%20comments%20over%20too%3B%20however%2C%20due%20to%20reasons%E2%80%A6%20all%20of%20the%20comments%20will%20migrate%20over%20as%20anonymous%3B%20we%20felt%20there%20was%20still%20value%20there%20to%20keep%20the%20discussion%20present%20even%20though%20it%20might%20not%20be%20immediately%20obvious%20who%20was%20asking%20and%20replying%20exactly.%20The%20context%20helps%20in%20many%20cases%2C%20and%20good%20advice%20is%20good%20advice%20so%E2%80%A6%3C%2FLI%3E%3CLI%3EWe%20will%20work%20to%20make%20sure%20all%20of%20individual%20current%20post%20URLs%20redirect%20to%20migrated%20posts%20in%20their%20new%20location%3C%2FLI%3E%3CLI%3EWe%20will%20work%20to%20redirect%20short%20URLs%20that%20go%20to%20our%20blog%20today%2C%20like%20%3CA%20href%3D%22http%3A%2F%2Faka.ms%2Fehlo%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3Ehttp%3A%2F%2Faka.ms%2Fehlo%3C%2FA%3E%3C%2FLI%3E%3CLI%3EAll%20of%20this%20is%20going%20to%20happen%20within%20next%203-6%20weeks.%20Or%20earlier.%20Or%20later.%20Basically%3A%20%E2%80%9CWhen%20it%E2%80%99s%20ready.%E2%80%9D%3C%2FLI%3E%3C%2FUL%3E%3C%2FP%3E%3CH3%20id%3D%22toc-hId-1562856280%22%20id%3D%22toc-hId-1563542588%22%20id%3D%22toc-hId-1563542588%22%3EWhat%20can%20you%20do%20to%20prepare%3F%3C%2FH3%3E%3CP%3EIf%20you%20want%20to%20keep%20being%20engaged%20with%20us%20and%20want%20to%20keep%20commenting%20to%20our%20posts%20(and%20continue%20the%20%3CA%20href%3D%22https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dw_BvYIG1g8c%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3Ediscussion%20that%20Exchange%20community%20is%20known%20for%3C%2FA%3E)%2C%20you%20will%20need%20to%20register%20with%20Tech%20Community%20site.%20We%20are%20not%20doing%20any%20kind%20of%20migration%20of%20user%20accounts.%3C%2FP%3E%3CP%3EWhen%20we%20will%20be%20in%20the%20finalization%20stage%2C%20there%20is%20likely%20going%20to%20be%20some%20time%20when%20we%20will%20take%20a%20%E2%80%98snapshot%E2%80%99%20and%20migrate%20that%2C%20and%20any%20comments%20etc.%20made%20after%20that%20will%20be%20lost%20once%20we%20move%20over%20(as%20they%20will%20not%20be%20in%20migration%20set).%20We%20will%20give%20you%20a%20heads%20up%20when%20this%20is%20about%20to%20happen.%20If%20unexpected%20things%20happen%20and%20you%20start%20getting%20errors%20temporarily%2C%20now%20you%20know%20what%E2%80%99s%20up!%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22author%22%3EThe%20Exchange%20Team%20Blog%20Team%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-611574%22%20slang%3D%22en-US%22%3EExchange%202010%20Server%20Role%20Requirements%20Calculator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-611574%22%20slang%3D%22en-US%22%3E%3CP%3E%3C%2FP%3E%3CP%20class%3D%22ehlopost%22%3E%3CSPAN%20style%3D%22color%3A%20%23ff0000%3B%22%3EEDIT%3A%20This%20post%20has%20been%20updated%20on%205%2F24%2F2013%20for%20the%20new%20version%20of%20calculator.%20For%20the%20list%20of%20latest%20major%20changes%2C%20please%20see%20%3CA%20href%3D%22http%3A%2F%2Fblogs.technet.com%2Fb%2Fexchange%2Farchive%2F2010%2F01%2F22%2Fupdates-to-the-exchange-2010-mailbox-server-role-requirements-calculator.aspx%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3ETHIS%3C%2FA%3E.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CH2%20class%3D%22ehlopost%22%20id%3D%22toc-hId-1760053240%22%20id%3D%22toc-hId--792100868%22%3EOverview%3C%2FH2%3E%0A%3CP%20class%3D%22ehlopost%22%3EThe%20Exchange%20Mailbox%20Server%20role%20is%20arguably%20one%20of%20the%20most%20important%20roles%20within%20an%20Exchange%20deployment%20for%20it%20stores%20the%20data%20that%20users%20will%20ultimately%20access%20on%20a%20daily%20basis.%20Therefore%2C%20ensuring%20that%20you%20design%20the%20mailbox%20server%20role%20correctly%20is%20critical%20to%20your%20design.%3C%2FP%3E%0A%3CP%20class%3D%22ehlopost%22%3EWith%20Exchange%202010%20you%20can%20deploy%20a%20solution%20that%20leverages%20mailbox%20resiliency%20and%20has%20multiple%20database%20copies%20deployed%20across%20datacenters%2C%20implements%20single%20item%20recovery%20for%20data%20recovery%2C%20and%20has%20the%20flexibility%20in%20storage%20design%20to%20allow%20you%20to%20deploy%20on%20storage%20area%20networks%20utilizing%20fibre-channel%20or%20SATA%20class%20disks%20or%20on%20direct%20attached%20storage%20utilizing%20SAS%20or%20SATA%20class%20disks%20with%20or%20without%20RAID%20protection.%20But%2C%20in%20order%20to%20design%20your%20solution%2C%20you%20need%20to%20understand%20the%20following%20criteria%3A%3C%2FP%3E%0A%3CDIV%20class%3D%22ehlopost%22%3E%0A%3CUL%3E%0A%3CLI%3EUser%20profile%20-%20the%20message%20profile%2C%20the%20mailbox%20size%2C%20and%20the%20number%20of%20users%3C%2FLI%3E%0A%3CLI%3EHigh%20availability%20architecture%20-%20the%20number%20of%20database%20copies%20you%20plant%20to%20deploy%2C%20whether%20the%20solution%20will%20be%20site%20resilient%2C%20the%20desired%20number%20of%20mailbox%20servers%3C%2FLI%3E%0A%3CLI%3EServer's%20CPU%20platform%3C%2FLI%3E%0A%3CLI%3EStorage%20architecture%20-%20the%20disk%20capacity%20%2F%20type%20and%20storage%20solution%3C%2FLI%3E%0A%3CLI%3EBackup%20architecture%20-%20whether%20to%20use%20hardware%20or%20software%20VSS%20and%20the%20frequency%20of%20the%20backups%2C%20or%20leverage%20the%20Exchange%20native%20data%20protection%20features%3C%2FLI%3E%0A%3CLI%3ENetwork%20architecture%20-%20the%20utilization%2C%20throughput%2C%20and%20latency%20aspects%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FDIV%3E%0A%3CP%3EPrevious%20versions%20of%20Exchange%20were%20somewhat%20rigid%20in%20terms%20of%20the%20choices%20you%20had%20in%20designing%20your%20mailbox%20server%20role.%20The%20flexibility%20in%20the%20architecture%20with%20Exchange%202010%2C%20allows%20you%20the%20freedom%20to%20design%20the%20solution%20to%20meet%20your%20needs.%20Prior%20to%20making%20any%20decisions%2C%20please%20review%20the%20following%20topics%20from%20the%20Exchange%202010%20Online%20Help%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fdd638137(EXCHG.140).aspx%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EUnderstanding%20High%20Availability%20and%20Site%20Resilience%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3E%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fdd638104(EXCHG.140).aspx%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EPlanning%20for%20High%20Availability%20and%20Site%20Resilience%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3E%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fdd876874(EXCHG.140).aspx%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EUnderstanding%20Backup%2C%20Restore%20and%20Disaster%20Recovery%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3E%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fdd346703(EXCHG.140).aspx%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EMailbox%20Server%20Storage%20Design%20Recommendations%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3E%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fdd351197.aspx%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EPerformance%20and%20Scalability%3C%2FA%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EAfter%20you%20have%20determined%20the%20design%20you%20would%20like%20to%20implement%2C%20you%20can%20follow%20the%20steps%20in%20the%20%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fee832789.aspx%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EExchange%202010%20Mailbox%20Server%20Role%20Design%20Example%3C%2FA%3E%20article%20within%20the%20Exchange%202010%20Online%20Help%20to%20calculate%20your%20solution's%20CPU%2C%20memory%2C%20and%20storage%20requirements%2C%20or%20you%20can%20leverage%20the%20Exchange%202010%20Mailbox%20Server%20Role%20Requirements%20Calculator.%3C%2FP%3E%0A%3CP%3EThe%20calculator%20is%20broken%20out%20into%20the%20following%20sections%20(worksheets)%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EInput%3C%2FLI%3E%0A%3CLI%3ERole%20Requirements%3C%2FLI%3E%0A%3CLI%3EActivation%20Scenarios%3C%2FLI%3E%0A%3CLI%3EDistribution%3C%2FLI%3E%0A%3CLI%3ELUN%20Requirements%3C%2FLI%3E%0A%3CLI%3EBackup%20Requirements%3C%2FLI%3E%0A%3CLI%3ELog%20Replication%20Requirements%3C%2FLI%3E%0A%3CLI%3EStorage%20Design%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSTRONG%3EImportant%3A%3C%2FSTRONG%3E%20The%20data%20points%20provided%20in%20the%20calculator%20are%20an%20example%20configuration.%20As%20such%20any%20data%20points%20entered%20into%20the%20Input%20worksheet%20are%20specific%20to%20that%20particular%20configuration%20and%20do%20not%20apply%20for%20other%20configurations.%20Please%20ensure%20you%20are%20using%20the%20correct%20data%20points%20for%20your%20design%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EInput%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EWhen%20you%20launch%20the%20Exchange%202010%20Mailbox%20Server%20Role%20Requirements%20Calculator%2C%20you%20are%20presented%20with%20the%20Input%20worksheet.%20This%20worksheet%20is%20broken%20down%20into%205%20key%20areas.%20This%20section%20is%20where%20you%20enter%20in%20all%20the%20relevant%20information%20regarding%20your%20intended%20design%2C%20so%20that%20the%20calculator%20can%20generate%20what%20you%20need%20in%20order%20to%20achieve%20it.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ENote%3A%3C%2FSTRONG%3E%20There%20are%20many%20input%20factors%20that%20need%20to%20be%20accounted%20for%20before%20you%20can%20design%20your%20solution.%20Each%20input%20factor%20is%20briefly%20listed%20below%3B%20there%20are%20additional%20notes%20within%20the%20calculator%20that%20explain%20them%20in%20more%20detail.%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--792103721%22%20id%3D%22toc-hId-950709467%22%3EEnvironment%20Configuration%3C%2FH2%3E%0A%3CP%3EWithin%20Step%201%20you%20will%20enter%20in%20the%20appropriate%20information%20concerning%20your%20messaging%20environment's%20configuration%20-%20the%20high%20availability%20architecture%20and%20database%20copy%20configuration%2C%20the%20data%20and%20I%2FO%20configuration%2C%20and%20CPU%20inputs.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ENote%3A%20%3C%2FSTRONG%3EFor%20optimal%20sizing%2C%20choose%20a%20multiple%20of%20the%20total%20number%20of%20database%20copies%20you%20have%20selected%20for%20the%20number%20of%20mailbox%20servers.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%3CA%20href%3D%22https%3A%2F%2Fhelpcenter.xactlycorp.com%2Flegacyfs%2Fonline%2Fmedia%2FTNBlogsFS%2Fprod.evol.blogs.technet.com%2FCommunityServer.Blogs.Components.WeblogFiles%2F00%2F00%2F00%2F31%2F06%2F6840.1.png%22%20original-url%3D%22http%3A%2F%2Fblogs.technet.com%2Fcfs-file.ashx%2F__key%2Fcommunityserver-blogs-components-weblogfiles%2F00-00-00-31-06%2F6840.1.png%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%22%3E%3CIMG%20src%3D%22http%3A%2F%2Fmigration9.stage.lithium.com%2Fskins%2Fimages%2FAF7D1A50469BCCC446F7CEAA2F38CF9E%2Fresponsive_peak%2Fimages%2Fimage_not_found.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FA%3E%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EExchange%20Environment%20Configuration%3C%2FSTRONG%3E%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3E%3CEM%3EWhat%20server%20architecture%20are%20you%20deploying%20for%20your%20global%20catalogs%3F%3C%2FEM%3E%20You%20can%20deploy%20either%20the%2032-bit%20or%2064-bit%20architecture%20for%20your%20Active%20Directory%20servers.%20The%20architecture%20you%20deploy%20will%20affect%20your%20core%20ratio%20planning.%20For%20more%20information%2C%20please%20see%20%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fdd346701.aspx%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3Ehttp%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fdd346701.aspx%3C%2FA%3E.%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EDo%20these%20servers%20only%20have%20the%20mailbox%20server%20role%20installed%3F%3C%2FEM%3E%20Having%20the%20Hub%20Transport%20and%20Client%20Access%20server%20roles%20also%20installed%20on%20the%20along%20with%20the%20mailbox%20server%20role%20affects%20your%20design%20in%20the%20areas%20of%20load%20balancing%20client%20requests%2C%20memory%20utilization%2C%20and%20CPU%20utilization.%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EWill%20these%20servers%20be%20deployed%20as%20guest%20machines%20in%20a%20virtualized%20environment%3F%3C%2FEM%3E%26nbsp%3B%20There%20is%20CPU%20overhead%20that%20must%20be%20accounted%20for%20when%20deploying%20guest%20machines%20that%20must%20be%20accounted%20for%20in%20the%20design.%26nbsp%3B%20For%20Hyper-V%20deployments%20the%20overhead%20is%20about%2010%25.%26nbsp%3B%20Check%20with%20your%20hypervisor%20vendor%20to%20determine%20their%20overhead%20and%20adjust%20the%20%E2%80%9CHypervisor%20CPU%20Adjustment%20Factor%E2%80%9D%20accordingly.%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EAre%20you%20deploying%20a%20database%20availability%20group%20(DAG)%3F%3C%2FEM%3E%20Deploying%20the%20solution%20as%20DAG%20provides%20you%20additional%20flexibility%20and%20resiliency%20choices%20like%20having%20multiple%20mailbox%20database%20copies%2C%20leveraging%20flexible%20mailbox%20protection%20features%20in%20lieu%20of%20traditional%20backups%2C%20and%20flexibility%20in%20your%20storage%20architecture%20(e.g.%20RAID%20or%20JBOD).%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EHow%20many%20mailbox%20servers%20are%20you%20going%20to%20deploy%3C%2FEM%3E%20%3CEM%3Ewithin%20the%20primary%20datacenter%3C%2FEM%3E%3F%20If%20you%20enter%20more%20than%20a%20single%20server%20(remember%20a%20DAG%20requires%20at%20least%20two%20and%20can%20support%20a%20maximum%20of%2016)%2C%20the%20calculator%20will%20evenly%20distribute%20the%20user%20mailboxes%20across%20the%20total%20number%20of%20mailbox%20servers%20and%20make%20performance%20and%20capacity%20recommendations%20for%20each%20server%2C%20as%20well%20as%2C%20for%20the%20entire%20environment.%20As%20for%20the%20secondary%20datacenter%2C%20the%20calculator%20will%20determine%20the%20number%20of%20mailbox%20servers%20you%20need%20to%20deploy%20there%20based%20on%20the%20requirements%20(number%20of%20databases%2C%20number%20of%20copies%2C%20etc.).%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EHow%20many%20DAGs%20are%20you%20planning%20to%20deploy%20in%20the%20environment%3F%3C%2FEM%3E%20If%20you%20enter%20more%20than%20a%20single%20DAG%2C%20then%20the%20calculator%20will%20distribute%20the%20user%20mailboxes%20across%20the%20total%20number%20of%20DAGs%20and%20make%20performance%20and%20capacity%20recommendations%20for%20each%20server%20and%20each%20DAG%2C%20as%20well%20as%2C%20for%20the%20entire%20environment.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3E%3CSTRONG%3ESite%20Resilience%20Configuration%3C%2FSTRONG%3E%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3E%3CEM%3EAre%20you%20deploying%20the%20DAG%20in%20a%20site%20resilient%20configuration%3F%3C%2FEM%3E%20A%20DAG%20can%20be%20stretched%20across%202%20or%20more%20datacenters%20(the%20calculator%20only%20allows%20for%201%20datacenter)%20without%20requiring%20the%20AD%20site%20or%20network%20subnet%20to%20be%20stretched.%3CEM%3E%26nbsp%3B%3C%2FEM%3E%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EWhat%20user%20distribution%20model%20will%20you%20be%20leveraging%20in%20your%20site%20resilient%20architecture%3F%3C%2FEM%3EWhen%20planning%20a%20site%20resilience%20model%20with%20Exchange%202010%2C%20keep%20in%20mind%20there%20are%20two%20variables%20that%20need%20to%20be%20considered%3A%20namespace%20model%20and%20user%20distribution%20model.%20For%20the%20namespace%20or%20datacenter%20model%2C%20Exchange%202010%20requires%20both%20datacenters%20to%20be%20in%20an%20Active%2FActive%20configuration.%20This%20means%20that%20both%20datacenters%20participating%20in%20the%20DAG%20solution%20must%20have%20active%2C%20reachable%20namespaces%20and%20have%20the%20ability%20to%20support%20active%20load%20at%20any%20time.%20For%20the%20user%20distribution%20model%2C%20the%20design%20can%20support%20both%20Active%2FPassive%20and%20Active%2FActive%20user%20distribution.%20The%20calculator%20supports%20three%20scenarios%20for%20these%20user%20distribution%20models%3A%3COL%3E%0A%3CLI%3EActive%2FPassive%20User%20Distribution%20Model%20-%20An%20Active%2FPassive%20user%20distribution%20architecture%20simply%20has%20database%20copies%20deployed%20in%20the%20secondary%20datacenter%2C%20but%20no%20active%20mailboxes%20are%20hosted%20there%20and%20no%20database%20copies%20will%20be%20activated%20there%20during%20normal%20runtime%20operations.%20However%2C%20the%20datacenter%20supports%20both%20single%20cross-datacenter%20database%20*overs%2C%20and%20full%20datacenter%20activation.%3C%2FLI%3E%0A%3CLI%3EAn%20Active%2FActive%20user%20distribution%20architecture%20has%20the%20user%20population%20dispersed%20across%20both%20datacenters%20(usually%20evenly)%20with%20each%20datacenter%20being%20the%20primary%20datacenter%20for%20its%20specific%20user%20population.%26nbsp%3B%20In%20the%20event%20of%20a%20failure%2C%20the%20user%20population%20can%20be%20activated%20in%20the%20secondary%20datacenter%20(either%20via%20cross-datacenter%20single%20database%20*over%20or%20via%20full%20datacenter%20activation).%26nbsp%3B%20There%20are%20two%20types%20of%20Active%2FActive%20user%20distribution%20models%3A%3COL%3E%0A%3CLI%3EActive%2FActive%20(Single%20DAG)%20-%20This%20model%20stretches%20a%20DAG%20across%20the%20two%20datacenters%20and%20has%20active%20mailboxes%20located%20in%20each%20datacenter.%26nbsp%3B%20A%20corresponding%20passive%20copy%20is%20located%20in%20the%20alternate%20datacenter.%26nbsp%3B%20This%20scenario%20does%20have%20a%20single%20point%20of%20failure%20(potentially)%2C%20the%20WAN%20connection.%26nbsp%3B%20Loss%20of%20the%20WAN%20connection%20will%20result%20in%20the%20mailbox%20servers%20in%20one%20of%20the%20datacenters%20going%20into%20a%20failed%20state%20from%20a%20failover%20cluster%20perspective%20(due%20to%20loss%20of%20quorum)%3A%3CTABLE%20style%3D%22width%3A%20400px%3B%22%20border%3D%221%22%20cellspacing%3D%220%22%20cellpadding%3D%222%22%3E%0A%3CTBODY%3E%0A%3CTR%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22199%22%3E---DC1---%3C%2FTD%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22199%22%3E---DC2---%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22199%22%3EDAG1%3C%2FTD%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22199%22%3EDAG1%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22199%22%3EActive%20Copies%3C%2FTD%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22199%22%3EPassive%20Copies%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22199%22%3EPassive%20Copies%3C%2FTD%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22199%22%3EActive%20Copies%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3C%2FTBODY%3E%0A%3C%2FTABLE%3E%0A%3C%2FLI%3E%0A%3CLI%3EActive%2FActive%20(Multiple%20DAGs)%20-%20This%20model%20leverages%20multiple%20DAGs%20to%20remove%20single%20points%20of%20failure%20(e.g.%2C%20the%20WAN).%26nbsp%3B%20In%20this%20model%2C%20there%20are%20least%20two%20DAGs%2C%20with%20each%20DAG%20having%20its%20active%20copies%20in%20the%20alternate%20datacenter%3A%3CTABLE%20style%3D%22width%3A%20400px%3B%22%20border%3D%221%22%20cellspacing%3D%220%22%20cellpadding%3D%222%22%3E%0A%3CTBODY%3E%0A%3CTR%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22199%22%3E---DC1---%3C%2FTD%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22199%22%3E---DC2---%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22199%22%3EDAG-A%20(active%2Fpassive%20copies)%3C%2FTD%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22199%22%3EDAG-A%20(Passive%20Copies)%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22199%22%3EDAG-B%20(Passive%20Copies%3C%2FTD%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22199%22%3EDAG-B%20(Active%2FPassive%20Copies)%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3C%2FTBODY%3E%0A%3C%2FTABLE%3E%0A%3C%2FLI%3E%0A%3C%2FOL%3E%3C%2FLI%3E%0A%3C%2FOL%3E%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EIn%20your%20site%20resilient%20architecture%2C%20how%20far%20behind%20can%20you%20get%20in%20terms%20of%20log%20shipping%20between%20datacenters%3F%20%3C%2FEM%3EThe%20effect%20of%20the%20RPO%20is%20to%20evaluate%20the%20non-contiguous%20peak%20hours%20(defined%20in%20Step%205)%2C%20say%208am%20and%204pm%2C%20and%20determine%20the%20resulting%20throughput%20requirement%2C%20assuming%20that%20you%20can%20take%20the%20time%20in%20between%208%20and%204%20to%20catch%20up%20(within%20the%20specified%20RPO%2C%20of%20course).%20By%20allowing%20replication%20to%20get%20behind%20there%20are%20two%20outcomes%3A%201.%20Active%20Manager%20is%20less%20likely%20to%20choose%20a%20database%20copy%20that%20has%20a%20high%20copy%20queue%20length%20(unless%20more%20viable%20alternatives%20aren't%20available).%202.%20If%20the%20copy%20queue%20length%20is%20greater%20than%20the%20target%20server's%20AutoDatabaseMountDial%20setting%2C%20the%20database%20will%20not%20automatically%20mount%20once%20activated.%20Manually%20mounting%20that%20database%20will%20result%20in%20the%20loss%20of%20data%20that%20had%20not%20been%20copied.%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EWill%20you%20activation%20block%20the%20mailbox%20servers%20in%20the%20secondary%20datacenter%3F%20%3C%2FEM%3EIn%20certain%20situations%20(e.g.%20highly%20utilized%20network%20connection)%2C%20you%20may%20want%20to%20control%20whether%20cross-site%20failovers%20occur%20automatically.%20This%20can%20be%20controlled%20by%20placing%20an%20activation%20block%20on%20the%20remote%20mailbox%20servers%2C%20thereby%20preventing%20Active%20Manager%20from%20selecting%20those%20copies%20during%20a%20failover.%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EWhen%20deploying%20an%20Active%2FActive%20(Single%20DAG)%20architecture%2C%20do%20you%20want%20to%20deploy%20dedicated%20disaster%20recovery%20Mailbox%20servers%20in%20the%20alternate%20datacenter%3F%3C%2FEM%3E%26nbsp%3B%20If%20deploying%20a%20single%20DAG%20Active%2FActive%20solution%2C%20you%20can%20choose%20to%20have%20dedicated%20DR%20Mailbox%20servers%20deployed%20in%20the%20secondary%20datacenter%20to%20be%20used%20in%20the%20event%20of%20disaster%20or%20utilize%20the%20existing%20mailbox%20servers%20that%20are%20hosting%20active%20mailboxes.%26nbsp%3B%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3E%3CSTRONG%3EMailbox%20Database%20Copy%20Configuration%3C%2FSTRONG%3E%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3E%3CEM%3EHow%20many%20highly%20available%20(HA)%20mailbox%20database%20copy%20instances%20per%20database%20do%20you%20plan%20to%20deploy%20within%20a%20DAG%3F%3C%2FEM%3E%20Enter%20in%20the%20number%20of%20highly%20available%20database%20copies%20you%20plan%20to%20have%20within%20the%20environment.%20This%20value%20excludes%20lagged%20database%20copies%2C%20but%20does%20account%20for%20both%20the%20active%20and%20any%20passive%20HA%20database%20copies%2C%20but%20includes%20both%20the%20active%20copy%20and%20all%20passive%20copies%20you%20plan%20to%20deploy.%20For%20optimal%20sizing%2C%20choose%20a%20multiple%20of%20the%20total%20number%20of%20mailbox%20servers%20you%20have%20selected.%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EHow%20many%20lagged%20database%20copy%20instances%20per%20database%20do%20you%20plan%20to%20deploy%20within%20a%20DAG%3F%3C%2FEM%3E%20Lagged%20database%20copies%20are%20an%20optional%20feature%20that%20can%20provide%20protection%20against%20certain%20disaster%20scenarios%20(like%20logical%20corruption).%20Lagged%20database%20copies%20should%20not%20be%20considered%20an%20HA%20database%20copy%20as%20the%20replay%20will%20delay%20the%20availability%20of%20the%20database%20for%20use%20once%20activated.%20While%20technically%20there%20is%20no%20limit%20to%20how%20many%20lagged%20copies%20you%20can%20deploy%20within%20a%20DAG%2C%20the%20calculator%20limits%20you%20to%20a%20maximum%20of%202%20copies.%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EHow%20many%20highly%20available%20mailbox%20database%20copy%20instances%20per%20database%20do%20you%20plan%20to%20deploy%20within%20the%20secondary%20datacenter%20within%20a%20DAG%3F%3C%2FEM%3E%20If%20you%20are%20deploying%20a%20site%20resilient%20solution%2C%20you%20can%20choose%20to%20a%20portion%20of%20the%20total%20HA%20database%20copies%20deployed%20in%20the%20secondary%20datacenter.%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EHow%20many%20lagged%20database%20copy%20instances%20per%20database%20do%20you%20plan%20to%20deploy%20within%20the%20secondary%20datacenter%20within%20a%20DAG%3F%3C%2FEM%3E%20If%20you%20are%20deploying%20a%20site%20resilient%20solution%2C%20you%20can%20choose%20to%20have%20a%20portion%20or%20all%20of%20your%20lagged%20database%20copies%20deployed%20in%20the%20secondary%20datacenter.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3E%3CSTRONG%3ELagged%20Database%20Copy%20Configuration%3C%2FSTRONG%3E%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3E%3CEM%3EWill%20you%20deploy%20the%20lagged%20database%20copies%20on%20a%20dedicated%20server%3F%3C%2FEM%3E%20Using%20a%20dedicated%20server%20for%20lagged%20database%20copies%20certainly%20makes%20it%20easier%20to%20manage.%20For%20DAGs%20where%20the%20lagged%20database%20copies%20are%20evenly%20distributed%20across%20all%20the%20DAG%20mailbox%20servers%2C%20you%20will%20need%20to%20use%20the%20Suspend-MailboxDatabaseCopy%20with%20the%20-ActivationOnly%20flag%20to%20prevent%20them%20from%20being%20mounted%2C%20but%20there%20are%20scenarios%20that%20can%20clear%20this.%20With%20a%20dedicated%20server%20you%20can%20activation%20block%20the%20entire%20server%20and%20the%20setting%20is%20persistent.%20The%20choice%20can%20also%20affect%20your%20storage%20design%20in%20terms%20of%20choosing%20RAID%20or%20JBOD.%20Unless%20you%20have%20multiple%20lagged%20copies%2C%20lagged%20copies%20should%20be%20placed%20on%20storage%20that%20is%20utilizing%20RAID%20to%20provide%20additional%20protection.%20The%20calculator%20will%20determine%20the%20appropriate%20number%20of%20lagged%20copy%20servers%20you%20need%20to%20deploy%20based%20on%20the%20requirements%20(number%20of%20databases%2C%20number%20of%20copies%2C%20etc).%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EHow%20long%20will%20you%20delay%20transaction%20log%20replay%20on%20your%20lagged%20copy%3F%3C%2FEM%3E%20This%20parameter%20is%20used%20to%20specify%20the%20amount%20of%20time%20that%20the%20Microsoft%20Exchange%20Information%20Store%20service%20should%20wait%20before%20replaying%20log%20files%20that%20have%20been%20copied%20to%20the%20lagged%20database.%20The%20maximum%20amount%20of%20replay%20delay%20you%20can%20set%20is%2014%20days.%20The%20value%20you%20specify%20here%20will%20influence%20the%20log%20capacity%20requirements%20for%20all%20copies%20and%20the%20amount%20of%20time%20required%20to%20mount%20a%20lagged%20copy.%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EHow%20long%20will%20you%20delay%20transaction%20log%20truncation%20on%20your%20lagged%20copy%3F%3C%2FEM%3E%20This%20parameter%20is%20used%20to%20specify%20the%20amount%20of%20time%20that%20the%20Microsoft%20Exchange%20Replication%20service%20should%20wait%20before%20truncating%20log%20files%20that%20have%20been%20copied%20to%20the%20lagged%20database.%20The%20time%20period%20begins%20after%20the%20log%20has%20been%20successfully%20replayed%20into%20the%20lagged%20copy.%20The%20maximum%20allowable%20setting%20for%20this%20value%20is%2014%20days.%20The%20minimum%20allowable%20setting%20is%200%2C%20although%20setting%20this%20value%20to%200%20effectively%20eliminates%20any%20delay%20in%20log%20truncation%20activity.%20The%20value%20you%20specify%20here%20will%20influence%20the%20log%20capacity%20requirements%20for%20all%20copies.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3E%3CSTRONG%3EExchange%20Data%20Configuration%3C%2FSTRONG%3E%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3E%3CEM%3EWhat%20will%20be%20the%20Data%20Overhead%20Factor%3F%3C%2FEM%3E%20Microsoft%20recommends%20using%2020%25%20to%20account%20for%20any%20extraneous%20growth%20that%20may%20occur.%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EHow%20many%20mailboxes%20do%20you%20move%20per%20week%3F%3C%2FEM%3E%20In%20terms%20of%20transactions%2C%20you%20have%20to%20take%20into%20account%20how%20many%20mailboxes%20you%20will%20either%20be%20moving%20to%20this%20server%20or%20within%20this%20server%2C%20as%20transactions%20totaling%20the%20size%20of%20the%20mailbox%20will%20always%20get%20generated%20at%20the%20target%20database.%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EAre%20you%20going%20to%20deploy%20a%20Dedicated%20Restore%20LUN%3F%3C%2FEM%3E%20A%20dedicated%20restore%20LUN%20is%20used%20as%20a%20staging%20point%20for%20the%20restoration%20of%20data%20or%20could%20be%20used%20during%20maintenance%20activities%3B%20if%20one%20is%20selected%20then%20additional%20capacity%20will%20not%20be%20factored%20into%20each%20database%20LUN.%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EWhat%20percentage%20of%20disk%20space%20do%20you%20want%20to%20ensure%20remains%20free%20on%20the%20LUN%3F%3C%2FEM%3E%20Most%20operations%20management%20programs%20have%20capacity%20thresholds%20that%20alert%20when%20a%20LUN%20is%20more%20than%2080%25%20utilized.%20This%20value%20allows%20you%20to%20ensure%20that%20each%20LUN%20has%20a%20certain%20percentage%20of%20disk%20space%20available%20so%20that%20the%20LUN%20is%20not%20designed%20and%20implemented%20at%20maximum%20capacity.%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EDo%20you%20have%20log%20shipping%20compression%20enabled%20within%20the%20DAG%3F%20%3C%2FEM%3EBy%20default%2C%20each%20DAG%20is%20configured%20to%20compress%20and%20encrypt%20the%20socket%20connection%20used%20to%20ship%20logs%20across%20different%20IP%20subnets%20(you%20can%20disable%20these%20features%20all%20together%20or%20enable%20them%20for%20all%20communications%20regardless%20of%20subnet).%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EWhat%20is%20your%20compression%20rate%3F%3C%2FEM%3E%C3%82%26nbsp%3B%20The%20compression%20capability%20that%20is%20obtained%20for%20the%20socket%20connection%20used%20to%20ship%20logs%20will%20vary%20with%20each%20customer%2C%20based%20on%20the%20data%20obtained%20in%20the%20transaction%20log%20files.%C3%82%26nbsp%3B%20By%20default%2C%20Microsoft%20recommends%20using%20a%20value%20of%2030%25%2C%20however%2C%20you%20can%20determine%20this%20value%20by%20analyzing%20your%20environment%20(e.g.%2C%20once%20Exchange%202010%20is%20deployed%20you%20could%20evaluate%20the%20throughput%20rate%20with%20compression%20disabled%20and%20then%20compare%20with%20compression%20is%20enabled)%20.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3E%3CSTRONG%3EDatabase%20Configuration%3C%2FSTRONG%3E%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3E%3CEM%3EDo%20you%20want%20to%20follow%20Microsoft's%20recommendations%20regarding%20maximum%20database%20size%3F%3C%2FEM%3E%20For%20standalone%20mailbox%20server%20role%20solutions%2C%20Microsoft%20recommends%20that%20the%20database%20size%20should%20not%20be%20more%20than%20200GB%20in%20size.%20For%20solutions%20leveraging%20mailbox%20resiliency%2C%20Microsoft%20recommends%20that%20the%20database%20size%20should%20not%20exceed%202TB.%20Neither%20of%20these%20is%20by%20any%20means%20a%20hard%20limit%2C%20but%20a%20recommendation%20based%20on%20the%20impact%20database%20size%20has%20to%20recovery%20times.%20If%20you%20want%20to%20follow%20Microsoft's%20recommendation%2C%20then%20select%20Yes.%20Otherwise%2C%20select%20No.%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EDo%20you%20want%20to%20specify%20a%20custom%20Maximum%20Database%20Size%3F%3C%2FEM%3E%20If%20you%20selected%20No%20for%20the%20previous%20field%2C%20then%20you%20need%20to%20enter%20in%20a%20custom%20maximum%20database%20size.%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EWould%20you%20like%20the%20calculator%20to%20determine%20the%20optimum%20number%20of%20databases%20for%20the%20design%3F%3C%2FEM%3E%20By%20default%20the%20calculator%20will%20determine%20the%20optimum%20number%20of%20databases%20for%20the%20architecture.%20In%20the%20event%20that%20you%20may%20want%20to%20have%20a%20defined%20number%20of%20databases%2C%20select%20No%20to%20%22Automatically%20Calculate%20Number%20of%20Databases%22%20and%20enter%20in%20a%20custom%20number%20of%20databases.%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EDo%20you%20want%20to%20specify%20the%20number%20of%20databases%20that%20should%20be%20deployed%3F%3C%2FEM%3E%20If%20you%20selected%20%22No%22%20to%20the%20previous%20field%2C%20then%20you%20need%20to%20enter%20in%20the%20number%20of%20databases%20you%20would%20like%20to%20have%20deployed%20within%20your%20mailbox%20server%20or%20DAG%20architecture.%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EDo%20you%20want%20to%20design%20your%20database%20infrastructure%20such%20that%20you%20deploy%20the%20correct%20number%20of%20databases%20to%20ensure%20symmetrical%20distribution%20during%20server%20failure%20events%3F%3C%2FEM%3E%26nbsp%3B%20If%20possible%2C%20the%20calculator%20will%20deploy%20the%20correct%20number%20of%20databases%20such%20that%20you%20can%20achieve%20a%20symmetrical%20distribution%20of%20the%20active%20copies%20across%20the%20remaining%20server%20infrastructure%20as%20the%20DAG%20experiences%20server%20failures.%26nbsp%3B%20Note%20that%20to%20use%20this%20option%2C%20you%20must%20allow%20the%20calculator%20to%20automatically%20calculate%20the%20required%20number%20of%20databases.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3E%3CSTRONG%3EIOPS%20Configuration%3C%2FSTRONG%3E%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3E%3CEM%3EWhat%20will%20be%20the%20I%2FO%20Overhead%20Factor%3F%3C%2FEM%3E%20Microsoft%20recommends%20using%2020%25%20to%20ensure%20adequate%20headroom%20in%20terms%20of%20I%2FO%20to%20allow%20for%20abnormal%20spikes%20in%20I%2FO%20that%20may%20occur%20from%20to%20time.%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EWhat%20additional%20I%2FO%20requirements%20do%20you%20need%20to%20factor%20into%20the%20solution%20for%20each%20mailbox%20server's%20storage%20design%3F%3C%2FEM%3E%20For%20example%2C%20let's%20say%20the%20solution%20requires%20500%20IOPS%20for%20the%20mailboxes%20and%20you%20have%20decided%20you%20want%20to%20ensure%20there%20is%20extra%20I%2FO%20capacity%20to%20support%20additional%20products%20(e.g.%20antivirus)%20to%20generate%20load%20during%20the%20peak%20user%20usage%20window.%20So%20you%20enter%20300%20IOPS%20in%20this%20input%20factor.%20The%20result%20is%20that%20from%20a%20host%20perspective%2C%20the%20solution%20needs%20to%20achieve%20800%20IOPS.%20This%20may%20require%20additional%20testing%20by%20comparing%20a%20baseline%20system%20against%20a%20system%20that%20has%20the%20I%2FO%20generating%20application%20installed%20and%20running.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3E%3CSTRONG%3EMailbox%20Configuration%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EWithin%20Step%202%20you%20will%20define%20your%20user%20profile%20for%20up%20to%20four%20different%20tiers%20of%20user%20populations.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fhelpcenter.xactlycorp.com%2Flegacyfs%2Fonline%2Fmedia%2FTNBlogsFS%2Fprod.evol.blogs.technet.com%2FCommunityServer.Blogs.Components.WeblogFiles%2F00%2F00%2F00%2F31%2F06%2F0020.2.JPG%22%20original-url%3D%22http%3A%2F%2Fblogs.technet.com%2Fcfs-file.ashx%2F__key%2Fcommunityserver-blogs-components-weblogfiles%2F00-00-00-31-06%2F0020.2.JPG%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%22%3E%3CIMG%20src%3D%22http%3A%2F%2Fmigration9.stage.lithium.com%2Fskins%2Fimages%2FAF7D1A50469BCCC446F7CEAA2F38CF9E%2Fresponsive_peak%2Fimages%2Fimage_not_found.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FA%3E%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3E%3CEM%3EHow%20many%20mailboxes%20will%20you%20deploy%20in%20the%20environment%3F%3C%2FEM%3E%20If%20deploying%20a%20single%20server%20environment%2C%20this%20is%20how%20many%20mailboxes%20you%20will%20deploy%20on%20this%20server.%20If%20you%20are%20deploying%20multiple%20servers%2C%20then%20this%20is%20how%20many%20mailboxes%20you%20will%20deploy%20in%20the%20environment.%20If%20you%20are%20deploying%20multiple%20DAGs%2C%20then%20this%20is%20how%20many%20mailboxes%20you%20will%20deploy%20across%20all%20of%20the%20DAGs.%20For%20example%2C%20if%20you%20choose%20to%20deploy%205%20servers%2C%20and%20want%203000%20mailboxes%20per%20server%2C%20then%20enter%2015000%20here.%20Or%20if%20you%20plan%20to%20deploy%202%20DAGs%2C%20each%20with%206%20servers%2C%20and%20you%20entered%2024000%20total%20mailboxes%2C%20then%2012000%20mailboxes%20will%20be%20deployed%20per%20DAG.%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EWhat%20is%20the%20solution's%20projected%20growth%20in%20terms%20of%20number%20of%20mailboxes%20over%20its%20lifecycle%3F%3C%2FEM%3E%20Enter%20in%20the%20total%20percentage%20by%20which%20you%20believe%20the%20number%20of%20mailboxes%20will%20grow%20during%20the%20solution's%20lifecycle.%20For%20example%2C%20if%20you%20believe%20the%20solution%20will%20increase%20by%2030%25%20over%20the%20lifecycle%20of%20the%20design%20and%20you%20are%20starting%20out%20with%201000%20mailboxes%2C%20then%20at%20the%20end%20of%20the%20lifecycle%2C%20the%20solution%20will%20have%201300%20mailboxes.%20The%20calculator%20will%20utilize%20the%20projected%20growth%20plus%20the%20number%20of%20mailboxes%20to%20ensure%20that%20the%20capacity%20and%20performance%20requirements%20can%20be%20sustained%20throughout%20the%20solution's%20lifecycle.%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EHow%20much%20mail%20do%20the%20users%20send%20and%20receive%20per%20day%20on%20average%3F%3C%2FEM%3E%20The%20usage%20profiles%20found%20here%20are%20based%20on%20the%20work%20done%20around%20the%20memory%20and%20processor%20scalability%20requirements.%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EWhat%20is%20the%20average%20message%20size%3F%3C%2FEM%3E%20For%20most%20customers%20the%20average%20message%20size%20is%20around%2075KB.%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EWhat%20will%20be%20the%20prohibit%20send%20%26amp%3B%20receive%20mailbox%20size%20limit%3C%2FEM%3E%3F%20If%20you%20want%20to%20adequately%20control%20your%20capacity%20requirements%2C%20you%20need%20to%20set%20a%20hard%20mailbox%20size%20limit%20(prohibit%20send%20and%20receive)%20for%20the%20majority%20of%20your%20users.%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EIf%20deploying%20a%20personal%20archive%20mailbox%2C%20what%20will%20be%20the%20personal%20archive%20quota%20limit%3F%3C%2FEM%3E%20If%20you%20want%20to%20adequately%20control%20your%20capacity%20requirements%2C%20you%20need%20to%20set%20a%20hard%20mailbox%20size%20limit%20(prohibit%20send%20and%20receive)%20for%20the%20majority%20of%20your%20users.%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EWhat%20is%20the%20deleted%20item%20retention%20period%3F%3C%2FEM%3E%20Enter%20in%20the%20deleted%20item%20retention%20period%20you%20plan%20to%20utilize%20within%20the%20environment.%20The%20default%20retention%20period%20is%2014%20days%2C%20however%2C%20you%20should%20adjust%20this%20to%20match%20your%20policy%20concerning%20deleted%20item%20recovery%20when%20enabling%20Single%20Item%20Recovery%20to%20eliminate%20going%20to%20backup%20media%20to%20recover%20deleted%20items.%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EAre%20you%20deploying%20Single%20Item%20Recovery%3F%3C%2FEM%3E%20Single%20Item%20Recovery%20ensures%20that%20all%20deleted%20and%20modified%20items%20are%20preserved%20for%20the%20duration%20of%20the%20deleted%20item%20retention%20window.%20By%20default%20in%20Exchange%202010%20RTM%2C%20this%20is%20not%20enabled.%20When%20enabled%2C%20this%20feature%20increases%20the%20capacity%20requirements%20for%20the%20mailbox.%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EWill%20you%20have%20calendar%20version%20logging%20enabled%3F%3C%2FEM%3E%20By%20default%2C%20all%20changes%20to%20a%20calendar%20item%20are%20recorded%20in%20the%20mailbox%20of%20a%20user%20to%20keep%20older%20versions%20of%20meeting%20items%20for%20120%20days%20and%20can%20be%20used%20to%20repair%20the%20calendar%20in%20the%20event%20of%20an%20issue.%20This%20data%20is%20stored%20in%20the%20mailbox's%20dumpster%20folder.%20When%20enabled%2C%20this%20feature%20increases%20the%20capacity%20requirements%20for%20the%20mailbox.%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EDo%20you%20want%20to%20include%20an%20IOPS%20Multiplication%20Factor%20in%20the%20prediction%20or%20custom%20I%2FO%20profile%3F%3C%2FEM%3E%20The%20IOPS%20Multiplication%20Factor%20can%20be%20used%20to%20increase%20the%20IOPS%2Fmailbox%20footprint%20for%20mailboxes%20that%20require%20additional%20I%2FO%20(for%20example%2C%20these%20mailboxes%20may%20use%20third-party%20mobile%20devices).%20The%20way%20this%20value%20is%20used%20is%20as%20follows%3A%20(IOPS%20value%20*%20Multiplication%20Factor)%20%3D%20new%20IOPS%20value.%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EDo%20you%20want%20to%20include%20a%20Megacycle%20Multiplication%20Factor%20when%20sizing%20the%20CPU%20requirements%20for%20the%20mailbox%20tier%3F%3C%2FEM%3E%26nbsp%3B%20The%20Megacycles%20Multiplication%20Factor%20can%20be%20used%20to%20increase%20the%20CPU%20cost%2Fmailbox%20footprint%20for%20mailboxes%20that%20require%20perform%20more%20CPU%20work%20than%20a%20typical%20mailbox%20(for%20example%2C%20these%20mailboxes%20may%20use%20third-party%20mobile%20devices).%20The%20way%20this%20value%20is%20used%20is%20as%20follows%3A%20(Megacycles%20value%20*%20Multiplication%20Factor)%20%3D%20new%20Megacycles%20value.%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EDo%20your%20Outlook%20Online%20Mode%20clients%20have%20versions%20of%20Windows%20Desktop%20Search%20older%20than%204.0%20or%20third-party%20desktop%20search%20engines%20deployed%3F%3C%2FEM%3E%20The%20addition%20of%20these%20indexing%20tools%20to%20the%20online%20mode%20clients%20incur%20additional%20read%20I%2FO%20penalties%20to%20the%20mailbox%20server%20storage%20subsystem.%20Care%20should%20be%20taken%20when%20enabling%20these%20desktop%20search%20engines.%20Windows%20Desktop%20Search%204.0%20and%20later%20utilizes%20synchronization%20protocols%20that%20are%20similar%20to%20how%20Outlook%20operates%20in%20cached%20mode%20to%20index%20the%20mailbox%20contents%2C%20and%20thus%20has%20a%20very%20minor%20impact%20in%20terms%20of%20disk%20read%20I%2FO.%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EAre%20you%20planning%20to%20use%20the%20I%2FO%20prediction%20formula%20or%20define%20your%20own%20IOPS%20profile%20to%20design%20toward%3F%3C%2FEM%3E%20This%20question%20asks%20whether%20you%20want%20to%20override%20the%20calculator%20in%20determining%20the%20IOPS%20%2F%20mailbox%20value.%20By%20default%20the%20calculator%20will%20predict%20the%20IOPS%20%2F%20mailbox%20value%20based%20on%20the%20number%20of%20messages%20per%20mailbox%2C%20and%20the%20user%20memory%20profile.%20For%20some%20customers%20that%20want%20to%20design%20toward%20a%20specific%20I%2FO%20profile%2C%20this%20option%20will%20not%20be%20viable.%20Therefore%2C%20if%20you%20want%20to%20design%20toward%20a%20specific%20I%2FO%20profile%2C%20select%20No.%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EWhat%20is%20your%20custom%20IOPS%20profile%20%2F%20mailbox%3F%3C%2FEM%3E%20Only%20enter%20a%20value%20in%20this%20field%20if%20you%20selected%20%22No%22%20to%20the%20%22Predict%20IOPS%20Value%22%20question.%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EWhat%20will%20be%20the%20database%20read%3Awrite%20ratio%20for%20your%20custom%20IOPS%20profile%3F%3C%2FEM%3E%20Only%20adjust%20this%20value%20if%20you%20selected%20%22No%22%20to%20the%20%22Predict%20IOPS%20Value%22%20parameter.%20When%20IOPS%20prediction%20is%20enabled%2C%20the%20calculator%20will%20calculate%20the%20read%3Awrite%20ratio%20based%20on%20the%20user%20profile.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3E%3CSTRONG%3EBackup%20Configuration%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EWithin%20Step%203%20you%20will%20define%20your%20backup%20model%20and%20your%20tolerance%20settings%2C%20as%20well%20as%2C%20choose%20whether%20to%20isolate%20the%20transaction%20logs%20from%20the%20database.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fhelpcenter.xactlycorp.com%2Flegacyfs%2Fonline%2Fmedia%2FTNBlogsFS%2Fprod.evol.blogs.technet.com%2FCommunityServer.Blogs.Components.WeblogFiles%2F00%2F00%2F00%2F31%2F06%2F4403.3.JPG%22%20original-url%3D%22http%3A%2F%2Fblogs.technet.com%2Fcfs-file.ashx%2F__key%2Fcommunityserver-blogs-components-weblogfiles%2F00-00-00-31-06%2F4403.3.JPG%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%22%3E%3CIMG%20src%3D%22http%3A%2F%2Fmigration9.stage.lithium.com%2Fskins%2Fimages%2FAF7D1A50469BCCC446F7CEAA2F38CF9E%2Fresponsive_peak%2Fimages%2Fimage_not_found.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FA%3E%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3E%3CEM%3EWhat%20backup%20methodology%20will%20be%20used%20to%20backup%20the%20solution%3F%20%3C%2FEM%3EYou%20have%20several%20options%20for%20a%20backup%20methodology%2C%20including%20leveraging%20a%20VSS%20solution%20(hardware%20or%20software%20based)%20or%20leveraging%20the%20native%20data%20protection%20features%20that%20Exchange%20provides.%20The%20solution%20you%20choose%20will%20depend%20on%20many%20factors.%20For%20example%2C%20if%20you%20are%20deploying%20the%20mailbox%20resiliency%20and%20single%20item%20recovery%20features%2C%20you%20may%20be%20able%20to%20forgo%20a%20traditional%20backup%20architecture%20in%20favor%20of%20leveraging%20Exchange%20as%20its%20own%20backup.%20Or%20if%20you%20still%20require%20a%20backup%20(e.g.%20legal%2Fcompliance%20reasons)%2C%20then%20you%20need%20to%20deploy%20a%20VSS%20solution.%20The%20type%20of%20VSS%20solution%20you%20deploy%20will%20depend%20on%20your%20storage%20architecture.%20Hardware%20VSS%20solutions%20are%20available%20with%20storage%20area%20networks.%20Software%20VSS%20solutions%20can%20be%20leveraged%20against%20either%20storage%20area%20networks%20or%20direct%20attached%20storage%20architectures.%20Also%2C%20the%20backup%20methodology%20will%20affect%20the%20LUN%20design%3B%20for%20example%2C%20hardware%20VSS%20solutions%20require%20a%20LUN%20architecture%20that%20is%202%20LUNs%20%2F%20Database.%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EWhat%20will%20be%20the%20backup%20frequency%3F%3C%2FEM%3E%20You%20can%20choose%20Daily%20Full%2C%20Weekly%20Full%20with%20Daily%20Differential%2C%20Weekly%20Full%20with%20Daily%20Incremental%2C%20or%20Bi-Monthly%20Full%20with%20Daily%20Incremental.%20The%20backup%20frequency%20will%20affect%20the%20LUN%20design%20and%20the%20disk%20space%20requirements%20(e.g.%20if%20performing%20daily%20differentials%2C%20then%20you%20need%20to%20account%20for%207%20days%20of%20log%20generation%20in%20your%20capacity%20design).%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EWill%20you%20isolate%20the%20logs%20from%20the%20database%3F%3C%2FEM%3E%C3%82%26nbsp%3B%20Database%2FLog%20isolation%20refers%20to%20placing%20the%20DB%20file%20an%20logs%20from%20the%20same%20Mailbox%20Database%20on%20to%20different%20volumes%20backed%20by%20different%20physical%20disks.%C3%82%26nbsp%3B%20For%20standalone%20architectures%2C%20the%20Exchange%20best%20practice%20is%20to%20separate%20database%20file%20(.edb)%20and%20logs%20from%20same%20database%20to%20different%20volumes%20backed%20by%20different%20physical%20disks%20for%20recoverability%20purposes.%C3%82%26nbsp%3B%20For%20solutions%20leveraging%20mailbox%20resiliency%2C%20isolation%20is%20not%20required.%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EHow%20many%20times%20can%20you%20operate%20without%20log%20truncation%3F%3C%2FEM%3E%20Select%20how%20many%20times%20you%20can%20survive%20without%20a%20full%20backup%20or%20an%20incremental%20backup%20(the%20minimum%20value%20is%201).%20For%20example%2C%20if%20you%20are%20a%20performing%20weekly%20full%20backup%20and%20daily%20differential%20backups%2C%20the%20only%20time%20log%20truncation%20occurs%20is%20during%20the%20full%20backup.%20If%20the%20full%20backup%20fails%2C%20then%20you%20have%20to%20wait%20an%20entire%20week%20to%20perform%20another%20full%20backup%20or%20perform%20an%20emergency%20full%20backup.%20This%20parameter%20allows%20you%20to%20ensure%20that%20you%20have%20enough%20capacity%20to%20not%20have%20to%20perform%20an%20immediate%20full%20backup.%20If%20you%20are%20leveraging%20the%20native%20data%20protection%20features%20within%20Exchange%20as%20your%20backup%20mechanism%2C%20then%20you%20should%20enter%203%20here%20to%20ensure%20you%20have%20enough%20capacity%20to%20allow%20for%203%20days'%20worth%20of%20log%20generation%20to%20occur%20as%20a%20result%20of%20potential%20log%20replication%20issues.%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EHow%20long%20can%20you%20survive%20a%20network%20outage%3F%3C%2FEM%3E%20When%20a%20network%20outage%20occurs%2C%20log%20replication%20cannot%20occur.%20As%20a%20result%2C%20the%20copy%20queue%20length%20will%20increase%20on%20the%20source%3B%20in%20addition%2C%20log%20truncation%20cannot%20occur%20on%20the%20source.%20For%20geographically%20dispersed%20DAG%20deployments%2C%20network%20outages%20can%20seriously%20affect%20the%20solution's%20usefulness.%20If%20the%20outage%20is%20too%20long%2C%20log%20capacity%20on%20the%20source%20may%20become%20compromised%20and%20as%20result%2C%20capacity%20must%20be%20increased%20or%20a%20manual%20log%20truncation%20event%20must%20occur.%20Once%20that%20happens%2C%20the%20remote%20copies%20must%20be%20reseeded.%20The%20Network%20Failure%20Tolerance%20parameter%20ensures%20there%20is%20enough%20capacity%20on%20the%20log%20LUNs%20so%20that%20you%20can%20survive%20an%20excessive%20network%20outage.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3E%3CSTRONG%3EStorage%20Configuration%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EWithin%20Step%204%20you%20will%20define%20your%20storage%20configuration.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%26nbsp%3B%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%3CA%20href%3D%22https%3A%2F%2Fhelpcenter.xactlycorp.com%2Flegacyfs%2Fonline%2Fmedia%2FTNBlogsFS%2Fprod.evol.blogs.technet.com%2FCommunityServer.Blogs.Components.WeblogFiles%2F00%2F00%2F00%2F31%2F06%2F2287.4.JPG%22%20original-url%3D%22http%3A%2F%2Fblogs.technet.com%2Fcfs-file.ashx%2F__key%2Fcommunityserver-blogs-components-weblogfiles%2F00-00-00-31-06%2F2287.4.JPG%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%22%3E%3CIMG%20src%3D%22http%3A%2F%2Fmigration9.stage.lithium.com%2Fskins%2Fimages%2FAF7D1A50469BCCC446F7CEAA2F38CF9E%2Fresponsive_peak%2Fimages%2Fimage_not_found.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FA%3E%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EStorage%20Options%3C%2FSTRONG%3E%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3E%3CEM%3EDo%20you%20want%20to%20consider%20storage%20designs%20that%20leverage%20JBOD%3F%20%3C%2FEM%3EJBOD%20storage%20refers%20to%20placing%20a%20database%20and%20its%20transaction%20logs%20on%20a%20single%20disk%20without%20leveraging%20RAID.%20In%20order%20to%20deploy%20this%20type%20of%20storage%20solution%20for%20your%20mailbox%20server%20environment%2C%20you%20must%20have%203%20or%20more%20HA%20database%20copies%20and%20have%20a%20LUN%20architecture%20that%20is%20equal%20to%201%20LUN%20%2F%20Database.%20If%20you%20select%20yes%20for%20this%20input%2C%20the%20calculator%20will%20attempt%20to%20design%20the%20solution%20so%20that%20it%20can%20be%20deployed%20on%20JBOD%20storage.%20Please%20note%20that%20other%20factors%20may%20alter%20the%20viability%20of%20JBOD%2C%20however%20(e.g.%20deploying%20a%20single%20lagged%20database%20copy%20on%20the%20same%20mailbox%20servers%20hosting%20your%20HA%20database%20copies).%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3E%3CSTRONG%3EPrimary%20Datacenter%20Disk%20Configuration%3C%2FSTRONG%3E%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3E%3CEM%3EWhat%20are%20the%20disk%20capacities%20and%20types%20you%20plan%20to%20deploy%3F%3C%2FEM%3E%20For%20each%20type%20of%20LUN%20(database%2C%20log%2C%20and%20restore%20LUN)%20you%20plan%20to%20deploy%2C%20select%20the%20appropriate%20capacity%20and%20disk%20type%20model.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3E%3CSTRONG%3ESecondary%20Datacenter%20Disk%20Configuration%3C%2FSTRONG%3E%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3E%3CEM%3EWhat%20are%20the%20disk%20capacities%20and%20types%20you%20plan%20to%20deploy%3F%3C%2FEM%3E%20For%20each%20type%20of%20LUN%20(database%2C%20log%2C%20and%20restore%20LUN)%20you%20plan%20to%20deploy%2C%20select%20the%20appropriate%20capacity%20and%20disk%20type%20model.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3E%3CSTRONG%3EProcessor%20Configuration%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EWithin%20Step%205%2C%20you%20will%20define%20the%20number%20of%20processor%20core%20you%20have%20deployed%20for%20each%20mailbox%20server%20within%20your%20primary%20and%20secondary%20datacenters%2C%20as%20well%20as%2C%20enter%20the%20SPECint2006%20Rate%20Value%20for%20the%20system%20you%20have%20selected.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhen%20you%20enable%20virtualization%2C%20you%20must%20be%20sure%20to%20configure%20the%20processor%20architecture%20correctly.%26nbsp%3B%20In%20particular%2C%20you%20must%20enter%20in%20the%20correct%20number%20of%20processor%20cores%20that%20the%20%3CSTRONG%3Eguest%20machine%3C%2FSTRONG%3E%20will%20support%2C%20as%20well%20as%2C%20the%20correct%20SPECInt2006%20rating%20for%20these%20virtual%20processor%20cores.%20To%20calculate%20the%20SPECInt2006%20rate%20value%2C%20you%20can%20utilize%20the%20following%20formula%3A%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%0A%3CP%3EX%2F(N*Y)%20%3D%20per%20virtual%20processor%20SPECInt2006%20Rate%20value%3C%2FP%3E%0A%3CP%3EWhere%20X%20is%20the%20SPECInt2006%20rate%20value%20for%20the%20hypervisor%20host%20server%20%3CBR%20%2F%3EWhere%20N%20%3D%20the%20number%20of%20physical%20cores%20in%20the%20hypervisor%20host%20%3CBR%20%2F%3EWhere%20Y%20%3D%201%20if%20you%20will%20be%20deploying%201%3A1%20virtual%20processor-to-physical%20processor%20on%20the%20hypervisor%20host%20%3CBR%20%2F%3EWhere%20Y%20%3D%202%20if%20you%20will%20be%20deploying%20up%20to%202%3A1%20virtual%20processor-to-physical%20processor%20on%20the%20hypervisor%20host%3C%2FP%3E%0A%3C%2FBLOCKQUOTE%3E%0A%3CP%3EFor%20example%2C%20let%E2%80%99s%20say%20I%20am%20deploying%20an%20HP%20ProLiant%20DL580%20G7%20(2.27%20GHz%2C%20Intel%20Xeon%20X7560)%20system%20which%20includes%20four%20sockets%2C%20each%20containing%20an%208-core%20processor%2C%20then%20the%20SPECInt2006%20rate%20value%20for%20the%20system%20is%20757.%3C%2FP%3E%0A%3CP%3EIf%20I%20am%20deploying%20my%20Mailbox%20server%20role%20as%20a%20guest%20machine%20using%20Hyper-V%2C%20and%20following%20best%20practices%20where%20I%20do%20not%20oversubscribed%20the%20number%20of%20virtual%20CPUs%20to%20physical%20processors%2C%20then%3C%2FP%3E%0A%3CP%3E757%2F(32*1)%20%3D%2023.66%3C%2FP%3E%0A%3CP%3ESince%20each%20Mailbox%20server%20will%20have%20a%20maximum%20of%204%20virtual%20processors%2C%20this%20means%20the%20SPECInt2006%20rate%20value%20I%20would%20enter%20into%20the%20calculator%20would%20be%2023.66*4%20%3D%2095.%3C%2FP%3E%0A%3CP%3EIn%20addition%2C%20if%20you%20are%20deploying%20your%20Exchange%20servers%20as%20guest%20machines%2C%20you%20can%20specify%20the%20Hypervisor%20CPU%20Adjustment%20Factor%20to%20take%20into%20account%20the%20overhead%20of%20deploying%20guest%20machines.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%3CA%20href%3D%22https%3A%2F%2Fhelpcenter.xactlycorp.com%2Flegacyfs%2Fonline%2Fmedia%2FTNBlogsFS%2Fprod.evol.blogs.technet.com%2FCommunityServer.Blogs.Components.WeblogFiles%2F00%2F00%2F00%2F31%2F06%2F6886.5.JPG%22%20original-url%3D%22http%3A%2F%2Fblogs.technet.com%2Fcfs-file.ashx%2F__key%2Fcommunityserver-blogs-components-weblogfiles%2F00-00-00-31-06%2F6886.5.JPG%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%22%3E%3CIMG%20src%3D%22http%3A%2F%2Fmigration9.stage.lithium.com%2Fskins%2Fimages%2FAF7D1A50469BCCC446F7CEAA2F38CF9E%2Fresponsive_peak%2Fimages%2Fimage_not_found.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FA%3E%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EServer%20Configuration%3C%2FSTRONG%3E%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3E%3CEM%3EHow%20many%20processor%20cores%20and%20what%20is%20their%20megacycle%20capability%20are%20you%20planning%20to%20deploy%20in%20each%20server%3F%3C%2FEM%3EFor%20each%20server%20type%20(primary%20datacenter%2C%20secondary%20datacenter%2C%20and%20lagged%20copy%20server)%20you%20plan%20to%20deploy%2C%20select%20the%20number%20of%20processor%20cores%20and%20the%20server%E2%80%99s%20SPECint2006%20rate%20value.%26nbsp%3B%20To%20determine%20your%20SPECint2006%20Rate%20Value%3A%3COL%3E%0A%3CLI%3EOpen%20a%20web%20browser%20and%20got%20to%20%3CA%20href%3D%22http%3A%2F%2Fwww.spec.org%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3Ewww.spec.org%3C%2FA%3E.%3C%2FLI%3E%0A%3CLI%3EClick%20on%20Results%2C%20highlight%20CPU2006%20and%20then%20select%20Search%20CPU2006%20Results.%3C%2FLI%3E%0A%3CLI%3EUnder%20Available%20Configurations%2C%20select%20SPECint2006%20Rates%20and%20click%20Go.%26nbsp%3B%20Under%20Simple%20Request%2C%20enter%20the%20search%20criteria%20(e.g.%2C%20Processor%20matches%20x5550).%3C%2FLI%3E%0A%3CLI%3EFind%20the%20server%20and%20processor%20you%20are%20planning%20to%20deploy%20and%20take%20note%20of%20the%20result%20value.%20For%20example%2C%20let's%20say%20you%20are%20deploying%20a%20Dell%20PowerEdge%20M710%208-core%20server%20with%20Intel%20x5550%202.67GHz%20processors%20(2670%20Hertz)%3B%20the%20SPECint_rate2006%20results%20value%20is%20240.%3C%2FLI%3E%0A%3C%2FOL%3E%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3E%3CSTRONG%3ELog%20Replication%20Configuration%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EWithin%20Step%206%2C%20you%20will%20define%20your%20hourly%20log%20generation%20rate%2C%20the%20network%20link%2C%20and%20the%20network%20link%20latency%20you%20expect%20to%20have%20within%20your%20site%20resilient%20architecture.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fhelpcenter.xactlycorp.com%2Flegacyfs%2Fonline%2Fmedia%2FTNBlogsFS%2Fprod.evol.blogs.technet.com%2FCommunityServer.Blogs.Components.WeblogFiles%2F00%2F00%2F00%2F31%2F06%2F4760.6.JPG%22%20original-url%3D%22http%3A%2F%2Fblogs.technet.com%2Fcfs-file.ashx%2F__key%2Fcommunityserver-blogs-components-weblogfiles%2F00-00-00-31-06%2F4760.6.JPG%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%22%3E%3CIMG%20src%3D%22http%3A%2F%2Fmigration9.stage.lithium.com%2Fskins%2Fimages%2FAF7D1A50469BCCC446F7CEAA2F38CF9E%2Fresponsive_peak%2Fimages%2Fimage_not_found.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FA%3E%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3E%3CEM%3EHow%20many%20transaction%20logs%20are%20generated%20for%20each%20hour%20in%20the%20day%3F%3C%2FEM%3E%20Enter%20in%20the%20percentage%20of%20transaction%20logs%20that%20are%20generated%20for%20each%20hour%20in%20the%20day%20by%20measuring%20an%20existing%20Exchange%202003%20or%20Exchange%202007%20server%20in%20your%20environment.%20If%20the%20existing%20messaging%20environment%20is%20not%20using%20Exchange%2C%20then%20evaluate%20the%20messaging%20environment%20and%20enter%20in%20the%20rate%20of%20change%20per%20hour%20here.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3ENow%20you%20may%20be%20wondering%20how%20you%20can%20collect%20this%20data.%20We've%20written%20a%20simple%20VBS%20script%20that%20will%20collect%20all%20files%20in%20a%20folder%20and%20output%20it%20to%20a%20log%20file.%20You%20can%20use%20Task%20Scheduler%20to%20execute%20this%20script%20at%20certain%20intervals%20in%20the%20day%20(e.g.%20every%2015%20minutes).%20Once%20you%20have%20generated%20the%20log%20file%20for%20a%2024%20hour%20period%2C%20you%20can%20import%20it%20into%20Excel%2C%20massage%20the%20data%20(i.e.%20remove%20duplicate%20entries)%20and%20determine%20how%20many%20logs%20are%20generated%20for%20each%20hour.%20If%20you%20do%20this%20for%20each%20storage%20group%2C%20you%20will%20be%20able%20to%20determine%20your%20log%20generation%20rate%20for%20each%20hour%20in%20the%20day.%20This%20script%20is%20named%20collectlogs.vbsrename%20(just%20rename%20it%20to%20collectlogs.vbs)%20and%20you%20can%20find%20it%20here%3A%20%3CA%20href%3D%22http%3A%2F%2Fgallery.technet.microsoft.com%2Fscriptcenter%2F7ae3af04-07f2-4263-b194-926cb170c5e9%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3ECollectlogs%20VBS%20script%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ENetwork%20Configuration%3C%2FSTRONG%3E%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3E%3CEM%3EWhat%20type%20of%20network%20link%20will%20you%20be%20using%20between%20the%20servers%3F%3C%2FEM%3E%20Select%20the%20appropriate%20network%20link%20you%20will%20be%20using%20between%20the%20two%20datacenters.%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EWhat%20is%20the%20latency%20on%20the%20network%20link%3F%3C%2FEM%3E%20Enter%20in%20the%20latency%20(in%20milliseconds)%20that%20exists%20on%20the%20network%20link.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CH2%20id%3D%22toc-hId-950706614%22%20id%3D%22toc-hId--1601447494%22%3E%3CSTRONG%3ERole%20Requirements%3C%2FSTRONG%3E%3C%2FH2%3E%0A%3CP%3EThis%20section%20provides%20the%20solution's%20I%2FO%2C%20capacity%2C%20memory%2C%20and%20CPU%20requirements.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fhelpcenter.xactlycorp.com%2Flegacyfs%2Fonline%2Fmedia%2FTNBlogsFS%2Fprod.evol.blogs.technet.com%2FCommunityServer.Blogs.Components.WeblogFiles%2F00%2F00%2F00%2F31%2F06%2Fmetablogapi%2F2133.rolereq_74B86F57.png%22%20original-url%3D%22http%3A%2F%2Fblogs.technet.com%2Fcfs-file.ashx%2F__key%2Fcommunityserver-blogs-components-weblogfiles%2F00-00-00-31-06-metablogapi%2F2133.rolereq_5F00_74B86F57.png%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3E%3CIMG%20style%3D%22background-image%3A%20none%3B%20padding-top%3A%200px%3B%20padding-left%3A%200px%3B%20display%3A%20inline%3B%20padding-right%3A%200px%3B%20border%3A%200px%3B%22%20title%3D%22rolereq%22%20src%3D%22http%3A%2F%2Fmigration9.stage.lithium.com%2Flegacyfs%2Fonline%2Fmedia%2FTNBlogsFS%2Fprod.evol.blogs.technet.com%2FCommunityServer.Blogs.Components.WeblogFiles%2F00%2F00%2F00%2F31%2F06%2Fmetablogapi%2F6254.rolereq_thumb_72124457.png%22%20original-url%3D%22http%3A%2F%2Fblogs.technet.com%2Fcfs-file.ashx%2F__key%2Fcommunityserver-blogs-components-weblogfiles%2F00-00-00-31-06-metablogapi%2F6254.rolereq_5F00_thumb_5F00_72124457.png%22%20alt%3D%22rolereq%22%20width%3D%22518%22%20height%3D%22480%22%20border%3D%220%22%20%2F%3E%3C%2FA%3E%3C%2FP%3E%0A%3CP%3EBased%20on%20the%20above%20input%20factors%20the%20calculator%20will%20recommend%20the%20following%20architecture%2C%20broken%20down%20into%20four%20sections%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EEnvironment%20Configuration%3C%2FLI%3E%0A%3CLI%3EActive%20Database%20Copy%20Configuration%3C%2FLI%3E%0A%3CLI%3EServer%20Configuration%3C%2FLI%3E%0A%3CLI%3ELog%2C%20Disk%20Space%2C%20and%20IO%20Requirements%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSTRONG%3EProcessor%20Core%20Ratio%20Requirements%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EThis%20table%20identifies%20the%20required%20number%20of%20processor%20cores%20required%20to%20support%20the%20activated%20databases.%20This%20table%20is%20only%20populated%20if%20you%20populate%20the%20processor%20core%20megacycle%20information%20on%20the%20Input%20tab.%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EThe%20Recommended%20Minimum%20Number%20of%20Global%20Catalog%20Cores%20identifies%20the%20minimum%20number%20of%20processor%20cores%20required%20to%20sustain%20the%20load%20for%20global%20catalog%20related%20activities%20and%20is%20based%20on%20the%20number%20of%20processor%20cores%20required%20to%20support%20the%20activated%20databases.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSTRONG%3EClient%20Access%20Server%20Requirements%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EThis%20table%20identifies%20the%20memory%20and%20CPU%20requirements%20for%20dedicated%20Client%20Access%20servers%20if%20you%20choose%20to%20not%20co-locate%20the%20server%20roles.%20This%20table%20is%20only%20populated%20if%20you%20populate%20the%20processor%20core%20megacycle%20information%20on%20the%20Input%20tab.%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EThe%20Recommended%20Minimum%20Number%20of%20Client%20Access%20Processor%20Cores%20identifies%20the%20minimum%20number%20of%20processor%20cores%20required%20per%20server%20to%20sustain%20the%20load%20for%20client%20related%20activities.%3C%2FLI%3E%0A%3CLI%3EThe%20Recommended%20Minimum%20Number%20of%20Client%20Access%20Server%20RAM%20Configuration%20identifies%20the%20minimum%20amount%20of%20memory%20required%20per%20server%20to%20sustain%20the%20load%20for%20client%20related%20activities.%20This%20number%20is%20scaled%20to%20a%20multiple%20that%20can%20be%20typically%20installed%20in%20a%20server.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSTRONG%3EHub%20Transport%20Server%20Requirements%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EThis%20table%20identifies%20the%20memory%20and%20CPU%20requirements%20for%20dedicated%20Hub%20Transport%20servers%20if%20you%20choose%20to%20not%20co-locate%20the%20server%20roles.%20This%20table%20is%20only%20populated%20if%20you%20populate%20the%20processor%20core%20megacycle%20information%20on%20the%20Input%20tab.%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EThe%20Recommended%20Minimum%20Number%20of%20Hub%20Transport%20Processor%20Cores%20identifies%20the%20minimum%20number%20of%20processor%20cores%20required%20per%20server%20to%20sustain%20the%20load%20for%20client%20related%20activities.%3C%2FLI%3E%0A%3CLI%3EThe%20Recommended%20Minimum%20Number%20of%20Hub%20Transport%20RAM%20Configuration%20identifies%20the%20minimum%20amount%20of%20memory%20required%20per%20server%20to%20sustain%20the%20load%20for%20client%20related%20activities.%20This%20number%20is%20scaled%20to%20a%20multiple%20that%20can%20be%20typically%20installed%20in%20a%20server.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSTRONG%3EEnvironment%20Configuration%20%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EThe%20Environment%20Configuration%20table%20identifies%20the%20number%20of%20mailboxes%20being%20deployed%20in%20each%20datacenter%2C%20as%20well%20as%2C%20how%20many%20mailbox%20servers%20and%20lagged%20copy%20servers%20you%20will%20deploy%20in%20each%20datacenter.%26nbsp%3B%26nbsp%3B%20This%20table%20will%20also%20identify%20the%20minimum%20number%20of%20dedicated%20Hub%20Transport%20and%20Client%20Access%20servers%20you%20should%20deploy%20in%20each%20datacenter%20(taking%20into%20account%20worst%20case%20failure%20mode%20of%20two%20simultaneous%20server%20failures).%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EUser%20Mailbox%20Configuration%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EThe%20Mailbox%20Configuration%20table%20provides%20you%20with%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EThe%20Number%20of%20Mailboxes%20that%20you%20entered%20in%20the%20Input%20section%20(this%20value%20will%20include%20the%20projected%20growth).%3C%2FLI%3E%0A%3CLI%3EThe%20Number%20of%20Mailboxes%20%2F%20Database%20provides%20a%20breakdown%20of%20how%20many%20mailboxes%20from%20each%20mailbox%20tier%20will%20be%20stored%20within%20a%20database.%3C%2FLI%3E%0A%3CLI%3EThe%20User%20Mailbox%20Size%20within%20Database%20is%20the%20actual%20mailbox%20size%20on%20disk%20that%20factors%20in%20the%20prohibit%20send%2Freceive%20limit%2C%20the%20number%20of%20messages%20the%20user%20sends%2Freceives%20per%20day%2C%20the%20deleted%20item%20retention%20window%20(with%20or%20without%20calendar%20version%20logging%20and%20single%20item%20recovery%20enabled)%2C%20and%20the%20average%20database%20daily%20churn%20per%20mailbox.%20It%20is%20important%20to%20note%20that%20the%20Mailbox%20size%20on%20disk%20is%20actually%20higher%20than%20your%20mailbox%20size%20limit%3B%20this%20is%20to%20be%20expected.%3C%2FLI%3E%0A%3CLI%3EThe%20Transaction%20Logs%20Generated%20%2F%20Mailbox%20value%20is%20based%20on%20the%20message%20profile%20selected%20and%20the%20average%20message%20size%20and%20indicates%20how%20many%20transaction%20logs%20will%20be%20generated%20per%20mailbox%20per%20day.%20The%20log%20generation%20numbers%20per%20message%20profile%20account%20for%3A%3CUL%3E%0A%3CLI%3EMessage%20size%20impact.%20In%20our%20analysis%20of%20the%20databases%20internally%20we%20have%20found%20that%2090%25%20of%20the%20database%20is%20the%20attachments%20and%20message%20tables%20(message%20bodies%20and%20attachments).%20So%20if%20the%20average%20message%20size%20doubles%20(from%2075%20to%20150)%2C%20the%20worst%20case%20scenario%20would%20be%20for%20the%20log%20traffic%20to%20increase%20by%201.9%20times.%20Thereafter%2C%20as%20message%20size%20doubles%2C%20the%20impact%20doubles.%3C%2FLI%3E%0A%3CLI%3EAmount%20of%20data%20Sent%2Freceived.%3C%2FLI%3E%0A%3CLI%3EDatabase%20health%20maintenance%20operations.%3C%2FLI%3E%0A%3CLI%3ERecords%20Management%20operations%3C%2FLI%3E%0A%3CLI%3EData%20stored%20in%20mailbox%20that%20is%20not%20a%20message%20(tasks%2C%20local%20calendar%20appts%2C%20contacts%2C%20etc).%3C%2FLI%3E%0A%3CLI%3EForced%20log%20rollover%20(a%20mechanism%20that%20periodically%20closes%20the%20current%20transaction%20log%20file%20and%20creates%20the%20next%20generation).%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FLI%3E%0A%3CLI%3EThe%20IOPS%20%2F%20Mailbox%20value%20is%20the%20calculated%20IOPS%20%2F%20Mailbox%20value%20that%20is%20based%20on%20the%20number%20of%20messages%20per%20mailbox%2C%20the%20user%20memory%20profile%2C%20and%20desktop%20search%20engine%20choices.%20If%20you%20had%20chosen%20to%20enter%20in%20a%20specific%20IOPS%20%2F%20mailbox%20value%20rather%20than%20allowing%20the%20calculator%20determining%20the%20value%20based%20on%20the%20above%20requirements%2C%20then%20this%20value%20will%20be%20that%20custom%20value.%3C%2FLI%3E%0A%3CLI%3EThe%20Read%3AWrite%20ratio%20%2F%20Mailbox%20value%20defines%20the%20ratio%20of%20the%20mailbox's%20IOPS%20that%20are%20read%20I%2FOs.%20This%20information%20is%20required%20to%20accurately%20design%20the%20storage%20subsystem%20I%2FO%20requirements.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSTRONG%3EDatabase%20Copy%20Instance%20Configuration%20%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EThis%20table%20highlights%20how%20many%20HA%20mailbox%20database%20copy%20instances%20and%20lagged%20database%20copy%20instances%20your%20solution%20will%20have%20within%20each%20datacenter%20for%20a%20given%20DAG.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EDatabase%20Configuration%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EThe%20Database%20Configuration%20table%20provides%20you%20with%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EThe%20Number%20of%20Databases%20is%20the%20calculated%20number%20of%20databases%20required%20to%20support%20the%20mailbox%20population%20within%20a%20standalone%20server%20or%20DAG.%3C%2FLI%3E%0A%3CLI%3EThe%20Recommended%20Number%20of%20Mailboxes%20%2F%20Database%20is%20the%20calculated%20number%20of%20mailboxes%20per%20database%20ensuring%20that%20the%20database%20size%20does%20not%20go%20above%20the%20recommended%20database%20size%20limit.%3C%2FLI%3E%0A%3CLI%3EThe%20Available%20Database%20Cache%20%2F%20Mailbox%20value%20is%20the%20amount%20of%20database%20cache%20memory%20that%20is%20available%20per%20mailbox.%20A%20large%20database%20cache%20ensures%20that%20read%20I%2FOs%20can%20be%20reduced.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSTRONG%3EDatabase%20Copy%20Configuration%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EThe%20Database%20Copy%20Configuration%20table%20provides%20you%20with%20the%20number%20of%20database%20copies%20being%20deployed%20within%20each%20server%20and%20the%20total%20number%20of%20database%20copies%20within%20the%20DAG.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EServer%20Configuration%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EThe%20Server%20Configuration%20table%20provides%20you%20with%20the%20following%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EThe%20Recommended%20RAM%20Configuration%20for%20the%20primary%20datacenter%20mailbox%20servers%2C%20secondary%20datacenter%20mailbox%20servers%2C%20and%20lagged%20copy%20servers.%20This%20is%20the%20amount%20of%20RAM%20needed%20to%20support%20the%20number%20of%20maximum%20activated%20database%20copies%20on%20a%20given%20server%2C%20in%20addition%20to%2C%20the%20number%20of%20mailboxes%20based%20on%20their%20memory%20profile.%3C%2FLI%3E%0A%3CLI%3EThe%20number%20of%20processor%20cores%20utilized%20during%20the%20worst%20failure%20mode%20scenario.%3C%2FLI%3E%0A%3CLI%3EThe%20CPU%20Utilization%20value%20is%20the%20expected%20CPU%20Utilization%20for%20a%20fully%20utilized%20server%20based%20on%20the%20megacycles%20associated%20with%20the%20user%20profile%20and%20the%20number%20of%20database%20copies.%20Depending%20on%20the%20environment%2C%20this%20will%20either%20be%20for%20a%20standalone%20server%20hosting%20100%25%20active%20databases%2C%20or%20a%20server%20participating%20in%20a%20DAG%20that%20is%20dealing%20with%20a%20single%20or%20double%20server%20failure%20event%20(or%20secondary%20datacenter%20activation).%20It%20is%20recommended%20that%20servers%20not%20exceed%2080%25%20utilization%20during%20peak%20period.%20The%20CPU%20utilization%20value%20is%20determined%20by%20taking%20the%20CPU%20Megacycle%20Requirements%20and%20dividing%20it%20by%20the%20total%20number%20of%20megacycles%20available%20on%20the%20server%20(which%20is%20based%20on%20the%20CPU%20and%20number%20of%20cores).%20If%20the%20calculator%20highlights%20the%20CPU%20utilization%20with%20a%20red%20background%2C%20then%20this%20means%20the%20design%20may%20not%20be%20able%20to%20sustain%20the%20load%20-%20either%20you%20must%20change%20the%20design%20(number%20of%20mailboxes%2C%20number%20of%20copies%2C%20etc.)%20or%20change%20the%20server%20CPU%20platform.%3C%2FLI%3E%0A%3CLI%3EThe%20CPU%20Megacycle%20Requirements%20value%20defines%20the%20amount%20of%20megacycles%20the%20primary%20datacenter%20servers%20must%20be%20able%20to%20sustain%20when%20either%20all%20mailbox%20databases%20are%20active%20or%20the%20number%20of%20mailbox%20database%20copies%20that%20are%20activated%20based%20on%20a%20single%20server%20or%20double%20server%20failure%20event.%20For%20secondary%20servers%20hosting%20HA%20copies%2C%20this%20value%20defines%20the%20amount%20of%20megacycles%20required%20to%20support%20the%20activation%20of%20all%20databases%20after%20datacenter%20activation.%20For%20lagged%20copy%20servers%2C%20this%20value%20defines%20the%20amount%20of%20megacycles%20required%20to%20support%20all%20of%20the%20passive%20lagged%20copies.%3C%2FLI%3E%0A%3CLI%3EThe%20Server%20Total%20Available%20Adjusted%20Megacycles%20value%20defines%20the%20total%20available%20megacycles%20the%20server%20platform%20is%20capable%20of%20delivering%20at%20100%25%20CPU%20utilization.%26nbsp%3B%20This%20value%20has%20been%20normalized%20against%20the%20baseline%20server%20platform%20(Intel%20Xeon%20x5470%202x4%203.33GHZ%20processors).%3C%2FLI%3E%0A%3CLI%3EThe%20Possible%20Storage%20Architecture%20outlines%20whether%20the%20solution%20could%20utilize%20RAID%20or%20JBOD%20for%20the%20primary%20datacenter%20servers%2C%20secondary%20datacenter%20servers%2C%20and%20lagged%20copy%20servers.%20JBOD%20is%20only%20considered%20under%20the%20following%20conditions%20(this%20assumes%20you%20configured%20the%20calculator%20to%20consider%20JBOD)%3A%3CUL%3E%0A%3CLI%3EIn%20order%20to%20deploy%20on%20JBOD%20in%20the%20primary%20datacenter%20servers%3A%20You%20need%20a%20total%20of%203%20or%20more%20HA%20copies%20within%20the%20DAG.%20If%20you%20are%20mixing%20lagged%20copies%20on%20the%20same%20server%20that%20is%20hosting%20your%20HA%20copies%20(i.e.%20not%20using%20dedicated%20lagged%20copy%20servers)%2C%20then%20you%20need%20at%20least%202%20lagged%20copies.%3C%2FLI%3E%0A%3CLI%3EFor%20the%20secondary%20datacenter%20servers%20to%20use%20JBOD%3A%20You%20should%20have%20at%20least%202%20HA%20copies%20in%20secondary%20datacenter.%20That%20way%20loss%20of%20a%20copy%20in%20the%20secondary%20datacenter%20doesn't%20result%20in%20requiring%20a%20reseed%20across%20the%20WAN%20or%20loss%20of%20data%20(in%20the%20datacenter%20activation%20case).%20If%20you%20are%20mixing%20lagged%20copies%20on%20the%20same%20server%20that%20is%20hosting%20your%20HA%20copies%20(i.e.%20not%20using%20dedicated%20lagged%20copy%20servers)%2C%20then%20you%20need%20at%20least%202%20lagged%20copies.%3C%2FLI%3E%0A%3CLI%3EFor%20dedicated%20lagged%20copy%20servers%3A%20You%20should%20have%20at%20least%202%20lagged%20copies%20within%20a%20datacenter%20in%20order%20to%20use%20JBOD.%20Otherwise%20loss%20of%20disk%20results%20in%20loss%20of%20your%20lagged%20copy%20(and%20whatever%20protection%20mechanism%20that%20was%20providing).%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSTRONG%3ETransaction%20Log%20Requirements%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EThe%20Transaction%20Log%20Requirements%20table%20provides%20you%20with%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EThe%20User%20Transaction%20Logs%20Generated%20%2F%20Day%20indicates%20how%20many%20transaction%20logs%20will%20be%20generated%20during%20the%20day%20for%20each%20active%20database%2C%20each%20server%2C%20within%20the%20DAG%2C%20and%20within%20the%20environment.%3C%2FLI%3E%0A%3CLI%3EThe%20Average%20Mailbox%20Move%20Transaction%20Logs%20Generated%20%2F%20Day%20indicates%20how%20many%20transaction%20logs%20will%20be%20generated%20during%20the%20day%20for%20active%20database%2C%20each%20server%2C%20within%20a%20DAG%2C%20and%20within%20the%20environment.%20This%20number%20is%20an%20assumption%20and%20assumes%20that%20an%20equal%20percentage%20of%20mailboxes%20will%20be%20moved%20each%20day%2C%20as%20opposed%20to%20moving%20all%20mailboxes%20on%20the%20same%20day.%3C%2FLI%3E%0A%3CLI%3EThe%20Average%20Transaction%20Logs%20Generated%20%2F%20Day%20is%20the%20total%20number%20of%20transaction%20logs%20that%20are%20generated%20per%20day%20for%20active%20database%2C%20each%20server%2C%20within%20a%20DAG%2C%20and%20within%20the%20environment%20(includes%20user%20generated%20logs%20and%20mailbox%20move%20generated%20logs).%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSTRONG%3EDisk%20Space%20Requirements%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EThe%20Disk%20Space%20Requirements%20table%20provides%20you%20with%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EThe%20Database%20Space%20Required%20is%20the%20amount%20of%20space%20required%20to%20support%20each%20database%20and%20its%20corresponding%20copies.%20This%20value%20is%20derived%20from%20the%20mailbox%20size%20on%20disk%2C%20the%20data%20overhead%20factor%2C%20whether%20a%20dedicated%20restore%20LUN%20is%20available.%20This%20row%20also%20shows%20you%20the%20space%20requirements%20for%20each%20server%20(based%20on%20the%20total%20number%20of%20database%20copies)%2C%20each%20DAG%2C%20and%20within%20the%20environment.%3C%2FLI%3E%0A%3CLI%3EThe%20Log%20Space%20Required%20is%20the%20amount%20of%20space%20required%20to%20support%20each%20database%20log%20stream%20and%20the%20corresponding%20copies.%20This%20value%20takes%20into%20account%20the%20number%20of%20mailboxes%20moved%20per%20week%20(assumes%20worst%20case%20and%20that%20all%20mailboxes%20are%20moved%20on%20the%20same%20day)%2C%20the%20type%20of%20backup%20frequency%20in%20use%2C%20the%20number%20of%20days%20that%20can%20be%20tolerated%20without%20log%20truncation%20and%20the%20number%20of%20transaction%20logs%20generated%20per%20day.%20This%20row%20also%20shows%20you%20the%20space%20requirements%20for%20each%20server%20(based%20on%20the%20total%20number%20of%20database%20copies)%2C%20each%20DAG%2C%20and%20within%20the%20environment.%3C%2FLI%3E%0A%3CLI%3EThe%20Database%20LUN%20Space%20Required%20is%20the%20LUN%20size%20required%20to%20support%20the%20database%20(and%20potentially%20its%20log%20stream).%20This%20calculation%20takes%20the%20total%20disk%20space%20required%20for%20the%20database%20and%20adds%20to%20it%20the%20size%20of%20a%20database%20plus%20110%25%20(if%20a%20dedicated%20restore%20LUN%20does%20not%20exist)%20for%20offline%20maintenance%20operations%2C%20an%20additional%2010%25%20of%20the%20database%20size%20for%20content%20indexing%20(if%20enabled)%2C%20and%20includes%20an%20amount%20of%20free%20space%20to%20ensure%20the%20LUN%20is%20not%20100%25%20utilized%20(based%20on%20LUN%20Free%20Space%20Percentage).%20This%20row%20also%20shows%20you%20the%20space%20requirements%20for%20each%20server%20(based%20on%20the%20total%20number%20of%20database%20copies)%2C%20each%20DAG%2C%20and%20within%20the%20environment.%3C%2FLI%3E%0A%3CLI%3EThe%20Log%20LUN%20Space%20Required%20is%20the%20LUN%20size%20required%20to%20support%20the%20databases%20log%20stream.%20This%20field%20lists%20the%20amount%20of%20space%20required%20to%20support%20the%20transaction%20logs%20for%20a%20given%20set%20of%20databases%20and%20includes%20an%20amount%20of%20free%20space%20to%20ensure%20the%20LUN%20is%20not%20100%25%20utilized%20(based%20on%20LUN%20Free%20Space%20Percentage).%20This%20row%20also%20shows%20you%20the%20space%20requirements%20for%20each%20server%20(based%20on%20the%20total%20number%20of%20database%20copies)%2C%20each%20DAG%2C%20and%20within%20the%20environment.%3C%2FLI%3E%0A%3CLI%3EThe%20Restore%20LUN%20Space%20Required%20is%20the%20amount%20of%20space%20needed%20to%20support%20a%20restore%20LUN%20if%20the%20option%20was%20selected%20in%20the%20Input%20Factor%20section%3B%20this%20will%20include%20space%20for%20up%20to%207%20databases%20and%207%20transaction%20log%20sets.%20Each%20server%20will%20be%20provisioned%20with%20a%20restore%20LUN.%20This%20row%20also%20shows%20you%20the%20space%20requirements%20for%20each%20server%20(based%20on%20the%20total%20number%20of%20database%20copies)%2C%20each%20DAG%2C%20and%20within%20the%20environment.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSTRONG%3EHost%20IO%20and%20Throughput%20Performance%20Requirements%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EThe%20Host%20IO%20and%20Throughput%20Performance%20Requirements%20table%20provides%20you%20with%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EThe%20Total%20Required%20Database%20IOPS%20is%20the%20amount%20of%20read%20and%20write%20host%20I%2FO%20the%20database%20disk%20set%20must%20sustain%20during%20peak%20load%20(this%20does%20not%20factor%20in%20any%20RAID%20penalties).%20This%20row%20also%20shows%20you%20the%20IOPS%20requirements%20for%20each%20server%20(based%20on%20the%20total%20number%20of%20database%20copies)%2C%20each%20DAG%2C%20and%20within%20the%20environment%3C%2FLI%3E%0A%3CLI%3EThe%20Total%20Required%20Log%20IOPS%20is%20the%20amount%20of%20read%20and%20write%20host%20I%2FO%20that%20will%20occur%20against%20the%20transaction%20log%20disk%20set.%20This%20row%20also%20shows%20you%20the%20IOPS%20requirements%20for%20each%20server%20(based%20on%20the%20total%20number%20of%20database%20copies)%2C%20each%20DAG%2C%20and%20within%20the%20environment.%3C%2FLI%3E%0A%3CLI%3EThe%20Database%20Read%20I%2FO%20Percentage%20defines%20the%20percentage%20of%20database%20required%20IOPS%20that%20are%20read%20I%2FOs.%20This%20information%20is%20required%20to%20accurately%20design%20the%20storage%20subsystem%20I%2FO%20requirements.%3C%2FLI%3E%0A%3CLI%3EThe%20amount%20of%20throughput%20required%20for%20Background%20Database%20Maintenance%20operations.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSTRONG%3ESpecial%20Notes%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EThe%20Special%20Notes%20table%20will%20provide%20you%20with%20additional%20information%20about%20your%20design%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EWhen%20to%20use%20GPT%20disks%20(when%20a%20LUN%20size%20is%20greater%20than%202TB).%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CH2%20id%3D%22toc-hId--1601450347%22%20id%3D%22toc-hId-141362841%22%3EActivation%20Scenarios%3C%2FH2%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fhelpcenter.xactlycorp.com%2Flegacyfs%2Fonline%2Fmedia%2FTNBlogsFS%2Fprod.evol.blogs.technet.com%2FCommunityServer.Blogs.Components.WeblogFiles%2F00%2F00%2F00%2F31%2F06%2F1614.8.JPG%22%20original-url%3D%22http%3A%2F%2Fblogs.technet.com%2Fcfs-file.ashx%2F__key%2Fcommunityserver-blogs-components-weblogfiles%2F00-00-00-31-06%2F1614.8.JPG%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%22%3E%3CIMG%20src%3D%22http%3A%2F%2Fmigration9.stage.lithium.com%2Fskins%2Fimages%2FAF7D1A50469BCCC446F7CEAA2F38CF9E%2Fresponsive_peak%2Fimages%2Fimage_not_found.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FA%3E%3C%2FP%3E%0A%3CP%3EIf%20you%20are%20deploying%20a%20highly%20available%20and%2For%20site%20resilient%20architecture%2C%20then%20this%20section%20will%20break%20down%20the%20failure%20scenarios.%26nbsp%3B%20The%20section%20is%20broken%20up%20into%20two%20scenarios%3A%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3EScenario%201%20-%20Deploying%20a%20DAG%20architecture%20within%20a%20single%20datacenter%20or%20deploying%20it%20in%20a%20site%20resilient%20Active%2FPassive%20user%20distribution%20model.%3C%2FLI%3E%0A%3CLI%3EScenario%202%20-%20Deploying%20a%20site%20resilient%20DAG%20architecture%20with%20an%20Active%2FActive%20user%20distribution%20model.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3E%3CSTRONG%3EImportant%3C%2FSTRONG%3E%3A%26nbsp%3B%20For%20the%20purposes%20of%20this%20calculator%2C%20the%20term%20%22primary%20datacenter%22%20refers%20to%20the%20datacenter%20that%20is%20preferred%20for%20hosting%20the%20active%20copies%20for%20a%20given%20set%20of%20databases%2C%20while%20the%20term%20%22secondary%20datacenter%22%20refers%20to%20the%20disaster%20recovery%20datacenter%20that%20is%20used%20for%20datacenter%20activation%20and%20cross-site%20database%20failover%20events.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ESingle%20Datacenter%20and%20Active%2FPassive%20Environments%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EThe%20DAG%20Member%20Layout%20table%20identifies%20the%20number%20of%20Active%20Mailbox%20servers%20(those%20that%20are%20hosting%20active%20mailboxes%20within%20the%20primary%20datacenter)%2C%20the%20Disaster%20Recovery%20Mailbox%20Servers%20(those%20that%20host%20passive%20database%20copies%20in%20the%20second%20datacenter)%2C%20and%20any%20Lagged%20Copy%20Mailbox%20servers%20you%20may%20be%20deploying.%3C%2FP%3E%0A%3CP%3EThere%20are%20two%20tables%20that%20provide%20data%20around%20the%20Active%20Database%20configuration%2C%20one%20for%20the%20primary%20datacenter%2C%20which%20outlines%20the%20single%20or%20double%20server%20events%2C%20and%20one%20for%20the%20secondary%20datacenter%2C%20which%20outlines%20the%20activation%20of%20that%20datacenter%20when%20the%20primary%20datacenter%20is%20lost.%20Both%20tables%20provide%20you%20with%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EThe%20Number%20of%20Active%20Databases%20(Normal%20Run%20Time)%20value%20defines%20the%20number%20of%20active%20databases%20hosted%20on%20each%20server%20when%20there%20are%20no%20server%20outages.%20Unlike%20Exchange%202007%2C%20Exchange%202010%20is%20no%20longer%20bound%20by%20an%20active%2Fpassive%20high%20availability%20model.%20Instead%2C%20each%20server%20within%20a%20DAG%20can%20host%20active%20mailbox%20database%20copies.%20The%20calculator%20distributes%20the%20number%20of%20unique%20databases%20across%20the%20primary%20datacenter%20servers%20within%20the%20DAG%2C%20ensuring%20an%20equal%20distribution%20of%20mailbox%20database%20copies%20are%20activated%20on%20each%20server.%20This%20row%20exposes%20the%20total%20number%20of%20mailboxes%20that%20are%20accessible%20on%20each%20server%20as%20a%20result%20of%20the%20activated%20database%20copies.%20In%20addition%2C%20this%20row%20highlights%20the%20total%20number%20of%20databases%20deployed%20within%20each%20datacenter%2C%20in%20the%20event%20that%20cross-site%20database%20*overs%20are%20allowed%20to%20occur.%3C%2FLI%3E%0A%3CLI%3EThe%20Number%20of%20Active%20Databases%20(After%20First%20Server%20Failure)%20value%20defines%20the%20number%20of%20active%20databases%20hosted%20on%20each%20server%20when%20there%20is%20a%20single%20server%20outage.%20As%20a%20result%20of%20the%20single%20server%20outage%2C%20the%20database%20copies%20that%20were%20activated%20on%20the%20failed%20server%20are%20equally%20redistributed%20across%20all%20remaining%20server%20nodes.%20This%20row%20exposes%20the%20total%20number%20of%20mailboxes%20that%20are%20accessible%20on%20each%20server%20as%20a%20result%20of%20the%20activated%20database%20copies.%20In%20addition%2C%20this%20row%20highlights%20the%20total%20number%20of%20databases%20deployed%20within%20each%20datacenter%2C%20in%20the%20event%20that%20cross-site%20database%20*overs%20are%20allowed%20to%20occur.%3C%2FLI%3E%0A%3CLI%3EThe%20Number%20of%20Active%20Databases%20(After%20Double%20Server%20Failure)%20value%20is%20populated%20when%20you%20have%20at%20least%203%20HA%20mailbox%20copies%20and%20at%20least%204%20mailbox%20servers%20within%20your%20design.%20It%20defines%20the%20number%20of%20active%20databases%20hosted%20on%20each%20server%20when%20there%20are%20two%20server%20outages.%20As%20a%20result%20of%20the%20double%20server%20outage%2C%20the%20database%20copies%20that%20were%20activated%20on%20the%20failed%20servers%20are%20equally%20redistributed%20across%20all%20remaining%20server%20nodes.%20This%20row%20exposes%20the%20total%20number%20of%20mailboxes%20that%20are%20accessible%20on%20each%20server%20as%20a%20result%20of%20the%20activated%20database%20copies.%20In%20addition%2C%20this%20row%20highlights%20the%20total%20number%20of%20databases%20deployed%20within%20each%20datacenter%2C%20in%20the%20event%20that%20cross-site%20database%20*overs%20are%20allowed%20to%20occur.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSTRONG%3EActive%2FActive%20Environments%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EThis%20section%20breaks%20out%20the%20architecture%20into%20two%20perspectives%2C%20the%20layout%20of%20Datacenter%201%20and%20the%20layout%20of%20Datacenter%202%20with%20respect%20to%20the%20DAG%20architecture.%26nbsp%3B%20Recall%20that%3C%2FP%3E%0A%3COL%3E%3C!--StartFragment--%3E%0A%3CLI%3EActive%2FActive%20(Single%20DAG)%20-%20This%20model%20stretches%20a%20DAG%20across%20the%20two%20datacenters%20and%20has%20active%20mailboxes%20located%20in%20each%20datacenter.%26nbsp%3B%20A%20corresponding%20passive%20copy%20is%20located%20in%20the%20alternate%20datacenter.%26nbsp%3B%20This%20scenario%20does%20have%20a%20single%20point%20of%20failure%20(potentially)%2C%20the%20WAN%20connection.%26nbsp%3B%20Loss%20of%20the%20WAN%20connection%20will%20result%20in%20the%20mailbox%20servers%20in%20one%20of%20the%20datacenters%20going%20into%20a%20failed%20state%20from%20a%20failover%20cluster%20perspective%20(due%20to%20loss%20of%20quorum)%3A%3CTABLE%20style%3D%22width%3A%20400px%3B%22%20border%3D%221%22%20cellspacing%3D%220%22%20cellpadding%3D%222%22%3E%0A%3CTBODY%3E%0A%3CTR%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22199%22%3E---DC1---%3C%2FTD%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22199%22%3E---DC2---%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22199%22%3EDAG1%3C%2FTD%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22199%22%3EDAG1%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22199%22%3EActive%20Copies%3C%2FTD%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22199%22%3EPassive%20Copies%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22199%22%3EPassive%20Copies%3C%2FTD%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22199%22%3EActive%20Copies%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3C%2FTBODY%3E%0A%3C%2FTABLE%3E%0A%3C%2FLI%3E%0A%3CLI%3EActive%2FActive%20(Multiple%20DAGs)%20-%20This%20model%20leverages%20multiple%20DAGs%20to%20remove%20single%20points%20of%20failure%20(e.g.%2C%20the%20WAN).%26nbsp%3B%20In%20this%20model%2C%20there%20are%20least%20two%20DAGs%2C%20with%20each%20DAG%20having%20its%20active%20copies%20in%20the%20alternate%20datacenter%3A%3CTABLE%20style%3D%22width%3A%20400px%3B%22%20border%3D%221%22%20cellspacing%3D%220%22%20cellpadding%3D%222%22%3E%0A%3CTBODY%3E%0A%3CTR%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22199%22%3E---DC1---%3C%2FTD%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22199%22%3E---DC2---%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22199%22%3EDAG-A%20(active%2Fpassive%20copies)%3C%2FTD%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22199%22%3EDAG-A%20(Passive%20Copies)%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22199%22%3EDAG-B%20(Passive%20Copies%3C%2FTD%3E%0A%3CTD%20valign%3D%22top%22%20width%3D%22199%22%3EDAG-B%20(Active%2FPassive%20Copies)%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3C%2FTBODY%3E%0A%3C%2FTABLE%3E%0A%3C!--EndFragment--%3E%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3EThe%20DAG%20Member%20Layout%20table%20identifies%20the%20number%20of%20Active%20Mailbox%20servers%20(those%20that%20are%20hosting%20active%20mailboxes%20within%20the%20primary%20datacenter)%2C%20the%20Disaster%20Recovery%20Mailbox%20Servers%20(those%20that%20host%20passive%20database%20copies%20in%20the%20second%20datacenter)%2C%20and%20any%20Lagged%20Copy%20Mailbox%20servers%20you%20may%20be%20deploying.%3C%2FP%3E%0A%3CP%3EThere%20are%20two%20tables%20that%20provide%20data%20around%20the%20Active%20Database%20configuration%2C%20one%20for%20the%20primary%20datacenter%2C%20which%20outlines%20the%20single%20or%20double%20server%20events%2C%20and%20one%20for%20the%20secondary%20datacenter%2C%20which%20outlines%20the%20activation%20of%20that%20datacenter%20when%20the%20primary%20datacenter%20is%20lost.%20Both%20tables%20provide%20you%20with%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EThe%20Number%20of%20Active%20Databases%20(Normal%20Run%20Time)%20value%20defines%20the%20number%20of%20active%20databases%20hosted%20on%20each%20server%20when%20there%20are%20no%20server%20outages.%20Unlike%20Exchange%202007%2C%20Exchange%202010%20is%20no%20longer%20bound%20by%20an%20active%2Fpassive%20high%20availability%20model.%20Instead%2C%20each%20server%20within%20a%20DAG%20can%20host%20active%20mailbox%20database%20copies.%20The%20calculator%20distributes%20the%20number%20of%20unique%20databases%20across%20the%20primary%20datacenter%20servers%20within%20the%20DAG%2C%20ensuring%20an%20equal%20distribution%20of%20mailbox%20database%20copies%20are%20activated%20on%20each%20server.%20This%20row%20exposes%20the%20total%20number%20of%20mailboxes%20that%20are%20accessible%20on%20each%20server%20as%20a%20result%20of%20the%20activated%20database%20copies.%20In%20addition%2C%20this%20row%20highlights%20the%20total%20number%20of%20databases%20deployed%20within%20each%20datacenter%2C%20in%20the%20event%20that%20cross-site%20database%20*overs%20are%20allowed%20to%20occur.%3C%2FLI%3E%0A%3CLI%3EThe%20Number%20of%20Active%20Databases%20(After%20First%20Server%20Failure)%20value%20defines%20the%20number%20of%20active%20databases%20hosted%20on%20each%20server%20when%20there%20is%20a%20single%20server%20outage.%20As%20a%20result%20of%20the%20single%20server%20outage%2C%20the%20database%20copies%20that%20were%20activated%20on%20the%20failed%20server%20are%20equally%20redistributed%20across%20all%20remaining%20server%20nodes.%20This%20row%20exposes%20the%20total%20number%20of%20mailboxes%20that%20are%20accessible%20on%20each%20server%20as%20a%20result%20of%20the%20activated%20database%20copies.%20In%20addition%2C%20this%20row%20highlights%20the%20total%20number%20of%20databases%20deployed%20within%20each%20datacenter%2C%20in%20the%20event%20that%20cross-site%20database%20*overs%20are%20allowed%20to%20occur.%3C%2FLI%3E%0A%3CLI%3EThe%20Number%20of%20Active%20Databases%20(After%20Double%20Server%20Failure)%20value%20is%20populated%20when%20you%20have%20at%20least%203%20HA%20mailbox%20copies%20and%20at%20least%204%20mailbox%20servers%20within%20your%20design.%20It%20defines%20the%20number%20of%20active%20databases%20hosted%20on%20each%20server%20when%20there%20are%20two%20server%20outages.%20As%20a%20result%20of%20the%20double%20server%20outage%2C%20the%20database%20copies%20that%20were%20activated%20on%20the%20failed%20servers%20are%20equally%20redistributed%20across%20all%20remaining%20server%20nodes.%20This%20row%20exposes%20the%20total%20number%20of%20mailboxes%20that%20are%20accessible%20on%20each%20server%20as%20a%20result%20of%20the%20activated%20database%20copies.%20In%20addition%2C%20this%20row%20highlights%20the%20total%20number%20of%20databases%20deployed%20within%20each%20datacenter%2C%20in%20the%20event%20that%20cross-site%20database%20*overs%20are%20allowed%20to%20occur.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CH2%20id%3D%22toc-hId-141359988%22%20id%3D%22toc-hId-1884173176%22%3EDistribution%3C%2FH2%3E%0A%3CP%3EThe%20calculator%20includes%20a%20new%20worksheet%2C%20Distribution.%20Within%20the%20Distribution%20worksheet%2C%20you%20will%20find%20the%20layout%20we%20recommend%20based%20on%20the%20database%20copy%20layout%20principles.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fhelpcenter.xactlycorp.com%2Flegacyfs%2Fonline%2Fmedia%2FTNBlogsFS%2Fprod.evol.blogs.technet.com%2FCommunityServer.Blogs.Components.WeblogFiles%2F00%2F00%2F00%2F31%2F06%2F8420.9.JPG%22%20original-url%3D%22http%3A%2F%2Fblogs.technet.com%2Fcfs-file.ashx%2F__key%2Fcommunityserver-blogs-components-weblogfiles%2F00-00-00-31-06%2F8420.9.JPG%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%22%3E%3CIMG%20src%3D%22http%3A%2F%2Fmigration9.stage.lithium.com%2Fskins%2Fimages%2FAF7D1A50469BCCC446F7CEAA2F38CF9E%2Fresponsive_peak%2Fimages%2Fimage_not_found.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FA%3E%3C%2FP%3E%0A%3CP%3EThe%20Distribution%20worksheet%20includes%20several%20new%20options%20to%20help%20you%20with%20designing%20and%20deploying%20your%20database%20copies%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EYou%20can%20determine%20what%20the%20active%20copy%20distribution%20will%20be%20like%20as%20server%20failures%20occur%20within%20your%20environment.%20%3CA%20href%3D%22https%3A%2F%2Fhelpcenter.xactlycorp.com%2Flegacyfs%2Fonline%2Fmedia%2FTNBlogsFS%2Fprod.evol.blogs.technet.com%2FCommunityServer.Blogs.Components.WeblogFiles%2F00%2F00%2F00%2F31%2F06%2F7282.10.JPG%22%20original-url%3D%22http%3A%2F%2Fblogs.technet.com%2Fcfs-file.ashx%2F__key%2Fcommunityserver-blogs-components-weblogfiles%2F00-00-00-31-06%2F7282.10.JPG%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%22%3E%3CIMG%20src%3D%22http%3A%2F%2Fmigration9.stage.lithium.com%2Fskins%2Fimages%2FAF7D1A50469BCCC446F7CEAA2F38CF9E%2Fresponsive_peak%2Fimages%2Fimage_not_found.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3EYou%20can%20export%20a%20set%20of%20CSV%20and%20PowerShell%20scripts%20that%20perform%20the%20following%20actions%3A%3CUL%3E%0A%3CLI%3EDiskpart.ps1%20(uses%20Servers.csv)%20-%20Formats%20the%20physical%20disks%2C%20and%20mounts%20them%20as%20mount%20points%20under%20an%20anchor%20directory%20on%20each%20server.%3C%2FLI%3E%0A%3CLI%3ECreateMBDatabases.ps1%20(uses%20MailboxDatabases.csv)%20-%20Creates%20the%20mailbox%20database%20copies%20with%20activation%20preference%20value%20of%201.%3C%2FLI%3E%0A%3CLI%3ECreateMBDatabaseCopies.ps1%20(uses%20MailboxDatabaseCopies.csv)%20-%20Creates%20the%20mailbox%20database%20copies%20with%20the%20appropriate%20activation%20preference%20values%20across%20the%20server%20infrastructure.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSTRONG%3EImportant%3C%2FSTRONG%3E%3A%20The%20database%20copy%20layout%20the%20tool%20provides%20assumes%20that%20each%20server%20and%20its%20associated%20database%20copies%20are%20isolated%20from%20each%20other%20server%2Fcopies.%20It%20is%20important%20to%20take%20into%20account%20failure%20domain%20aspects%20when%20planning%20your%20database%20copy%20layout%20architecture%20so%20that%20you%20can%20avoid%20having%20multiple%20copy%20failures%20for%20the%20same%20database%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1884170323%22%20id%3D%22toc-hId--667983785%22%3ELUN%20Design%3C%2FH2%3E%0A%3CP%3EThe%20LUN%20Requirements%20section%20is%20really%20a%20continuation%20of%20the%20Storage%20Requirements%20section.%20It%20outlines%20what%20we%20believe%20is%20the%20appropriate%20LUN%20design%20based%20on%20the%20input%20factors%20and%20the%20analysis%20performed%20in%20the%20previous%20sections.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ENote%3A%3C%2FSTRONG%3E%20The%20term%20LUN%20utilized%20in%20the%20calculator%20refers%20only%20the%20representation%20of%20the%20disk%20that%20is%20exposed%20to%20the%20host%20operating%20system.%20It%20does%20not%20define%20the%20disk%20configuration.%3C%2FP%3E%0A%3CP%3EThe%20LUN%20Design%20highlights%20the%20LUN%20architecture%20chosen%20for%20this%20server%20solution.%20The%20architecture%20is%20derived%20from%20the%20backup%20type%2C%20backup%20frequency%2C%20and%20high%20availability%20architecture%20that%20were%20chosen%20in%20the%20Storage%20Requirements%20section.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fhelpcenter.xactlycorp.com%2Flegacyfs%2Fonline%2Fmedia%2FTNBlogsFS%2Fprod.evol.blogs.technet.com%2FCommunityServer.Blogs.Components.WeblogFiles%2F00%2F00%2F00%2F31%2F06%2F4130.11.JPG%22%20original-url%3D%22http%3A%2F%2Fblogs.technet.com%2Fcfs-file.ashx%2F__key%2Fcommunityserver-blogs-components-weblogfiles%2F00-00-00-31-06%2F4130.11.JPG%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%22%3E%3CIMG%20src%3D%22http%3A%2F%2Fmigration9.stage.lithium.com%2Fskins%2Fimages%2FAF7D1A50469BCCC446F7CEAA2F38CF9E%2Fresponsive_peak%2Fimages%2Fimage_not_found.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FA%3E%3C%2FP%3E%0A%3CP%3EThere%20are%20three%20types%20of%20LUN%20architecture%20that%20can%20be%20leveraged%20within%20Exchange%202010%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E1%20LUN%20%2F%20Database%3C%2FLI%3E%0A%3CLI%3E2%20LUNs%20%2F%20Database%3C%2FLI%3E%0A%3CLI%3E2%20LUNs%20%2F%20Backup%20Set%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSTRONG%3E1%20LUN%20%2F%20Database%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EA%20single%20LUN%20per%20Database%20architecture%20means%20that%20both%20the%20database%20and%20its%20corresponding%20log%20files%20are%20placed%20on%20the%20same%20LUN.%20In%20order%20to%20deploy%20a%20LUN%20architecture%20that%20only%20utilizes%20a%20single%20LUN%20per%20database%2C%20you%20must%20have%20a%20Database%20Availability%20Group%20that%20has%202%20or%20more%20copies%20and%20not%20be%20utilizing%20a%20hardware%20based%20VSS%20solution.%3C%2FP%3E%0A%3CP%3ESome%20of%20the%20benefits%20of%20this%20strategy%20include%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ESimplified%20storage%20administration.%20Fewer%20LUNs%20to%20manage.%3C%2FLI%3E%0A%3CLI%3EPotentially%20reduce%20the%20number%20of%20backup%20jobs.%3C%2FLI%3E%0A%3CLI%3EFlexibility%20to%20isolate%20the%20performance%20between%20Databases%20when%20not%20sharing%20spindles%20between%20LUNs.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3ESome%20of%20the%20concerns%20with%20this%20strategy%20include%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ELimits%20the%20ability%20to%20take%20hardware%20based%20VSS%20backup%20and%20restores%20(e.g.%2C%20clone%20snapshots).%20See%20%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Faa996004(EXCHG.65).aspx%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EBest%20Practices%20for%20Using%20Volume%20Shadow%20Copy%20Service%20with%20Exchange%20Server%202003%3C%2FA%3E%20for%20more%20VSS%20details.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSTRONG%3E2%20LUNs%20%2F%20Database%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EWith%20Exchange%202010%2C%20in%20the%20maximum%20case%20of%20100%20Databases%2C%20the%20number%20of%20LUNs%20you%20provision%20will%20depend%20upon%20your%20backup%20strategy.%20If%20your%20recovery%20time%20objective%20(RTO)%20is%20very%20small%2C%20or%20if%20you%20use%20VSS%20clones%20for%20fast%20recovery%2C%20it%20may%20be%20best%20to%20place%20each%20Database%20on%20its%20own%20transaction%20log%20LUN%20and%20database%20LUN.%20Because%20doing%20this%20will%20exceed%20the%20number%20of%20available%20drive%20letters%2C%20volume%20mount%20points%20must%20be%20used.%3C%2FP%3E%0A%3CP%3ESome%20of%20the%20benefits%20of%20this%20strategy%20include%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EEnables%20hardware-based%20VSS%20at%20a%20database%20level%2C%20providing%20single%20database%20backup%20and%20restore.%3C%2FLI%3E%0A%3CLI%3EFlexibility%20to%20isolate%20the%20performance%20between%20databases%20when%20not%20sharing%20spindles%20between%20LUNs.%3C%2FLI%3E%0A%3CLI%3EIncreased%20reliability.%20A%20capacity%20or%20corruption%20problem%20on%20a%20single%20LUN%20will%20only%20impact%20one%20database.%20This%20is%20an%20important%20consideration%20when%20you%20are%20not%20leveraging%20the%20built-in%20mailbox%20resiliency%20features.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3ESome%20of%20the%20concerns%20with%20this%20strategy%20include%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E100%20databases%20require%20200%20LUNs%20which%20could%20exceed%20some%20storage%20array%20maximums.%3C%2FLI%3E%0A%3CLI%3EA%20separate%20LUN%20for%20each%20database%20causes%20more%20LUNs%20per%20server%20increasing%20the%20administrative%20costs%20and%20complexity.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSTRONG%3E2%20LUNs%20%2F%20Backup%20Set%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EA%20backup%20set%20is%20the%20number%20of%20databases%20that%20are%20fully%20backed%20up%20in%20a%20night.%20A%20solution%20that%20performs%20a%20full%20backup%20on%201%2F7th%20of%20the%20databases%20nightly%20(i.e.%20using%20a%20weekly%20or%20bi-monthly%20full%20backup%20with%20daily%20incrementals%20or%20differentials)%20can%20reduce%20complexity%20by%20placing%20all%20of%20the%20databases%20to%20be%20backed%20up%20on%20the%20same%20log%20and%20database%20LUN.%20This%20can%20reduce%20the%20number%20of%20LUNs%20on%20the%20server.%3C%2FP%3E%0A%3CP%3ESome%20of%20the%20benefits%20of%20this%20strategy%20include%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ESimplified%20storage%20administration.%20Fewer%20LUNs%20to%20manage.%3C%2FLI%3E%0A%3CLI%3EPotentially%20reduce%20the%20number%20of%20backup%20jobs.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3ESome%20of%20the%20concerns%20with%20this%20strategy%20include%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ELimits%20the%20ability%20to%20take%20hardware%20based%20VSS%20backup%20and%20restores%20(e.g.%2C%20clone%20snapshots).%20See%20%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Faa996004(EXCHG.65).aspx%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EBest%20Practices%20for%20Using%20Volume%20Shadow%20Copy%20Service%20with%20Exchange%20Server%202003%3C%2FA%3E%20for%20more%20VSS%20details.%3C%2FLI%3E%0A%3CLI%3EA%20capacity%20or%20corruption%20problem%20on%20a%20single%20LUN%20could%20impact%20more%20than%20one%20Database.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CH3%20id%3D%22toc-hId--864500143%22%20id%3D%22toc-hId-878313045%22%3E%3CSTRONG%3EResults%20Pane%3C%2FSTRONG%3E%3C%2FH3%3E%0A%3CP%3EBased%20on%20the%20above%20input%20factors%20the%20calculator%20will%20recommend%20the%20following%20architecture%3A%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ELUN%20Design%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EThe%20LUN%20Design%20table%20highlights%20the%20recommended%20LUN%20architecture.%3CSTRONG%3E%26nbsp%3B%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ELUN%20Configuration%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EThe%20LUN%20Configuration%20table%20highlights%20the%20number%20of%20databases%20that%20should%20be%20placed%20on%20a%20single%20LUN.%20This%20is%20derived%20from%20LUN%20Architecture%20model.%3C%2FP%3E%0A%3CP%3EThis%20section%20also%20documents%20how%20many%20LUNs%20will%20be%20required%20for%20the%20entire%20solution%2C%20broken%20out%20by%20Database%20and%20Log%20sets%2C%20and%20the%20number%20of%20restore%20LUNs%20per%20server.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EDatabase%20Configuration%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EThe%20Database%20Configuration%20table%20outlines%20the%20number%20of%20databases%20(or%20copies)%20per%20server%2C%20the%20number%20of%20mailboxes%20per%20database%2C%20the%20size%20of%20each%20database%2C%20and%20the%20transaction%20log%20size%20required%20for%20each%20database.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EDatabase%20and%20Log%20LUN%20Design%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EThe%20database%20and%20log%20LUN%20Design%20table%20outlines%20the%20physical%20LUN%20layout%20and%20follows%20the%20recommended%20number%20of%20databases%20per%20LUN%20approach%20based%20on%20the%20LUN%20Architecture%20model.%20It%20also%20documents%20the%20LUN%20size%20required%20to%20support%20layout%20(this%20is%20where%20we%20factor%20in%20the%20additional%20capacity%20for%20content%20indexing%2C%20the%20LUN%20Free%20Space%20Percentage%2C%20and%20whether%20you%20are%20using%20a%20Restore%20LUN)%2C%20as%20well%20as%20the%20transaction%20log%20LUN.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EImportant%3A%3C%2FSTRONG%3E%20The%20DB%20and%20Log%20LUN%20Design%20Table%20identify%20databases%20by%20a%20unique%20number.%20However%2C%20databases%20copies%20are%20distributed%20across%20the%20servers%2C%20and%20thus%2C%20these%20numbers%20hold%20no%20significance%20and%20are%20used%20solely%20as%20an%20example%20to%20show%20a%20server's%20LUN%20layout.%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1074823697%22%20id%3D%22toc-hId--1477330411%22%3EBackup%20Requirements%3C%2FH2%3E%0A%3CP%3EThe%20Backup%20Requirements%20section%20is%20really%20a%20continuation%20of%20the%20Role%20Requirements%20section.%20It%20outlines%20what%20we%20believe%20is%20the%20appropriate%20backup%20design%20based%20on%20the%20input%20factors%20and%20the%20analysis%20performed%20in%20the%20previous%20sections.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%3CA%20href%3D%22https%3A%2F%2Fhelpcenter.xactlycorp.com%2Flegacyfs%2Fonline%2Fmedia%2FTNBlogsFS%2Fprod.evol.blogs.technet.com%2FCommunityServer.Blogs.Components.WeblogFiles%2F00%2F00%2F00%2F31%2F06%2F7230.12.JPG%22%20original-url%3D%22http%3A%2F%2Fblogs.technet.com%2Fcfs-file.ashx%2F__key%2Fcommunityserver-blogs-components-weblogfiles%2F00-00-00-31-06%2F7230.12.JPG%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%22%3E%3CIMG%20src%3D%22http%3A%2F%2Fmigration9.stage.lithium.com%2Fskins%2Fimages%2FAF7D1A50469BCCC446F7CEAA2F38CF9E%2Fresponsive_peak%2Fimages%2Fimage_not_found.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FA%3E%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EBackup%20Configuration%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EThe%20Backup%20Configuration%20table%20outlines%20the%20number%20of%20databases%20that%20will%20be%20placed%20within%20a%20single%20LUN%20and%20the%20type%20of%20backup%20methodology%20and%20frequency%20in%20which%20the%20backups%20will%20occur.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EBackup%20Frequency%20Configuration%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EThe%20Backup%20Frequency%20Configuration%20section%20will%20provide%20you%20with%20an%20outline%20on%20how%20you%20should%20perform%20the%20backups%20for%20each%20server%2C%20utilizing%20either%20a%20daily%20full%20backup%20or%20weekly%20or%20bi-monthly%20full%20backup%20frequency.%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--1477333264%22%20id%3D%22toc-hId-265479924%22%3ELog%20Replication%20Requirements%3C%2FH2%3E%0A%3CP%3EThe%20Log%20Replication%20Requirements%20section%20is%20another%20continuation%20of%20the%20Role%20Requirements%20section.%20It%20outlines%20what%20we%20believe%20is%20the%20throughput%20required%20to%20replicate%20the%20transaction%20logs%20to%20each%20target%20database%20copy%20in%20the%20secondary%20datacenter.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fhelpcenter.xactlycorp.com%2Flegacyfs%2Fonline%2Fmedia%2FTNBlogsFS%2Fprod.evol.blogs.technet.com%2FCommunityServer.Blogs.Components.WeblogFiles%2F00%2F00%2F00%2F31%2F06%2F4454.13.JPG%22%20original-url%3D%22http%3A%2F%2Fblogs.technet.com%2Fcfs-file.ashx%2F__key%2Fcommunityserver-blogs-components-weblogfiles%2F00-00-00-31-06%2F4454.13.JPG%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%22%3E%3CIMG%20src%3D%22http%3A%2F%2Fmigration9.stage.lithium.com%2Fskins%2Fimages%2FAF7D1A50469BCCC446F7CEAA2F38CF9E%2Fresponsive_peak%2Fimages%2Fimage_not_found.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EPeak%20Log%20and%20Content%20Index%20Replication%20Throughput%20Requirements%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EThe%20Peak%20Log%20and%20Content%20Index%20Replication%20Throughput%20Requirements%20table%20provides%20you%20with%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EThe%20Peak%20Log%20%26amp%3B%20Content%20Index%20Throughput%20Required%20%2F%20Database%20is%20the%20total%20throughput%20required%20for%20a%20single%20log%20stream%20and%20content%20index.%20This%20value%20is%20based%20on%20the%20peak%20log%20generation%20hour.%3C%2FLI%3E%0A%3CLI%3EThe%20Peak%20Log%20%26amp%3B%20Content%20Index%20Throughput%20Required%20Between%20Datacenters%20%2F%20DAG%20is%20the%20total%20throughput%20required%20to%20replicate%20the%20transaction%20logs%20and%20content%20index%20to%20all%20database%20copies%20(lagged%20and%20non-lagged)%20that%20exist%20within%20the%20alternate%20datacenter%20for%20the%20database%20availability%20group.%3C%2FLI%3E%0A%3CLI%3EThe%20Peak%20Log%20%26amp%3B%20Content%20Index%20Throughput%20Required%20Between%20Datacenters%20%2F%20Environment%20is%20the%20total%20throughput%20required%20to%20replicate%20the%20transaction%20logs%20and%20content%20index%20to%20all%20database%20copies%20(lagged%20and%20non-lagged)%20that%20exist%20within%20the%20alternate%20datacenter%20for%20all%20database%20availability%20groups.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSTRONG%3ERPO%20Log%20and%20Content%20Index%20Replication%20Throughput%20Requirements%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EIn%20terms%20of%20log%20replication%2C%20RPO%20means%20how%20behind%20can%20you%20get%20in%20log%20shipping%3F%20The%20lower%20the%20RPO%20(a%20value%20of%200%20or%201%20essentially%20means%20you%20want%20to%20only%20lose%20the%20open%20log%20file)%2C%20the%20higher%20the%20bandwidth%20you%20need%20because%20you%20cannot%20get%20behind%20in%20log%20replication.%20The%20higher%20the%20RPO%20(approaching%2024)%20less%20bandwidth%20is%20needed%20as%20you%20are%20expecting%20to%20be%20behind%20(up%20to%20x%20hours)%20in%20log%20replication%20and%20to%20catch%20up%20at%20some%20point%20in%20the%20day.%3C%2FP%3E%0A%3CP%3EThe%20RPO%20Log%20and%20Content%20Index%20Replication%20Throughput%20Requirements%20table%20provides%20you%20with%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EThe%20RPO%20Log%20%26amp%3B%20Content%20Index%20Throughput%20Required%20%2F%20Database%20is%20the%20required%20throughput%20necessary%20to%20replicate%20the%20transaction%20logs%20and%20content%20index%20based%20on%20the%20RPO%20to%20the%20mailbox%20servers%20that%20are%20located%20within%20the%20secondary%20datacenter%20per%20database.%3C%2FLI%3E%0A%3CLI%3EThe%20RPO%20Log%20%26amp%3B%20Content%20Index%20Throughput%20Required%20Between%20Datacenters%20%2F%20DAG%20is%20the%20RPO%20total%20throughput%20required%20to%20replicate%20the%20transaction%20logs%20and%20content%20index%20to%20all%20database%20copies%20(lagged%20and%20non-lagged)%20that%20exist%20within%20the%20alternate%20datacenter%20for%20the%20database%20availability%20group.%3C%2FLI%3E%0A%3CLI%3EThe%20RPO%20Log%20%26amp%3B%20Content%20Index%20Throughput%20Required%20Between%20Datacenters%20%2F%20Environment%20is%20the%20RPO%20total%20throughput%20required%20to%20replicate%20the%20transaction%20logs%20and%20content%20index%20to%20all%20database%20copies%20(lagged%20and%20non-lagged)%20that%20exist%20within%20the%20alternate%20datacenter%20for%20all%20database%20availability%20groups.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSTRONG%3EChosen%20Network%20Link%20Suitability%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EThe%20Chosen%20Network%20Link%20Suitability%20table%20will%20dictate%20whether%20the%20chosen%20network%20link%20has%20sufficient%20capacity%20to%20sustain%20the%20peak%20replication%20throughput%20requirements%20and%2For%20the%20RPO%20replication%20throughput%20requirements.%20If%20the%20network%20link%20cannot%20sustain%20the%20log%20replication%20traffic%2C%20then%20you%20will%20need%20to%20either%20upgrade%20the%20network%20link%20to%20the%20recommended%20network%20link%20throughput%2C%20or%20adjust%20the%20design%20appropriately.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ERecommended%20Network%20Link%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EThe%20Recommended%20Network%20Link%20table%20recommends%20an%20appropriate%20network%20link%20if%20the%20chosen%20network%20link%20does%20not%20have%20sufficient%20capacity%20to%20sustain%20log%20replication%20for%20solution%20for%20both%20the%20peak%20and%20RPO%20throughput%20requirements.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ENote%3A%3C%2FSTRONG%3E%20The%20Network%20Link%20recommendations%20do%20not%20take%20into%20account%20database%20seeding%20or%20any%20other%20data%20that%20may%20also%20utilize%20the%20link.%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-265477071%22%20id%3D%22toc-hId--1401400472%22%3EStorage%20Design%3C%2FH2%3E%0A%3CP%3EThe%20Storage%20Design%20worksheet%20is%20designed%20to%20take%20the%20data%20collected%20from%20the%20Input%20worksheet%20and%20Storage%20Requirements%20worksheet%20and%20help%20you%20determine%20the%20number%20of%20physical%20disks%20needed%20to%20support%20the%20databases%2C%20transaction%20logs%2C%20and%20Restore%20LUN%20configurations.%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId-1096612612%22%20id%3D%22toc-hId--1455541496%22%3EStorage%20Design%20Input%20Factors%3C%2FH3%3E%0A%3CP%3EIn%20order%20to%20determine%20the%20physical%20disk%20requirements%2C%20you%20must%20enter%20in%20some%20basic%20information%20about%20your%20storage%20solution.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%3CA%20href%3D%22https%3A%2F%2Fhelpcenter.xactlycorp.com%2Flegacyfs%2Fonline%2Fmedia%2FTNBlogsFS%2Fprod.evol.blogs.technet.com%2FCommunityServer.Blogs.Components.WeblogFiles%2F00%2F00%2F00%2F31%2F06%2F1106.14.JPG%22%20original-url%3D%22http%3A%2F%2Fblogs.technet.com%2Fcfs-file.ashx%2F__key%2Fcommunityserver-blogs-components-weblogfiles%2F00-00-00-31-06%2F1106.14.JPG%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%22%3E%3CIMG%20src%3D%22http%3A%2F%2Fmigration9.stage.lithium.com%2Fskins%2Fimages%2FAF7D1A50469BCCC446F7CEAA2F38CF9E%2Fresponsive_peak%2Fimages%2Fimage_not_found.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FA%3E%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ERAID%20Parity%20Configuration%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EFor%20the%20Database%2FLog%20RAID%20Parity%20Configuration%20table%20you%20need%20to%20select%20the%20type%20of%20RAID%20building%20block%20your%20storage%20solution%20utilizes.%20For%20example%2C%20some%20storage%20vendors%20build%20the%20underlying%20storage%20in%20sets%20of%20data%2Bparity%20(d%2Bp)%20groups.%20A%20RAID-5%203%2B1%20configuration%20means%20that%203%20disks%20will%20be%20used%20for%20capacity%20and%201%20disk%20will%20be%20used%20for%20parity%2C%20even%20though%20parity%20is%20distributed%20across%20all%20the%20disks.%20So%20if%20you%20had%20a%20capacity%20requirement%20that%20would%20utilize%2015%20disks%2C%20then%20you%20would%20need%20to%20deploy%205%203%2B1%20groups%20to%20build%20that%20RAID-5%20array.%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ERAID-1%2F0%20supports%201d%2B1p%2C%202d%2B2p%2C%20and%204d%2B4p%20groupings%3C%2FLI%3E%0A%3CLI%3ERAID-5%20supports%203d%2B1p%20through%2020d%2B1p%20groupings%20(though%20storage%20solutions%20could%20support%20more%20than%20that).%3C%2FLI%3E%0A%3CLI%3ERAID-6%20supports%206d%2B2p%20groupings.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSTRONG%3EDatabase%2FLog%20RAID%20Rebuild%20Overhead%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EWhen%20a%20disk%20is%20lost%2C%20the%20disk%20needs%20to%20be%20replaced%20and%20rebuilt.%20During%20this%20time%2C%20the%20performance%20of%20the%20RAID%20group%20is%20affected.%20This%20impact%20as%20a%20result%20can%20affect%20user%20actions.%20Therefore%2C%20to%20ensure%20that%20RAID%20rebuilds%20do%20not%20affect%20the%20overall%20performance%20of%20the%20mailbox%20server%2C%20Microsoft%20recommends%20that%20you%20should%20ensure%20sufficient%20overhead%20is%20provisioned%20into%20the%20performance%20calculations%20when%20designing%20for%20RAID%20parity.%20Most%20RAID-1%2F0%20implementations%20will%20suffer%20a%2025%25%20performance%20penalty%20during%20a%20rebuild.%20Most%20RAID-5%20and%20RAID-6%20implementations%20will%20suffer%20a%2050%25%20performance%20penalty%20during%20a%20rebuild.%3C%2FP%3E%0A%3CP%3EThe%20calculator%20defaults%20with%20the%20following%20as%20Microsoft%20recommendations%2C%20but%20they%20are%20adjustable%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EFor%20RAID-1%2F0%20implementations%2C%20ensure%20that%20you%20factor%20in%20an%20additional%2035%25%20performance%20overhead.%3C%2FLI%3E%0A%3CLI%3EFor%20RAID-5%2FRAID-6%20implementations%2C%20ensure%20that%20you%20factor%20in%20an%20additional%20100%25%20performance%20overhead.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EIn%20addition%2C%20you%20should%20consult%20with%20your%20storage%20vendor%20to%20determine%20the%20appropriate%20RAID%20rebuild%20penalty.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EDatabase%20RAID%20Configuration%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EBy%20default%2C%20for%20RAID%20storage%20solutions%2C%20the%20calculator%20will%20recommend%20either%20RAID-1%2F0%20or%20RAID-5%20by%20evaluating%20capacity%20and%20I%2FO%20factors%20and%20determining%20which%20configuration%20utilizes%20the%20least%20amount%20of%20disks%20while%20satisfying%20the%20requirements.%20If%20you%20would%20like%20to%20override%20this%20and%20force%20the%20calculator%20to%20utilize%20a%20particular%20RAID%20configuration%20for%20your%20databases%20(e.g.%2C%20RAID-0%20or%20RAID-6)%2C%20select%20%22Yes%22%20to%20this%20option%20and%20then%20select%20the%20appropriate%20RAID%20configuration%20in%20the%20cell%20labeled%20%22Desired%20RAID%20Configuration.%22%20Note%20that%20while%20you%20can%20potentially%20override%20the%20database%20RAID%20configuration%2C%20you%20cannot%20do%20so%20for%20the%20log%20RAID%20configuration%20-%20that%20will%20always%20be%20RAID-1%2F0.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ENote%3A%3C%2FSTRONG%3E%20The%20calculator%20prevents%20the%20use%20of%20RAID-5%20or%20RAID-6%20with%205.2K%2C%205.4K%2C%205.9K%20and%207.2K%20disk%20types%2C%20due%20to%20performance%20implications.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ERestore%20LUN%20RAID%20Configuration%20%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EYou%20can%20select%20the%20type%20of%20parity%20you%20will%20be%20utilizing%20and%20the%20RAID%20configuration%20you%20will%20be%20deploying%20for%20your%20Restore%20LUN.%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId--1455544349%22%20id%3D%22toc-hId-287268839%22%3EResults%20Pane%3C%2FH3%3E%0A%3CP%3EThe%20Storage%20Design%20Results%20section%20outputs%20the%20recommended%20configuration%20for%20the%20solution.%20The%20recommendations%20made%20are%20for%20implementing%20the%20solution%20potentially%20on%20RAID%20and%20JBOD%20storage.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%3CA%20href%3D%22https%3A%2F%2Fhelpcenter.xactlycorp.com%2Flegacyfs%2Fonline%2Fmedia%2FTNBlogsFS%2Fprod.evol.blogs.technet.com%2FCommunityServer.Blogs.Components.WeblogFiles%2F00%2F00%2F00%2F31%2F06%2F5141.15.JPG%22%20original-url%3D%22http%3A%2F%2Fblogs.technet.com%2Fcfs-file.ashx%2F__key%2Fcommunityserver-blogs-components-weblogfiles%2F00-00-00-31-06%2F5141.15.JPG%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%22%3E%3CIMG%20src%3D%22http%3A%2F%2Fmigration9.stage.lithium.com%2Fskins%2Fimages%2FAF7D1A50469BCCC446F7CEAA2F38CF9E%2Fresponsive_peak%2Fimages%2Fimage_not_found.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FA%3E%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ERAID%20Storage%20Architecture%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EThe%20RAID%20Storage%20Architecture%20Table%20outlines%20which%20servers%20(primary%20datacenter%20servers%2C%20secondary%20datacenter%20servers%2C%20or%20lagged%20copy%20servers)%20should%20be%20deployed%20on%20RAID%20storage.%3C%2FP%3E%0A%3CP%3EThe%20RAID%20Storage%20Architecture%20%2F%20Server%3CSTRONG%3E%20%3C%2FSTRONG%3Etable%20recommends%20the%20optimum%20RAID%20configuration%20and%20number%20of%20disks%20for%20each%20LUN%20(database%2C%20log%20and%20restore%20LUN)%20for%20each%20mailbox%20server%20ensuring%20that%20performance%20and%20capacity%20requirements%20are%20met%20within%20the%20design.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EJBOD%20Storage%20Architecture%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EThe%20JBOD%20Storage%20Architecture%20Table%20outlines%20which%20servers%20(primary%20datacenter%20servers%2C%20secondary%20datacenter%20servers%2C%20or%20lagged%20copy%20servers)%20could%20be%20deployed%20on%20JBOD%20storage.%3C%2FP%3E%0A%3CP%3EThe%20JBOD%20Storage%20Architecture%20%2F%20Server%3CSTRONG%3E%20%3C%2FSTRONG%3Etable%20recommends%20the%20optimum%20JBOD%20configuration%20and%20number%20of%20disks%20for%20each%20LUN%20(database%2C%20log%20and%20restore%20LUN)%20for%20each%20mailbox%20server%20ensuring%20that%20performance%20and%20capacity%20requirements%20are%20met%20within%20the%20design.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ETotal%20Disks%20Required%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EBy%20default%2C%20the%20calculator%20will%20determine%20the%20storage%20architecture%20that%20should%20be%20utilized%20to%20reduce%20the%20total%20number%20of%20disks%20required%20to%20support%20the%20design%2C%20in%20addition%2C%20to%20still%20ensuring%20you%20have%20minimized%20single%20points%20of%20failure%20by%20utilizing%20RAID%20and%2For%20JBOD%20based%20on%20the%20decisions%20found%20in%20the%20%22RAID%20Storage%20Architecture%22%20and%20%22JBOD%20Storage%20Architecture%22%20tables.%20However%2C%20you%20can%20change%20the%20storage%20architecture%20to%20be%20built%20entirely%20on%20RAID%20or%20entirely%20on%20JBOD%20(if%20the%20design%20supports%20JBOD%20as%20a%20possible%20solution%3B%20also%20keep%20in%20mind%20that%20certain%20scenarios%20(e.g.%2C%20a%20single%20database%20copy%20in%20a%20datacenter)%20may%20result%20in%20a%20single%20point%20of%20failure)%20by%20selecting%20the%20appropriate%20value%20in%20the%20%22Storage%20Architecture%20will%20be%20Deployed%3A%22%20drop-down.%3C%2FP%3E%0A%3CP%3EThe%20Storage%20Configuration%20table%20will%20output%20the%20total%20number%20of%20disks%20required%20for%20each%20mailbox%20server%20that%20requires%20RAID%20or%20JBOD%20storage%2C%20as%20well%20as%2C%20identify%20the%20total%20number%20of%20disks%20requiring%20RAID%20or%20JBOD%20storage%20in%20each%20datacenter.%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-2084217345%22%20id%3D%22toc-hId--467936763%22%3EConclusion%3C%2FH2%3E%0A%3CP%3EHopefully%20you%20will%20find%20this%20calculator%20invaluable%20in%20helping%20to%20determine%20your%20mailbox%20server%20role%20requirements%20for%20Exchange%202010%20mailbox%20servers.%20If%20you%20have%20any%20questions%20or%20suggestions%2C%20please%20email%20strgcalc%20AT%20microsoft%20DOT%20com.%3C%2FP%3E%0A%3CP%3EFor%20the%20calculator%20itself%2C%20please%20see%20the%20following%20link%3A%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22http%3A%2F%2Fgallery.technet.microsoft.com%2Fv144-of-the-Exchange-2010-1912958d%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EExchange%202010%20Server%20Role%20Requirements%20Calculator%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22author%22%3E%3CA%20href%3D%22http%3A%2F%2Fblogs.technet.com%2Farchive%2F2005%2F08%2F25%2F409819.aspx%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3ERoss%20Smith%20IV%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E

EHLO!

As we hinted in our 15 year blogoversary post, this blog will be moving to a new home soon. Here is what you can expect:

  • Our new home will be Microsoft Tech Community, Blogs section (there will be “Exchange” in the list once all is said and done, with its own unique URL)
  • We have done a lot of cleanup of our 15 years of content already; generally speaking – if it is live on the blog today, it will migrate over. We did not try to delete ‘legacy’ content, rather get rid of stuff that is obviously not relevant anymore (like that Exchange 5.5 Webcast announcement from 14 years ago)
  • Yes, we will be migrating post comments over too; however, due to reasons… all of the comments will migrate over as anonymous; we felt there was still value there to keep the discussion present even though it might not be immediately obvious who was asking and replying exactly. The context helps in many cases, and good advice is good advice so…
  • We will work to make sure all of individual current post URLs redirect to migrated posts in their new location
  • We will work to redirect short URLs that go to our blog today, like http://aka.ms/ehlo
  • All of this is going to happen within next 3-6 weeks. Or earlier. Or later. Basically: “When it’s ready.”

What can you do to prepare?

If you want to keep being engaged with us and want to keep commenting to our posts (and continue the discussion that Exchange community is known for), you will need to register with Tech Community site. We are not doing any kind of migration of user accounts.

When we will be in the finalization stage, there is likely going to be some time when we will take a ‘snapshot’ and migrate that, and any comments etc. made after that will be lost once we move over (as they will not be in migration set). We will give you a heads up when this is about to happen. If unexpected things happen and you start getting errors temporarily, now you know what’s up!

The Exchange Team Blog Team

2 Comments
Not applicable
Here's to the next 15 years at your new home - cheers and keep up the great work :-)
Not applicable
No surprise there I guess, I do hope that this will result in more MS folks participating in the forums section of the MTC.