Agree, maybe just mirror the backup volume, and the extra drive can be a hot spare if your raid/cabinet support that feature ?
Erik Goldoff IT Consultant Systems, Networks, & Security ' Security is an ongoing process, not a one time event ! ' From: Jim Holmgren [mailto:[email protected]] Sent: Friday, May 14, 2010 9:21 AM To: NT System Admin Issues Subject: RE: SharePoint - SQL Backend setup Bob, Given the number of disks you have to work with – that is probably the config I would use. My only ‘concern’ would be performance of the RAID5 for backups – RAID5 isn’t optimal for write-intensive applications. But…unless you can scare up another disk so you can go 0+1 for the backups, or maybe go with a RAID1 for backups and leave one drive as a hot spare (if that gives you enough capacity) – I’d say your config is pretty decent. Btw…some decent advice on this site if you want to really segment your databases and go all-out to optimize the SQL performance: http://www.sharepointjoel.com/Lists/Posts/Post.aspx?List=0cd1a63d-183c-4fc2- 8320-ba5369008acb <http://www.sharepointjoel.com/Lists/Posts/Post.aspx?List=0cd1a63d-183c-4fc2 -8320-ba5369008acb&ID=227> &ID=227 Jim Holmgren Manager of Server Engineering XLHealth Corporation The Warehouse at Camden Yards 351 West Camden Street, Suite 100 Baltimore, MD 21201 410.625.2200 (main) 443.524.8573 (direct) 443-506.2400 (cell) www.xlhealth.com From: Bob Fronk [mailto:[email protected]] Sent: Friday, May 14, 2010 9:04 AM To: NT System Admin Issues Subject: SharePoint - SQL Backend setup I am designing my SQL server for a SharePoint farm. I have an iSCSI array with 15 – 420GB SAS drives. I want to use the array to house the transaction logs, database and backups. My thought is to use two drives in a RAID1 for the transaction logs (420GB), Three drives in a RAID5 for the DB Backups (837GB) and Ten drives in a RAID 10 for the database (2TB). The server will be backed up by DPM, so the DB Backups volume won’t need to hold but a day or two of backups. Any SQL gurus see a problem with this setup? BF CONFIDENTIALITY NOTICE: This email, including attachments, is for the sole use of the intended recipient(s) and may contain confidential and/or protected health information. Under the Federal Law (HIPAA), the intended recipient is obligated to keep this information secure and confidential. Any disclosure to third parties without authorization from the member of as permitted by law is prohibited and punishable under Federal Law. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. NOTA DE CONFIDENCIALIDAD: Este mensaje incluyendo cualquier anejo es para uso exclusivo del (los) destinatario (s) y puede incluir información confidencial y/o información de salud protegida. La Ley Federal (HIPAA) establece que el destinatario está obligado a mantener la información confidencial y sequra. HIPAA prohíbe y castiga cualquier divulgación a terceras personas sin autorización del afiliado o permitido por ley. Si usted no es el destinatario, redirija esta mensaje al remitente, y destruye cualquier copia existente del mensaje original. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
