Troubleshooting SharePoint Protection and Recovery
Applies To: System Center Data Protection Manager 2007
This topic documents the following known issues and resolutions relating to protection and recovery of SharePoint data protected by System Center Data Protection Manager (DPM) 2007:
Windows SharePoint Services documents checked out or in the Recycle Bin during backup cannot be restored
DPM Protection Report shows incorrect data for Windows SharePoint Services farms
Windows SharePoint Services Protection Not Working Properly
SharePoint site or item recovery fails when a shared folder is used as a temporary location
SharePoint farm protection fails with ID 30111
SharePoint index backups fail during profile import
ConfigureSharepoint.exe fails with error code 997
Windows SharePoint Services documents checked out or in the Recycle Bin during backup cannot be restored
In Windows SharePoint Services, if documents are checked out from the documentation library or are located in the first or second stage of the recycle bin during the time your data was backed up, they cannot be restored. To restore these documents, you must pick a point in time that the documents were not checked out or in the recycle bin before restoring the data.
DPM Protection Report shows incorrect data for Windows SharePoint Services farms
DPM does not calculate the expected number of recovery points correctly in the DPM Protection Report. Therefore the percentage that shows the historical recovery point availability against the existing recovery points is incorrect.
Windows SharePoint Services Protection not working properly
If you are having trouble continuing protection of a Windows SharePoint Services site that is already part of a protection group after adding a content database, check to see if you have met all the DPM 2007 prerequisites for protecting Microsoft SQL Server 2005. In the process of adding a content database for protection, DPM may implicitly protect the backend SQL database without validating the prerequisites.
SharePoint site or item recovery fails when a shared folder is used as a temporary location
When a shared folder is specified as the temporary location for the recovery of a SharePoint site or item the recovery will fail. To resolve this issue, use a local folder as the temporary location for either the recovery farm or the production farm.
SharePoint farm protection fails with ID 30111
If your SharePoint farm protection is failing with the following error in the Jobs tab in the Monitoring pane on Administrator Console, it could be because that there is a volume with no mount points on the front-end web server of your SharePoint farm. To resolve this issue, assign a mount point or drive letter to the dismounted volume and perform a consistency check.
SharePoint index backups fail during profile import
Due to constraints in SharePoint, DPM cannot pause a profile import. Backups scheduled to run when profile import is taking place will fail. The backups fail with error code 32010.
Message: DPM was unable to get the Content Sources of the SSP <Name of data source>; to a consistent state.
Recommended action:
Check to see that the protected SSP is online and running.
Check to see that the WSSCmdletWrapper DCOM component is configured correctly on the front-end Web server hosting the protected farm.
Retry the operation and make sure no other application or process is trying to resume the crawl of the SSP during backup.
ConfigureSharepoint.exe fails with error code 997
If this is happening after you have changed the administrator password, do the following to resolve the issue.
From the command prompt, run dcomcnfg.
In the DCOM Config utility, search for the WSSCmdletWrapper object. Right-click the object and select Properties.
On the Identity tab, enter the new password.