Optimized item-level recovery for SharePoint

  • Article

Applies To: System Center 2012 - Data Protection Manager, System Center 2012 R2 Data Protection Manager, System Center 2012 SP1 - Data Protection Manager

Item level recovery for SharePoint farms is already supported by DPM 2010. However, the process was time consuming as it required the transfer of the entire database on a recovery point over the network to a staging location before you could recover an item.

System Center 2012 – Data Protection Manager (DPM) reduces the time and storage space required to restore an item by not requiring the entire database to be recovered and mounted, instead it attaches database files on the recovery point to a SQL Server instance remotely and recovers the item from the database.

This enhancement does not affect the protection or recovery of a SharePoint farm or database. For detailed steps on how to perform item-level recovery on SharePoint farms, see Recovering SharePoint Items.

Important

The SQL Server instance must run under an account that can be resolved by Active Directory services. This means that the SQL service must be running under a domain account, or under Local System or Network Service of the computer.

Warning

Item-level recovery must be performed in sequence one after the other. Parallel recoveries do not work.

This feature is available for farms on SharePoint 2007 and SharePoint 2010.

The following are not supported

  • Filestream databases

  • Tape recovery

  • SharePoint sites using Variations.

Item-level recovery of Filestream items

You must set the following registry key on the DPM server to enable SharePoint item-level recovery for items in SQL Server Filestream content databases.

Key

HKLM\Software\Microsoft\Microsoft Data Protection Manager\Configuration\SharePoint

Value

AutoTriggerUnOptimizedILR

Data

Type

DWORD

Note

When you try to recover a Filestream item, you will see a critical alert for recovery failure followed by an informational alert for a successful recovery. You should ignore the critical alert.

Forcing unoptimized recovery

DPM always tries optimized recoveries and switches to unoptimized if it is unable to do an optimized recovery. However, if unoptimized recovery is unable to start, set the following registry key and try the recovery. After the recovery is done, remove the registry entry.

Key

Software\Microsoft\Microsoft Data Protection Manager\Configuration\SharePoint

Value

DisableOptimizedILR

Data

1

Type

DWORD