SharePoint Madness

All about SharePoint and Office365

Posts Tagged ‘Disaster Recovery SharePoint 2010’

Backup Strategy for SharePoint 2010

Posted by Amit Bhatia on February 5, 2013

We were asked to develop the backup strategy on SharePoint 2010 for one of our client. There were two web applications with 3 site collections. Please note that this article does not give steps on how to write backup powershell commands. Instead this talks about the backup strategy being adopted in an enterprise environment.

Web Application 1 hosts 2 Site Collection

Web Application 2 hosts 1 site collection

The SP 2010 Farm backup requires different strategies for Database backup and Farm/web/site collection backup. Here I give you an example of one Site collection. You may backup multiple site collection as well.

SQL Server Backup (Created by the SQL DBA)

The backups are broken up into Full Backups and Transaction log backups.

  1. Full Backup

The database backups are run via a SQL Server job named UserDatabases.Full Backups.  The Full backup job runs each night at 8:45pm in the evening.  They are written to the directory U:\SQL Backup\<dbname>\.  The naming convention is <dbname>_backup_yyyy_mm_dd_hhmmss_<uniquenumber>.bak.

The database backup files are kept for three days and are then deleted.

2.        Transaction Logs

The transaction log backups are run via a SQL Server job that runs every 30 minutes on the half hour and the hour throughout the day.  The SQL Server job is named UserDatabases.Log Backups.  The logs are written to the directory U:\SQL Backups\<dbname>\. The naming convention is <dbname_yyyy_mm_dd_hhmmss_<lognumber>.trn.  The log files are kept for two days then deleted.

3.     Mirroring

The following Sharepoint databases are mirrored to the DR server  continuously.

  • WSS_Content (content database)

4.    Networker backups

The database files and the transaction logs are backed up by Networker daily at 9:00pm.

SharePoint Farm, Site Collection and Content Database Backup

We have three scheduled tasks running on the SharePoint Production Application Server.

  1. Full SP Farm Backup – It takes complete backup of the SharePoint Farm on which the SharePoint sites are hosted. The complete Farm backup includes backup of the farm configuration, Web Applications, IIS Configurations, Site Collections, Service Application databases, Content databases, and Configuration databases. This scheduled task calls the backup script to perform the backup and runs at 11:59 PM every Saturday (once in a week).
  2. RunDifferentialSPFarmBackup – It takes differential backup of the SharePoint Farm on which the SharePoint sites are hosted. It runs at 8:00 PM daily.
  3. HourlyContentDBBackup – It takes hourly backup of Content Database in order to ensure we have the latest Content database available in case of any disaster.

The Networker runs daily at 9:00 PM to copy these files over to the backup media tapes or devices.

The backups are run by powershell command tied to the Windows task scheduler.

Hope this simple strategy would help you in deciding your backup and Disaster recovery process in your enterprise.


Posted in SharePoint 2010 | Tagged: , | 1 Comment »

Searching For Value

"Helping You Master the Game of Investing"

Ideas with Conviction

The best thing about investing is the ease with which you can move your capital across different businesses, helping you capitalize on every opportunity..

CFA Institute Enterprising Investor

Practical analysis for investment professionals

Journeys of a Bumbling Trader

Learnings and Thoughts on Trading, Macroeconomics, Value Investing, Quantitative Finance, and Accounting

Flirting with Models

Research Library of Newfound Research

Alpha Ideas

Investment Blog for the Indian Markets

Fundoo Professor

Thoughts of a teacher & practitioner of value investing and behavioral economics