Prerequisites for SharePoint protection
Updated: May 13, 2016
Applies To: System Center 2012 SP1 - Data Protection Manager, System Center 2012 - Data Protection Manager, System Center 2012 R2 Data Protection Manager
Before you deploy DPM to protect SharePoint do the following:
Review the release notes and The Supported and unsupported scenarios in DPM for any SharePoint issues.
Verify the support for SharePoint versions and backup scenarios in the DPM protection support matrix.
Note that:
You’ll need to install the DPM protection agent on every server in the SharePoint farm, including SQL Servers. See Installing Protection Agents. The only exception is that you only install it on a single Web Front End (WFE) server. For example if you have a single farm with two WFE servers, an index server and a two-node SQL Server cluster you’d install the agent on the index server, both nodes in the SQL Server cluster, and one of the WFE servers. This is because WFE servers don’t host content. DPM only needs the agent on one of them to serve as the entry point for protection.
By default when you protect SharePoint all content databases (and the SharePoint_Config and SharePoint_AdminContent* databases) will be protected. If you want to add customizations such as search indexes, templates or application service databases, or the user profile service you’ll need to configure these for protection separately. Be sure that you enable protection for all folders that include these types of features or customization files.
Remember that for DPM runs as Local System and to backup SQL Server databases it needs sysadmin privileges on that account for the SQL server. On the SQL Server you want to back up set NT AUTHORITY\SYSTEM to sysadmin.
For every 10 million items in the farm, there must be at least 2 GB of space on the volume where the DPM folder is located. This space is required for catalog generation. To enable you to use DPM to perform a specific recovery of items (site collections, sites, lists, document libraries, folders, individual documents, and list items), catalog generation creates a list of the URLs contained within each content database. You can view the list of URLs in the recoverable item pane in the Recovery task area of DPM Administrator Console.
n the SharePoint farm, if you have SQL Server databases that are configured with SQL Server aliases, install the SQL Server client components on the front-end Web server that DPM will protect.
Protecting application store items isn’t supported with SharePoint 2013.
DPM doesn’t support protecting remote FILESTREAM. The FILESTREAM should be part of the database.
Before you can protect a computer running Office SharePoint Server 2007, you must apply the update in KB941422.
If you use the Office SharePoint Server Search service, before you can protect Office SharePoint Server 2007 SP1 data, you must apply updated in Microsoft KB articles: