You have to take a holistic approach to this to really understand why it landed on 667GB. So, you start with mailbox size quota and user count. In this case we have 24,000 users and a 2GB quota from each user. You then calculate IO requirments for those users (the E2010 Mailbox storage calculator is the tool of your dreams for all of this by the way, just in case you didn't know about it). You then calculate how many mailbox servers you need to support 24,000 users using all this informaiton, with the understanding that using 1 x 1tb 7.2K SATA hard drive will host each log/database pair. SOO..with all that being said:
6 mailbox servers equals 102 active databases (16 databases per server) and 204 passive copies per server (DAG allows 16 copies of a database) which brings us to a total of 306 databases. We don't really care about that though, lets focus on the active number of databases.
24,000 users divided by 102 active databases = 235 mailboxes per database. <--I think this is the part you were missing
235 Mailboxes @ 2 GB's per mailbox (2GB is what you want to be your max mailbox size, not a hard limit, you decide) + whitespace + dumpster + 20% growth factor equals 635 GB's per database.
Transaction log generation based on message profiling indicates that for each database there will be 5.6 GB of tlogs per day, give yourself 3 days of growth (23GB) + content indexing (63 GB) and wallah.
635 + 23 + 63 = 900 GB approximatly. The last step is to verify that the disk itself can handle your IOPS requirments, and in this case it falls well within acceptable range.
I know, more than you asked for. Anyways, the 667 GB number is based off of the maximum allowed number of active databases (102), which divides into the maximum number of mailboxes (24,000), and of course the maximium mailbox size (2GB). Thats how it arrives.
I hope I made that clearer instead of more messed up.
J.
If it was helpful, vote for it. If it answered your question, mark it as answered. Small thing to do for free help from a strong community
