Home
%3CLINGO-SUB%20id%3D%22lingo-sub-593922%22%20slang%3D%22en-US%22%3EReleased%3A%20Exchange%202013%20Server%20Role%20Requirements%20Calculator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-593922%22%20slang%3D%22en-US%22%3E%3CP%3E%3C%2FP%3E%3CDIV%20class%3D%22resources%22%20style%3D%22margin-left%3A10px%3Bwidth%3A150px%3B%22%3E%0A%3CUL%20style%3D%22list-style-type%3Anone%3Bfont-size%3A1.2em%3Blist-style-position%3Aoutside%3Bcolor%3A%233b79cc%3Bmargin-left%3A0.5em%3B%22%3E%0A%3CLI%3E%3CA%20title%3D%22Download%20Exchange%202013%20Server%20Role%20Requirements%20Calculator%22%20href%3D%22http%3A%2F%2Fgallery.technet.microsoft.com%2FExchange-2013-Server-Role-f8a61780%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3Edownload%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3E%3CA%20title%3D%22Exchange%202013%20Server%20Role%20Requirements%20Calculator%20Release%20Notes%22%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Fb%2Fexchange%2Farchive%2F2013%2F05%2F24%2Fexchange-2013-server-role-requirements-calculator-release-notes.aspx%22%20target%3D%22_blank%22%3Erelease%20notes%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3E%3CA%20title%3D%22Exchange%202013%20Server%20Role%20Requirements%20Calculator%20Readme%22%20href%3D%22http%3A%2F%2Fgallery.technet.microsoft.com%2FExchange-2013-Server-Role-c81ac1cf%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3Ereadme%3C%2FA%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FDIV%3E%0A%3CP%3EIt%E2%80%99s%20been%20a%20long%20road%2C%20but%20the%20initial%20release%20of%20the%20Exchange%20Server%20Role%20Requirements%20Calculator%20is%20here.%20No%2C%20that%20isn%E2%80%99t%20a%20mistake%2C%20the%20calculator%20has%20been%20rebranded.%26nbsp%3B%20Yes%2C%20this%20is%20no%20longer%20a%20Mailbox%20server%20role%20calculator%3B%20this%20calculator%20includes%20recommendations%20on%20sizing%20Client%20Access%20servers%20too!%20Originally%2C%20marketing%20wanted%20to%20brand%20it%20as%20the%20%3CEM%3EMicrosoft%20Exchange%20Server%202013%20Client%20Access%20and%20Mailbox%20Server%20Roles%20Theoretical%20Capacity%20Planning%20Calculator%2C%20On-Premises%20Edition%3C%2FEM%3E.%26nbsp%3B%20Wow%2C%20that%E2%80%99s%20a%20mouthful%20and%20reminds%20me%20of%20this%20%3CA%20href%3D%22https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DEUXnJraKM3k%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3Ebranding%20parody%3C%2FA%3E.%26nbsp%3B%20Thankfully%2C%20I%20vetoed%20that%20name%20(you%E2%80%99re%20welcome!).%3C%2FP%3E%0A%3CP%3EThe%20calculator%20supports%20the%20architectural%20changes%20made%20possible%20with%20Exchange%202013%20and%20later%3A%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId-1542364873%22%20id%3D%22toc-hId-1569289366%22%3EClient%20Access%20Servers%3C%2FH3%3E%0A%3CP%3E%3CSPAN%20class%3D%22lightyellow%22%3ELike%20with%20Exchange%202010%2C%20the%20recommendation%20in%20Exchange%202013%20is%20to%20deploy%20multi-role%20servers.%3C%2FSPAN%3E%20There%20are%20very%20few%20reasons%20you%20would%20need%20to%20deploy%20dedicated%20Client%20Access%20servers%20(CAS)%3B%20CPU%20constraints%2C%20use%20of%20Windows%20Network%20Load%20Balancing%20in%20small%20deployments%20(even%20with%20our%20architectural%20changes%20in%20client%20connectivity%2C%20we%20still%20do%20not%20recommend%20Windows%20NLB%20for%20any%20large%20deployments)%20and%20certificate%20management%20are%20a%20few%20examples%20that%20may%20justify%20dedicated%20CAS.%3C%2FP%3E%0A%3CP%3EWhen%20deploying%20multi-role%20servers%2C%20the%20calculator%20will%20take%20into%20account%20the%20impact%20that%20the%20CAS%20role%20has%20and%20make%20recommendations%20for%20sizing%20the%20entire%20server%E2%80%99s%20memory%20and%20CPU.%20So%20when%20you%20see%20the%20CPU%20utilization%20value%2C%20this%20will%20include%20the%20impact%20both%20roles%20have!%3C%2FP%3E%0A%3CP%3EWhen%20deploying%20dedicated%20server%20roles%2C%20the%20calculator%20will%20recommend%20the%20minimum%20number%20of%20Client%20Access%20processor%20cores%20and%20memory%20per%20server%2C%20as%20well%20as%2C%20the%20minimum%20number%20of%20CAS%20you%20should%20deploy%20in%20each%20datacenter.%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId--1009792088%22%20id%3D%22toc-hId--982867595%22%3ETransport%3C%2FH3%3E%0A%3CP%3ENow%20that%20the%20Mailbox%20server%20role%20includes%20additional%20components%20like%20transport%2C%20it%20only%20makes%20sense%20to%20include%20transport%20sizing%20in%20the%20calculator.%20This%20release%20does%20just%20that%20and%20will%20factor%20in%20%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Faa998043(v%3Dexchg.150).aspx%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3Emessage%20queue%20expiration%3C%2FA%3E%20and%20%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fjj657495.aspx%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3ESafety%20Net%20hold%20time%3C%2FA%3E%20when%20calculating%20the%20database%20size.%20The%20calculator%20even%20makes%20a%20recommendation%20on%20where%20to%20deploy%20the%20mail.que%20database%2C%20either%20the%20system%20disk%2C%20or%20on%20a%20dedicated%20disk!%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId-733018247%22%20id%3D%22toc-hId-759942740%22%3EMultiple%20Databases%20%2F%20JBOD%20Volume%20Support%3C%2FH3%3E%0A%3CP%3EExchange%202010%20introduced%20the%20concept%20of%201%20database%20per%20JBOD%20volume%20when%20deploying%20multiple%20database%20copies.%20However%2C%20this%20architecture%20did%20not%20ensure%20that%20the%20drive%20was%20utilized%20effectively%20across%20all%20three%20dimensions%20%E2%80%93%20throughput%2C%20IO%2C%20and%20capacity.%20Typically%2C%20the%20system%20was%20balanced%20from%20an%20IO%20and%20capacity%20perspective%2C%20but%20throughput%20was%20where%20we%20saw%20an%20imbalance%2C%20because%20during%20reseeds%20only%20a%20portion%20of%20the%20target%20disk%E2%80%99s%20total%20capable%20throughput%20was%20utilized.%20In%20addition%2C%20capacity%20on%20the%207.2K%20disks%20continue%20to%20increase%20with%204TB%20disks%20now%20available%2C%20thus%20impacting%20our%20ability%20to%20remain%20balanced%20along%20that%20dimension.%20In%20addition%2C%20Exchange%202013%20includes%20a%2033%25%20reduction%20in%20IO%20when%20compared%20to%20Exchange%202010.%20Naturally%2C%20the%20concept%20of%201%20database%20%2F%20JBOD%20volume%20needed%20to%20evolve.%20As%20a%20result%2C%20Exchange%202013%20made%20several%20architectural%20changes%20in%20the%20store%20process%2C%20ESE%2C%20and%20HA%20architecture%20to%20support%20multiple%20databases%20per%20JBOD%20volume.%20If%20you%20would%20like%20more%20information%2C%20please%20see%20Scott%E2%80%99s%20excellent%20TechEd%20session%20in%20a%20few%20weeks%20on%20%3CA%20href%3D%22https%3A%2F%2Fchannel9.msdn.com%2FEvents%2FTechEd%2FNorthAmerica%2F2013%2FOUC-B314%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EExchange%202013%20High%20Availability%20and%20Site%20Resilience%3C%2FA%3E%20or%20the%20%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fdd638137(v%3Dexchg.150).aspx%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EHigh%20Availability%20and%20Site%20Resilience%3C%2FA%3E%20topic%20on%20TechNet.%3C%2FP%3E%0A%3CP%3EBy%20default%2C%20the%20calculator%20will%20recommend%20multiple%20databases%20per%20JBOD%20volume.%20This%20architecture%20is%20supported%20for%20single%20datacenter%20deployments%20and%20multi-datacenter%20deployments%20when%20there%20is%20copy%20and%2For%20server%20symmetry.%20The%20calculator%20supports%20highly%20available%20database%20copies%20and%20lagged%20database%20copies%20with%20this%20volume%20architecture%20type.%20The%20distribution%20algorithm%20will%20lay%20out%20the%20copies%20appropriately%2C%20as%20well%20as%2C%20generate%20the%20deployment%20scripts%20correctly%20to%20support%20%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fjj619303(v%3Dexchg.150).aspx%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EAutoReseed%3C%2FA%3E.%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId--1819138714%22%20id%3D%22toc-hId--1792214221%22%3EHigh%20Availability%20Architecture%20Improvements%3C%2FH3%3E%0A%3CP%3EThe%20calculator%20has%20been%20improved%20in%20several%20ways%20for%20high%20availability%20architectures%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EYou%20can%20now%20specify%20the%20Witness%20Server%20location%2C%20either%20primary%2C%20secondary%2C%20or%20tertiary%20datacenter.%3C%2FLI%3E%0A%3CLI%3EThe%20calculator%20allows%20you%20to%20simulate%20WAN%20failures%2C%20so%20that%20you%20can%20see%20how%20the%20databases%20are%20distributed%20during%20the%20worst%20failure%20mode.%3C%2FLI%3E%0A%3CLI%3EThe%20calculator%20allows%20you%20to%20name%20servers%20and%20define%20a%20database%20prefix%20which%20are%20then%20used%20in%20the%20deployment%20scripts.%3C%2FLI%3E%0A%3CLI%3EThe%20distribution%20algorithm%20supports%20single%20datacenter%20HA%20deployments%2C%20Active%2FPassive%20deployments%2C%20and%20Active%2FActive%20deployments.%3C%2FLI%3E%0A%3CLI%3EThe%20calculator%20includes%20a%20PowerShell%20script%20to%20automate%20DAG%20creation.%3C%2FLI%3E%0A%3CLI%3EIn%20the%20event%20you%20are%20deploying%20your%20high%20availability%20architecture%20with%20direct%20attached%20storage%2C%20you%20can%20now%20specify%20the%20maximum%20number%20of%20database%20volumes%20each%20server%20will%20support.%20For%20example%2C%20if%20you%20are%20deploying%20a%20server%20architecture%20that%20can%20support%2024%20disks%2C%20you%20can%20specify%20a%20maximum%20support%20of%2020%20database%20volumes%20(leaving%202%20disks%20for%20system%2C%201%20disk%20for%20Restore%20Volume%2C%20and%201%20disks%20as%20a%20spare%20for%20AutoReseed).%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CH3%20id%3D%22toc-hId--76328379%22%20id%3D%22toc-hId--49403886%22%3EAdditional%20Mailbox%20Tiers%20(sort%20of!)%3C%2FH3%3E%0A%3CP%3EOver%20the%20years%2C%20a%20few%2C%20but%20vocal%2C%20members%20of%20the%20community%20have%20requested%20that%20I%20add%20more%20mailbox%20tiers%20to%20the%20calculator.%20As%20many%20of%20you%20know%2C%20I%20rarely%20recommend%20sizing%20multiple%20mailbox%20tiers%2C%20as%20that%20simply%20adds%20operational%20complexity%20and%20I%20am%20all%20about%20removing%20complexity%20in%20your%20messaging%20environments.%20While%2C%20I%20haven%E2%80%99t%20specifically%20added%20additional%20mailbox%20tiers%2C%20I%20have%20added%20the%20ability%20for%20you%20to%20define%20a%20percentage%20of%20the%20mailbox%20tier%20population%20that%20should%20have%20the%20IO%20and%20Megacycle%20Multiplication%20Factors%20applied.%20In%20a%20way%2C%20this%20allows%20you%20to%20define%20up%20to%20eight%20different%20mailbox%20tiers.%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId-1666481956%22%20id%3D%22toc-hId-1693406449%22%3EProcessors%3C%2FH3%3E%0A%3CP%3EI%E2%80%99ve%20received%20a%20number%20of%20questions%20regarding%20processor%20sizing%20in%20the%20calculator.%26nbsp%3B%20People%20are%20comparing%20the%20Exchange%202010%20Mailbox%20Server%20Role%20Requirements%20Calculator%20output%20with%20the%20Exchange%202013%20Server%20Role%20Requirements%20Calculator.%26nbsp%3B%20As%20mentioned%20in%20our%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Fb%2Fexchange%2Farchive%2F2013%2F05%2F06%2Fask-the-perf-guy-sizing-exchange-2013-deployments.aspx%22%20target%3D%22_blank%22%3EExchange%202013%20Performance%20Sizing%3C%2FA%3E%20article%2C%20the%20megacycle%20guidance%20in%20Exchange%202013%20leverages%20a%20new%20server%20baseline%2C%20therefore%2C%20you%20cannot%20directly%20compare%20the%20output%20from%20the%20Exchange%202010%20calculator%20with%20the%20Exchange%202013%20calculator.%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId--885675005%22%20id%3D%22toc-hId--858750512%22%3EConclusion%3C%2FH3%3E%0A%3CP%3EThere%20are%20many%20other%20minor%20improvements%20sprinkled%20throughout%20the%20calculator.%26nbsp%3B%20We%20hope%20you%20enjoy%20this%20initial%20release.%26nbsp%3B%20All%20of%20this%20work%20wouldn%E2%80%99t%20have%20occurred%20without%20the%20efforts%20of%20Jeff%20Mealiffe%20(for%20without%20our%20sizing%20guidance%20there%20would%20be%20no%20calculator!)%2C%20David%20Mosier%20(VBA%20scripting%20guru%20and%20the%20master%20of%20crafting%20the%20distribution%20worksheet)%2C%20and%20Jon%20Gollogy%20(deployment%20scripting%20master).%3C%2FP%3E%0A%3CP%3EAs%20always%20we%20welcome%20feedback%20and%20please%20report%20any%20issues%20you%20may%20encounter%20while%20using%20the%20calculator%20by%20emailing%20strgcalc%20AT%20microsoft%20DOT%20com.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22author%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Fb%2Fexchange%2Farchive%2F2005%2F08%2F25%2Fross-smith-iv-s-biography.aspx%22%20target%3D%22_blank%22%3ERoss%20Smith%20IV%3C%2FA%3E%3C%2FSPAN%3E%20%3CBR%20%2F%3EPrincipal%20Program%20Manager%20%3CBR%20%2F%3EExchange%20Customer%20Experience%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

