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.
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.
jakethecatuk
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
ASKER
would you happen to know which directory the EX2010 mailbox server use to do the SMTP writes?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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?
is there any other LUN or separate spindles i would need to create for the DAG mailbox servers?
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