Hi

I am using DPM 2012 SP1 to protect Sharepoint 2013.

The protection group is created and works fine.

I am trying to recover a document from the DPM and it is failing. I am using recovering to the orignal site and recovering without using a recovery farm.

The error that I get is: DPM was unable to export item XXXXX from the content database XXXXXX . Exception message = Source URL is Absent.(ID 32017)

From the WssCmdletsWrapperCurr.errlog i see that it could successfully add UnAttachedContentDatabase.

The Warning that i see is this:

18CC 2054 11/08 16:33:20.548 31 WssExportHelper.cs(494)   WARNING The specified Folder Url [XXXXXX/ s Documents/] is absent in the database
18CC 2054 11/08 16:33:20.548 31 WSSCmdlets.cs(451)   WARNING Caught Exception while trying to export Url [xxxxx/test/Mukuls Documents/3.PNG] to File [E:\Temp\DPM_c474b126_078a_479b_bea8_1ee97c3945eb\cmp\].
18CC 2054 11/08 16:33:20.548 31 WSSCmdlets.cs(1269)   WARNING --------------------------------------------------
18CC 2054 11/08 16:33:20.548 31 WSSCmdlets.cs(1270)   WARNING Exception Message   =
18CC 2054 11/08 16:33:20.548 31 WSSCmdlets.cs(1270)   WARNING Source Url is Absent
18CC 2054 11/08 16:33:20.548 31 WSSCmdlets.cs(1271)   WARNING Exception Stack     =

I have searched around blogs for the solution but no results.

All the help is hugely appreciated.

Regards

Mukul

Just an add-on.

I am using the same SQL instance for staging as the final recovery point. As in for the staging SQL instance i am using the SQL instance of the Sharepoint server.

Can that be a source of my problem.

Opened a case with Microsoft and found the solution.

It happens when we use managed paths and is a known issue with DPM.

Alternative is to manually recover the whole DB and then extract the document.

• Marked as answer by Mukul Rathi Wednesday, December 11, 2013 4:51 PM

Opened a case with Microsoft and found the solution.

It happens when we use managed paths and is a known issue with DPM.

Alternative is to manually recover the whole DB and then extract the document.

• Marked as answer by Mukul Rathi Wednesday, December 11, 2013 4:51 PM

Opened a case with Microsoft and found the solution.

It happens when we use managed paths and is a known issue with DPM.

Alternative is to manually recover the whole DB and then extract the document.

• Marked as answer by Mukul Rathi Wednesday, December 11, 2013 4:51 PM

Opened a case with Microsoft and found the solution.

It happens when we use managed paths and is a known issue with DPM.

Alternative is to manually recover the whole DB and then extract the document.

• Marked as answer by Mukul Rathi Wednesday, December 11, 2013 4:51 PM

Opened a case with Microsoft and found the solution.

It happens when we use managed paths and is a known issue with DPM.

Alternative is to manually recover the whole DB and then extract the document.

• Marked as answer by Mukul Rathi Wednesday, December 11, 2013 4:51 PM

Any updates on this? Are you saying that DPM cannot be used to perform item level restores on content under a managed path (I assume you mean a wildcard managed path)? That would be a HUGE problem as we have only one site on an explicit managed path (the root) and hundreds of sites under the "sites", "projects" and "personal" managed paths.

Can you offer clarification?