It’s been a long road, but the initial release of the Exchange Server Role Requirements Calculator is here. No, that isn’t a mistake, the calculator has been rebranded.  Yes, this is no longer a Mailbox server role calculator; this calculator includes recommendations on sizing Client Access servers too! Originally, marketing wanted to brand it as the Microsoft Exchange Server 2013 Client Access and Mailbox Server Roles Theoretical Capacity Planning Calculator, On-Premises Edition.  Wow, that’s a mouthful and reminds me of this branding parody.  Thankfully, I vetoed that name (you’re welcome!).

The calculator supports the architectural changes made possible with Exchange 2013 and later:

Client Access Servers

Like with Exchange 2010, the recommendation in Exchange 2013 is to deploy multi-role servers. There are very few reasons you would need to deploy dedicated Client Access servers (CAS); CPU constraints, use of Windows Network Load Balancing in small deployments (even with our architectural changes in client connectivity, we still do not recommend Windows NLB for any large deployments) and certificate management are a few examples that may justify dedicated CAS.

When deploying multi-role servers, the calculator will take into account the impact that the CAS role has and make recommendations for sizing the entire server’s memory and CPU. So when you see the CPU utilization value, this will include the impact both roles have!

When deploying dedicated server roles, the calculator will recommend the minimum number of Client Access processor cores and memory per server, as well as, the minimum number of CAS you should deploy in each datacenter.

Transport

Now that the Mailbox server role includes additional components like transport, it only makes sense to include transport sizing in the calculator. This release does just that and will factor in message queue expiration and Safety Net hold time when calculating the database size. The calculator even makes a recommendation on where to deploy the mail.que database, either the system disk, or on a dedicated disk!

Multiple Databases / JBOD Volume Support

Exchange 2010 introduced the concept of 1 database per JBOD volume when deploying multiple database copies. However, this architecture did not ensure that the drive was utilized effectively across all three dimensions – throughput, IO, and capacity. Typically, the system was balanced from an IO and capacity perspective, but throughput was where we saw an imbalance, because during reseeds only a portion of the target disk’s total capable throughput was utilized. In addition, capacity on the 7.2K disks continue to increase with 4TB disks now available, thus impacting our ability to remain balanced along that dimension. In addition, Exchange 2013 includes a 33% reduction in IO when compared to Exchange 2010. Naturally, the concept of 1 database / JBOD volume needed to evolve. As a result, Exchange 2013 made several architectural changes in the store process, ESE, and HA architecture to support multiple databases per JBOD volume. If you would like more information, please see Scott’s excellent TechEd session in a few weeks on Exchange 2013 High Availability and Site Resilience or the High Availability and Site Resilience topic on TechNet.

