We are allowing for a hot spare in the design but another might not be a bad idea. Thanks!
From: Joseph L. Casale [mailto:jcas...@activenetwerx.com] Sent: Sunday, October 14, 2012 9:14 AM To: MS-Exchange Admin Issues Subject: RE: DAG and Log+Database Design I might add that r5 isn't very realistic for this scenario given the size of the array. Whats the chance during a degraded state you loose another disc? High if you ask me... ________________________________ From: Rimmel, Carl [crimm...@hfhs.org] Sent: Friday, October 12, 2012 7:50 AM To: MS-Exchange Admin Issues Subject: DAG and Log+Database Design We are planning an 8-node DAG with a 6-node CAS Array. Each DAG node will host around 4,000 mailboxes. These will be HP DL380p G8 servers loaded with 25 300 GB 15K SAS drives, 22 of which will be available for either a split or unified Log\Database design. I have read a number of Exchange 2010 design articles that have indicated that separation of Log files from Database files is no longer as mandatory of a design parameter as it once was. In these scenarios, the recommendation typically assumes that at least 3 copies of each database exist within the DAG (and often there is a lag database as well). We plan on having 3 copies of each database. To maximize our available disk space, we are leaning towards a RAID 5 array utilizing all 22 drives without splitting the Logs from the Databases. Has anyone deployed 2010 in this manner? If so, any recommendations or caveats? I am most concerned with any performance impact that may be introduced by marrying the Log and Database transactions to the same array. We have engaged our HP vendor and they indicate that this design should be able to more than handle the IOPS for Exchange 2010. Thanks for any and all responses. ________________________________ CONFIDENTIALITY NOTICE: This email contains information from the sender that may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected from disclosure. This email is intended for use only by the person or entity to whom it is addressed. If you are not the intended recipient, any use, disclosure, copying, distribution, printing, or any action taken in reliance on the contents of this email, is strictly prohibited. If you received this email in error, please contact the sending party by reply email, delete the email from your computer system and shred any paper copies. Note to Patients: There are a number of risks you should consider before using e-mail to communicate with us. See our Privacy Policy and Henry Ford My Health at www.henryford.com<http://www.henryford.com> for more detailed information. If you do not believe that our policy gives you the privacy and security protection you need, do not send e-mail or Internet communications to us. --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
