Restoring SharePoint databases unless they are all internally inconsistent isn't supported (which also applies to the built-in stsadm backup functionality) - which is why SharePoint specific backup products proliferate. That said, unless your load is very high, taking a regular SQL Server backup will work fine.
Cheers Ken From: Bob Fronk [mailto:b...@btrfronk.com] Sent: Saturday, 15 May 2010 2:30 AM To: NT System Admin Issues Subject: RE: SharePoint - SQL Backend setup Yes.... Using DPM, but I like the extra protection since it is so little disk cost! Can't have too many backups! From: Ken Schaefer [mailto:k...@adopenstatic.com] Sent: Friday, May 14, 2010 2:22 PM To: NT System Admin Issues Subject: RE: SharePoint - SQL Backend setup Are you using DPM to backup SharePoint? In which case the DB backup LUN is not required. DPM will backup SQL Server DBs and index the content via the SharePoint WFE. Cheers Ken From: Bob Fronk [mailto:b...@btrfronk.com] Sent: Friday, 14 May 2010 9:04 PM 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 ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
