Ross Smith IV announced at the Microsoft Exchange Team Blog that the Exchange 2010 Mailbox Server Role Requirements Calculator has been updated to version 6.3.
According to the Updates Tracking page, here’s the list of changes:
Within the Total Disk Requirements results pane, you now will have three options:
- As Calculated – this is the default behavior where the calculator determines the most efficient design that ensures the least number of disks are deployed, while still ensuring you have minimized single points of failure by utilizing RAID and/or JBOD based on the decisions found in the "RAID Storage Architecture" and "JBOD Storage Architecture" tables.
- Entirely on RAID – Selecting this option outputs the results with each server utilizing the RAID storage defined in the RAID Storage Architecture results section.
- Entirely on JBOD – Selecting this option outputs the results with each server utilizing JBOD storage as defined in the JBOD Storage Architecture. There are two caveats worth mentioning here – first, if the design doesn’t support JBOD, then JBOD isn’t a viable option (e.g., you don’t have 3 HA copies); second, choosing this option may result in a situation where you have a single point of failure (e.g., having only a single copy on JBOD in the secondary datacenter).
- Message profiles have been simplified in order to be more consistent with the rest of our documentation and partner tools. For example, instead of using "20 sent/80 received", the calculator now simply uses "100 messages". The individual breakdown isn’t consequential to the overall design of the mailbox server IO and capacity planning algorithms.
- Added additional column to the "Active Database Configuration / DAG" table on the Role Requirements tab to expose configurations where you will have a portion of your databases activated in the secondary datacenter as a result of a failure event in the primary datacenter.
- Improved "Environment Configuration" table on the Role Requirements tab to indicate the Number of Mailbox Servers and Lagged Copy Servers / DAG in each datacenter.
- Re-ordered tables in the Role Requirements Results section.
- Fixed the Secondary datacenter Active and Passive megacycle calculations to take into account the number of activated databases based on the failure mode the secondary datacenter can support.
- Fixed the number of Active Databases / Secondary Datacenter Server after a first primary datacenter server failure to not display #VALUE for 2-node site resilient DAG solutions.
- Improved the number of Active Databases after double server failure in the primary datacenter site resilient calculation to deal with 3 servers in the primary datacenters, as well as, when there are 2 copies in the primary datacenter.
- Fixed an issue for site resilience scenarios that resulted in #DIV/0 errors as a result of determining the number of copies that can be mounted in the event of a double server failure when the solution only has 2 servers in the primary datacenter.
- Fixed an issue for site resilience scenarios that ensures that double failure events don’t result in more databases being activated on the remaining primary datacenter servers than possible when only 2 copies exist in the primary datacenter.
- Fixed CPU core calculations to take into account the total number of DAGs being deployed in the situation.
- Fixed active megacycle calculation to exclude database copy overhead for standalone deployments.
- Fixed Lagged Copy Storage Architecture formula to be HA aware.
- Fixed Secondary Datacenter Storage Architecture formula to ensure there is at least 1 HA copy being deployed in secondary datacenter.
- Updated storage design tab improvements based on user feedback and added "in primary datacenter" for input HA/lagged copy instances.
- Fixed formula for JBOD disk type to accurately reflect when there was insufficient database copies vs. requiring RAID.
- Updated comments on various cells.
To get the detailed instructions on how to use it, read Exchange 2010 Mailbox Server Role Requirements Calculator.
To download the tool itself, click here.