SharePoint 2010 Backup Strategy
Posted on 2012-09-12
I need some help with creating a backup strategy for SharePoint 2010, backend using SQL 2008 R2. Can someone please give some insight, or point me in the right direction to a good site to read about it.
I've read a number of things, but it's all kind of confusing. What technology should be used, PowerShell or SQL backups?
I've read that Sharepoint should be used for the config and central administration content database backups...but then SQL backups can be used for all the other databases. SharePoint should be the only option for the config/administration content database, because if you try to restore a SQL backup of these databases you'll corrupt the database. Can someone cofirm and/or deny, with some explanation?
If SharePoint should be used for those two databases, then why not simply use SharePoint for all databases? I'm assuming that SQL backups would be more efficient, but what else would I be gaining from using SQL backups? Is it just point-in-time recovery, with the transaction logs?
It seems as though I'd be creating a headache for myself if I were to backup some of the databases using SharePoint and SQL backups for other databases.
Point is, I need to create a strategy and I'd like to know what I'm talking about before making any recommendations.