Published: January, 2016
Microsoft SharePoint 2013 backup and recovery is a service that doesn't often get the attention it deserves — unless it’s too late. Organizations adopt SharePoint for collaboration, document management, and as an application and development platform that grows organically and often becomes mission-critical to business users. IT departments are often in the position of playing catch-up when it comes to planning, testing and formalizing SharePoint (and SQL Server) operational activities, such as backup and recovery to maximize data Availability.
Many organizations have not fully tested specific platform and data-availability backup strategies in SharePoint 2013 because they lack SharePoint-specific tools for operational activities such as backup and recovery, especially granular recovery. Many companies restore with SQL Server backups and recovery farms. This approach is labor intensive and time-consuming, especially for large organizations with huge databases and backup and recovery responsibilities distributed among multiple departments (SharePoint and SQL Server teams, for example). In addition, users often want documents, lists and libraries to be available 24/7. SQL Server backups simply don’t facilitate speedy recoveries. Consequently, users and business processes are often affected by delayed data recovery.
In this white paper, find out why it's critical for SharePoint data to be highly available from service-level and compliance points of view. Read a list of approaches for ideal SharePoint 2013 backup strategies, along with best practices for defining service levels for the business, architecture, operations and quality-assurance. Multiple stakeholder points of view for recovery strategies are also explained, as well as specifics of granular recovery in SharePoint environments and Veeam® Explorer™ for Microsoft SharePoint, a free toolset for item-level recovery of SharePoint data.