By default, the calculator will recommend multiple databases per JBOD volume. This architecture is supported for single datacenter deployments and multi-datacenter deployments when there is copy and/or server symmetry. The calculator supports highly available database copies and lagged database copies with this volume architecture type. The distribution algorithm will lay out the copies appropriately, as well as, generate the deployment scripts correctly to support AutoReseed.

High Availability Architecture Improvements

The calculator has been improved in several ways for high availability architectures:

  • You can now specify the Witness Server location, either primary, secondary, or tertiary datacenter.
  • The calculator allows you to simulate WAN failures, so that you can see how the databases are distributed during the worst failure mode.
  • The calculator allows you to name servers and define a database prefix which are then used in the deployment scripts.
  • The distribution algorithm supports single datacenter HA deployments, Active/Passive deployments, and Active/Active deployments.
  • The calculator includes a PowerShell script to automate DAG creation.
  • In the event you are deploying your high availability architecture with direct attached storage, you can now specify the maximum number of database volumes each server will support. For example, if you are deploying a server architecture that can support 24 disks, you can specify a maximum support of 20 database volumes (leaving 2 disks for system, 1 disk for Restore Volume, and 1 disks as a spare for AutoReseed).

Additional Mailbox Tiers (sort of!)

Over the years, a few, but vocal, members of the community have requested that I add more mailbox tiers to the calculator. As many of you know, I rarely recommend sizing multiple mailbox tiers, as that simply adds operational complexity and I am all about removing complexity in your messaging environments. While, I haven’t specifically added additional mailbox tiers, I have added the ability for you to define a percentage of the mailbox tier population that should have the IO and Megacycle Multiplication Factors applied. In a way, this allows you to define up to eight different mailbox tiers.

