Folks, - we have an existing 2007 in our domain - and are looking to setup a new server on our branch office. W2k3 Ent x64 sp2 R2 Looking to install Exchange 2007 sp1 We are using an IBM x3550 QC processor with 16 GB of ram C: Drive 70 GG D: Drive 69 GB For our exchange storagewe are looking to mirror our 2003 setup but I have heard conflicting topics on amout of disk space and storage requirements for each storage group. We are using and EMC SAN for our disk space requirement for the mail store. We were looking to partition the SAN as follows: - all are Raid 5 E: LOG drive 400 GB F: Storage 1 250 GB G: Storage 2 250 GB H: Storage 3 250 GB I: Storage 4 250 GB In each of thes SAN storage groups we were looking to create Exhange Storage groups with 2 Exhange Storage groups with 1 mailbox db per storage group this way each mailbox DB would be limited to 50 users each with a 2 GB limit. - keeping the mail db to 100 GB and hopefully manageable. Am I off track on this configuration? Recommendations? Thoughts? Thanks. -John

John.Leonard wrote: Folks, - we have an existing 2007 in our domain - and are looking to setup a new server on our branch office. ...... For our exchange storagewe are looking to mirror our 2003 setup but I have heard conflicting topics on amout of disk space and storage requirements for each storage group. What "2003 setup"? Did you mean to say you have Exchange 2003 in your existing domain? Anyway, that doesn't matter. Exchange 2003 storage design is different than Exchange 2007 storage design anyway. The primary difference is that you want a 1:1 ratio of SGs to DBs in E2k7 whereas in 2003 you did not. As for your actual storage design, I recommend you use two primary resources: http://technet.microsoft.com/en-us/library/bb738147(EXCHG.80).aspx http://msexchangeteam.com/archive/2007/01/15/432207.aspx Both of these links will help you determine, based on usage, what storage design would best work. Also keep in mind you want to keep transaction logs off of the disks that will be used for their respective databases. Additionally you want to keep your databases under a size that allows backups and restores to complete in your proper time window.