With SharePoint becoming more entrenched in organizations its importance to the business has increased significantly. SharePoint might not be directly linked to revenue generation in your organization but it’s most likely become a tool that people use daily and when there is a failure or data loss, you hear about it.

SharePoint is unlike other products organizations have adopted, its very nature is an IT administrators nightmare – puts the power into the hands of the users. Specifically its value  proposition to the business creates support pain for IT. There is no doubt that users see the power of SharePoint, its adoption in organizations creates a sprawl – entrenches deep and wide in organizations. One day IT wakes up and it realizes there are more stakeholders than they expected using SharePoint and meeting their needs / expectations seems impossible.

So where do you start? The following  are the areas you must cover to create a comprehensive backup and recovery plan:

  • Stakeholder Requirements
  • Defining SLAs
  • Components of a Backup and Restore solution
  • Technical Architecture
  • Backup and Restore Toolsets
  • Slip Streaming and WSPs
  • Policy and Process
  • Training and Awareness
  • Change Control
  • Test Plan
  • Proof of Concept/Pilot
  • Sign off with Owners
  • Backup Schedule
  • Governance and Communications
  • Backup and Restore Process
  • Further Reading

This article will provide you with a holistic view of SharePoint backup and restore with a focus on key subjects that must be covered in order to plan, design, implement and manage a SharePoint backup and restore solution that meets requirements and is sustainable.

Publishing date September 2011.