Processors

I’ve received a number of questions regarding processor sizing in the calculator.  People are comparing the Exchange 2010 Mailbox Server Role Requirements Calculator output with the Exchange 2013 Server Role Requirements Calculator.  As mentioned in our Exchange 2013 Performance Sizing article, the megacycle guidance in Exchange 2013 leverages a new server baseline, therefore, you cannot directly compare the output from the Exchange 2010 calculator with the Exchange 2013 calculator.

Conclusion

There are many other minor improvements sprinkled throughout the calculator.  We hope you enjoy this initial release.  All of this work wouldn’t have occurred without the efforts of Jeff Mealiffe (for without our sizing guidance there would be no calculator!), David Mosier (VBA scripting guru and the master of crafting the distribution worksheet), and Jon Gollogy (deployment scripting master).

As always we welcome feedback and please report any issues you may encounter while using the calculator by emailing strgcalc AT microsoft DOT com.

Ross Smith IV
Principal Program Manager
Exchange Customer Experience

53 Comments
Not applicable

terrific !!! been waiting for a while...

Not applicable

Nice work team!

Not applicable

It is so shiny and still has that new calculator smell to it. <breathes in deep> Ahhhhhh.

Not applicable

Awesome! Can't wait to have a test!

Not applicable

Very cool! It was a long wait but it prooved to be worth it. Thanks a ton!

Not applicable

long awaited and appreciated!!!

Not applicable

Great news !

Not applicable

Brilliant, thanks!

Not applicable

This is great but when is the storage calculator going to be released for 2013?  

