Exchange 2010 LUN design question

hello, we are designing our EX2010 architecture and i have a question about the spindle design.
i have the DB and Logs on separate raid groups [spindles] however for performance should i also create a separate raid group for the smtp write directory? [in ex2003 it was the mailroot/vsi1 directory.

thx - S.
siber1Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

jakethecatukCommented:
i wouldn't worry too much about SMTP to be honest with you as the speed of outgoing e-mails will be dicated more by your internet connection
0
siber1Author Commented:
would you happen to know which directory the EX2010 mailbox server use to do the SMTP writes?
0
tigermattCommented:

The SMTP queue database in E2010 is located under the Exchange Install Directory\Transport Roles\data\queue.

If you want to change this you need to edit the EdgeTransport.exe.config file, as there is no option in the GUI to do so: http://technet.microsoft.com/en-us/library/ee681659.aspx. You are looking specifically at QueueDatabasePath and QueueDatabaseLoggingPath.

Unless the mail profile of your users is huge, or you have an astronomical number of users, I wouldn't be too concerned over your queue directory. Today's modern disks aren't THAT slow at read/write so I'd focus instead on the spec of the new Exchange boxes or improve high availibility offerings with DAG with the money saved on a separate array for SMTP queues! We have a number of transport boxes here serving an email infrastructure for several thousand users, but I haven't ever moved the SMTP queue location.

BTW: the transport queue uses circular logging on its transaction logs, so it's not really worth splitting database and logs for disaster recovery purposes.

Matt
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
siber1Author Commented:
Thanks for the info Matt. so in the DAG mailbox storage design, should i just carve out a separate RG/LUN for Database and Logs. so basically, 2 LUNs per Database on separate spindles
is there any other LUN  or separate spindles i would need to create for the DAG mailbox servers?

0
tigermattCommented:

The thing to remember with a DAG is it isn't designed for shared storage, so whichever way you go about it, you'll need separate LUNs for database + logs for each member server in the DAG. In fact, a DAG is quite happy running off the local storage in the separate servers...

So yes, 2 LUNs per database (one per DAG member) should be fine. If you have an even number of DAG servers, you'd need a third box to site your witness server on (used to ensure there's always a majority vote to maintain quorum and prevent a split brain cluster when there's an even number of members in the cluster). However this will quite happily sit on a separate Hub Transport server or just another member server on your network. It requires just a few megabytes at most, so doesn't need a dedicated box or its own LUN, just a third physical box you're happy to site it on.

Clearly if you're using LUNs on a SAN you'll want to ensure the SAN has redundancy so that's not a single point of failure in your DAG, but I'm sure you've considered that. :)

Best of luck with this endeavour!

Matt
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.