[For content updates, see
Newly published content for Microsoft System Center Data Protection Manager.]
You can recover Windows SharePoint Services items, such as lists and documents, from a DPM recovery point to the original site or to an alternate site.
The following requirements apply to an item recovery:
-
A single machine SharePoint farm running both SharePoint front-end and SQL Server 2005 SP2.
.gif) Note |
|---|
|
We recommend that you use Microsoft SQL Server 2005 with SP2 as your SQL instance.
The version of SQL Server must be the same or higher than what was installed at the time of backup.
SQL VSS Writer should be running on the recovery farm.
This machine must be separate from the DPM server, active directory and farm machines.
This machine must have enough storage space to hold the largest content database in the environment as the entire database is restored to the recovery farm so that the object can be retrieved, and then it is deleted.
|
-
If you protect a MOSS farm, then the recovery farm must also be MOSS.
-
The features and templates installed on the recovery farm must match those of the target farm at the time of backup.
If there were any customized templates added or modified on the protected farm, these must be added to the recovery farm to ensure successful recovery.
-
If a service pack or update is installed on the protected farm, the recovery farm must have the same service pack or update installed or item-level restore operations could fail.
-
Both the recovery and target farms must be in the same language and have the same language packs installed.
-
The target farm must contain a site collection with the same path as the original protected site. If the site collection does not exist, you can create an empty site collection with the correct path on the target farm before you perform the recovery.
| Note |
|---|
| The target farm is not necessarily the original farm where the object existed when it was protected. It is merely the farm where the object will reside when the recovery is complete. This is not going to be the recovery farm where DPMRecoveryWebApplication resides. |
- Ensure that no content database is already attached to the recovery web application (DPMRecoveryWebApplication) as this will cause recoveries to fail.
When you restore an item, DPM restores the database to the recovery farm, extracts the item from the recovery farm, and imports it into the target farm. During this process, DPM creates a temporary file on the recovery farm at a location specified in the Recovery Wizard. You should periodically delete the temporary files at that location.
To recover an item to its original location
-
Create a farm that DPM can use for the recovery. For more information, go to Creating a Recovery Farm.
-
In DPM Administrator Console, click Recovery on the navigation bar.
-
In the Protected data pane, expand the server that contains the farm you want to recover, double-click All Protected SharePoint Data, and then double-click the server farm name.
Content databases display in the Recoverable item pane.
-
Use the calendar and Recovery time menu to select a recovery point.
-
In the Recoverable item pane, select the content database, browse to the item that you want to recover and select it.
| Note |
|---|
| You can only select and recover one object at a time. If you want to recover more than one object, consider recovering a higher level folder to an alternate location and then recovering the individual objects from within the SharePoint Central Administration website. |
-
Click Recover in the Actions pane and confirm the recovery details on the Review Recovery Selection page.
-
On the Select Recovery Type page, select Recover to original site.
-
On the Specify Recovery Farm page, enter the information for the recovery farm you created in step 1, and then complete the wizard.
Either type in the FQDN (Fully Qualified Domain Name) of the recovery farm where the DPMRecoveryWebApplication has been created or browse for the server. Once the server has been selected, browse for the SQL instance on that server. Lastly choose the temporary location where the files will be stored on the recovery farm.
| Note |
|---|
| The recovery farm must have enough disk space to store the largest content database in the environment. Best practice would dictate that an additional 10-20% be allocated on the temporary storage volume to provide a cushion for growth and reduce the risk of running out of space when trying to recover time-sensitive SharePoint data. |
-
On the Specify Staging Location page, enter a directory where the SharePoint data will be temporarily stored pending recovery to the original site.
-
On the Specify Recovery Options page, specify whether the recovery point’s security settings or the original site’s security settings will be applied to the recovered data object in the Restore Security section.
This is an important consideration if there have been security settings changes since the recovery point was taken.
| Note |
|---|
|
The network bandwidth usage throttling is used when there are concerns about the restore process consuming excessive bandwidth.
The SAN Recovery option is only available if the attached SAN is capable of snapping clones and splitting clones.
The Notification section is simply to notify administrators and other personnel of the completion of the recovery process.
|
-
Confirm the settings on the Summary page and click Recover to begin the process.
To recover an object to an alternate location
| Note |
|---|
| An alternate location can be on the same SharePoint farm and merely using a different site name or port number. |
-
Create a farm that DPM can use for the recovery. For more information, go to Creating a Recovery Farm.
-
In DPM Administrator Console, click Recovery on the Actions pane.
-
In the Protected data pane, expand the server that contains the farm you want to recover, double-click All Protected SharePoint Data, and then double-click the server farm name.
Content databases display in the Recoverable item pane.
-
Use the calendar and Recovery time menu to select a recovery point.
-
In the Recoverable item pane, select the content database and browse to the item you wish to recover.
| Note |
|---|
| You can only select and recover one object at a time. If you want to recover more than one object, consider recovering a higher level folder to an alternate location and then recovering the individual objects from within the SharePoint Central Administration website. |
-
Click Recover in the Actions pane and confirm the recovery details in the Review Recovery Selection page.
-
On the Select Recovery Type page, select Recover to an alternate site.
-
On the Specify Recovery Farm page, enter the information for the recovery farm you created in step 1, and then complete the wizard.
Either type in the FQDN (Fully Qualified Domain Name) of the recovery farm where DPMRecoveryWebApplication has been created or browse for the server. Once the server has been selected, browse for the SQL instance on that server. Finally choose the temporary location where the files will be stored on the recovery farm.
-
In the Recovery target site section, enter the alternate site’s URL in the Target site URL: field.
| Note |
|---|
| The site URL entered into the Target site URL field must be based on the same site template as the site hosting the object which is being restored. For example, SharePoint will not allow an object created in a site using a ‘Wiki Site’ template to be restored onto a site created using the ‘Team Site’, ‘Blank Site’, ‘Blog’, or ‘Document Workspace’ templates. If custom templates have been used, those same templates must reside on the recovery farm as well as having been used to create the alternate site where the recovery is being made to. |
The recovery farm must have enough disk space to store the largest content database in the environment. Best practice would dictate that an additional 10-20% be allocated on the temporary storage volume to provide a cushion for growth and reduce the risk of running out of space when trying to recover time-sensitive SharePoint data.
-
On the Specify Staging Location page, enter a directory where the SharePoint data will be temporarily stored pending recovery to the alternate site.
-
On the Specify Recovery Options page, specify whether the recovery point’s security settings for the object being recovered or the alternate site’s security settings will be applied to the recovered data object in the Restore Security section. This is an important consideration if there have been security settings changes since the recovery point was taken.
| Note |
|---|
|
The network bandwidth usage throttling is used when there are concerns about the restore process consuming excessive bandwidth from bandwidth sensitive applications.
The SAN Recovery option is only available if the attached SAN is capable of snapping clones and splitting clones.
The Notification section is simply to notify administrators and other personnel of the completion of the recovery process.
|
-
Confirm the settings on the Summary page and click Recover to begin the process.
| Note |
|---|
|
|
See Also