Not applicable

@Robert: This is the Exchange 2013 calculator.  :)

Not applicable

Do we now have tu use the accurate calculator for Exchange 2010 or 2013?

Bernd

Not applicable

Thank you!

Not applicable

@Bernd, you use the calculator from this blog post with Exchange 2013.  You use the older calculator at gallery.technet.microsoft.com/Exchange-2010-Mailbox-Server-Role- with Exchange 2010.

Not applicable

Excellent, thank you

Not applicable

How about Disk Space for OS and Installation ? Do we have to calculate it manual ?

Not applicable

Thanks for this, good job.  I've watched Scott's 2012 New Zealand TechEd sessions which include HA and Site resilience topic on Channel9, I believe it was for pre RTM,   just wanted to say how awesome they are.  Many thanks and I'm looking forward to watching the North American TechEd, in case there's more cool new features for CU1.

Not applicable

Awesome!!! World was holding the deployment for this

Not applicable

Yes, great work! I'm going to check our current implementation immediately. :)

Not applicable

Thanks Gentlemen, Any word on the release of the updated Exchange Client Network Bandwidth Calculator?

Not applicable

Question on the calculator. When I do a configuration for 200 Mailboxes(2 databases with 100 mailboxes on each.), Do I really need 24GB of memory on each database server?

Not applicable

I am really glad to see this.

Not applicable

Traffic improvement, I do checking now....Thanks for your support engineers

Not applicable

Great Work Gents ;)

Not applicable

Exciting!  Ross is there any forthcoming info on UM migrations?  The current TechNet article is confusing and seems to contradict itself in the early steps:

technet.microsoft.com/.../dn169226(v=exchg.150).aspx

Thanks!

Not applicable

Pesos - I'm willing to help here with UM, but I'm not sure what you're asking.  Can you give me some details? Thanks.

Not applicable

Oh my golly gosh! Thankyou. Orin Thomas just gave me the very exciting news during a class.

Not applicable

Great job! thanks

Not applicable

@ Scott Schnoll

Does that mean that the Calculator for Exchange 2010 will not be updateted in the future and that calculator fpr Exchange 20010 will not be developed further?

Bernd

Not applicable

@Bernd, no.  There are two calculators.  One for Exchange 2013, and one for Exchange 2010.

Not applicable

@Bernd - In fact, I will be releasing an updated E2010 calc soon.  I've been holding off on it as I knew a certain grumpy Irishman and a few other folks would have commented on the release of an existing calculator when the E2013 wasn't out yet. :)

Ross

Not applicable

Thanks for the calculator. It's given me some guidance for our upcoming deployment. However, I am having an issue on the distribution tab. When I click on the Calculate button, I get runtime error "11", "Division by zero" and it clears everything from the page. Am I doing something wrong?

Not applicable

@Tony - thank you for helping with UM!  Perhaps you can chime in on my thread here on the forums; looking forward to completing this migration! social.technet.microsoft.com/.../32bd9392-4f9a-4acf-b086-6d2e0fc58bdb

Not applicable

@Eric - please send a copy of the calculator to the email address listed in the article.

Not applicable

THANKS!

Not applicable

Hi, I got the same issue as Eric McAnallen.

Not applicable

Great Work.

I want to inform you that the distribution sheet is not working correctly on one of my inputs. When I select two servers at primary site and one at secondary site the distribution sheet open a debug window. Can you please check and confirm if the calculator is working fine.

Thanks

Not applicable

Hi Ross,

First, thanks for this amazing job !

Can you tell me about the "Recommended Min Number of GC Cores" ?

The value should be about "Exchange servers Core Number" / 8, isn't it ?

Refering to : blogs.technet.com/.../ask-the-perf-guy-sizing-exchange-2013-deployments.aspx

"Active Directory sizing remains the same as it was for Exchange 2010. As we gain more experience with production deployments we may adjust this in the future. For Exchange 2013, we recommend deploying a ratio of 1 Active Directory global catalog processor core for every 8 Mailbox role processor cores handling active load, assuming 64-bit global catalog servers."

The storage Calculator, in our sizing environement, gives us a 51/1 result, there is maybe a mistake ?

Regards,

Julien

Not applicable

@Julien Taisne:

When you calculate required GC cores, the ratio 1:8 applies to the cores required to support active mailboxes ("Mailbox role processor cores handling active load") and not to all cores physically available on Exchange server.

So, for example, if you have 32 total cores on an Exchange server but only 16 of them are actually needed to support active mailboxes (as determined by the calculator), you will need only 16/8=2 GC cores to support this Exchange server's AD queries.

I hope this clarifies your question.

Not applicable

Since you cannot override the RAID settings when using 7.2K RPM drives, does this imply that Microsoft does not support that configuration? TechNet states you support all RAID types, but the calculator doesn't give you the latitude to make that decision. While you prefer RAID 1/0 when using slower disks, certain storage vendors have capabilities in the array that can offset some of the performance implication, such as storage pools, thin provisioning and fast cache.

Not applicable

POSSIBLE BUG??:  It seems like the calculator is taking my tier 3 mailbox count and multiplying it by 6 in the role requirements tab.  I put in 1000 and it shows as 6000.  

Not applicable

Never mind on the bug....  Not a bug.  Growth %

Not applicable

@ Boris Lokhvitsky

Thanks for your reply, indeed we've finaly find this ratio after some test with the storage calc.

regards

Not applicable

In the "Role Requirement" sheet -> Server configuration section ->the value for Recomended RAM configurattion - Is it per server or per data center ? eg: if the value of recommended RAM is showing as 96 GB of RAM , and I have 2 servers in the primary datacenter , does it mean , each server should have 96/2 = 48 GB RAM ?

Not applicable

@Mike - There are no plans to change the calculator to support RAID-5/6 with 7.2K disks.  While it is supported to deploy our testing in the past as shown that JBOD and RAID-1/0 deployments to be more suitable.

@Bineesh - RAM is per server.

Not applicable

VBA Code Nags...

Option Explicit should be everywhere  (missing on the forms and code behind the worksheets)

Constants should be explicitly typed (otherwise they are variants)

Use Longs instead of Integers

Password protect the code (even though easily hacked)?

Not applicable

Awesome, just in time for my current 2013 hybrid engagement :)

Not applicable

Question on some calculator results I'm seeing after hearing your presentations at TechEd...

Looking at the differences between selecting Site Resilient Deployment = Yes with 2 CAS/MB multi-role servers in the primary datacenter, and 2 in the secondary datacenter in an active/active single DAG deployment.

With our settings, the role requirements indicate 96GB RAM for each of the 4 servers, in order to support losing both servers in either datacenter.

If I run the same settings against Site Resilient Deployment = No, still keeping a single DAG with 4 multi-role CAS/MB servers, allowing for the failure of any 2 of the servers (in the same datacenter), the calculator indicates 48GB RAM required.

I'm missing what the "special sauce" is in a Site Resiliency scenario that would necessitate double the RAM.  In the site resiliency scenario, both datacenters are hosting 50% of the active user databases, so the servers are carrying the same 25% load in both cases in normal operation, with the possibility of hosting up to 50% of the load, should both servers in the other location fail.

In our case, our secondary datacenter is directly fiber connected and is essentially a remote extension of our primary datacenters, so while in a different subnet/AD site, there are no users resident in the second site.  Because of this, I'm thinking that I should use the numbers for a non-site resilient scenario, with two servers in each location across a single cross-subnet DAG.  Can anyone shed light on the different resource requirements here?  Thanks!

Not applicable

The totDBVolSpaceDAG value don't seem to take in account multi database per volume. there a IF that refer to VolArchitectyre<>"2 Volumes / Backup Set", however the VolArchitecture is set to "Multiple DBs / Volume"

Not applicable

Precision : we are in the scenario : NumDBCopies = 4, no log isolation and jbod evalution, the calculator show 2 DB / volume, but the calculator don't take that in account and multiply the number of volume per the number of database, doubling the total space req.

Not applicable

Thank you very much for this, an excellent guide to prep for hardware.  However, there is no mention of sizing for Public Folders.  In our production environment, we have almost a 1:1 ratio of PF's to users...in considering the migration from 2010 PF db to 2013 mailbox, should I account for these mailboxes as users - i.e., consider adding another 'Tier' of user class mailbox to this calculator, with calculated size and send/rcv per PF?  Thanks for any help on this!