none
DPM and SharePoint Item Restore Restored Item is not the same RRS feed

  • Question

  • I want to be sure that my expectation of DPM is correct for SharePoint Item Restoration. If I create a restore point a week ago and it includes documents and list items from a site. Those items will contain the Created dates in the past and the Created By and Modified By of the original user.

    Now, a week later, if I restore one of those items, it has a Modified date of today and a Modified By of the System.

    Is this the expected behavior? It seems that this is not a perfect solution because the item is not the same as it was when it was backed up. From an audit perspective I have lost my audit trail.

    Does it restore the versions of items when the item is restored?

    Please tell me I have something misconfigured, this is my first stab at working with DPM 2012 and SharePoint 2013. I have not found any definitive installation instructions on TechNet.

    I'd love for this to be a solution for my clients.

    Thanks!


    Matthew McDermott, MVP SharePoint

    Tuesday, January 21, 2014 1:53 PM

All replies

  • Hi,

    DPM simply invokes sharepoint export and import API's to restore items, so it's sharepoint that is doing the restore to the destination.

    Be sure to select the option to "Apply the security settings of the recovery point version" - that sometimes makes a difference.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Tuesday, January 21, 2014 11:00 PM
    Moderator
  • Mike,

    Thanks that did make a difference. Though I wonder about the use of the word "sometimes". Is there any documentation on when it does not work?

    Is there any reference for when you would restore the document and not the associated library item?

    Is there any documentation on why you can only associate one item in a recovery? I see for document libraries that I can pick the document or the item, but not both. When would I choose one or the other?

    Is the version history included?

    After running through the Restore dialog several times, each time supplying the exact same info, I also wonder if there is a way to supply a "Restore Template" (or simply "Save as Default" so that I don't have to constantly repeat the same procedures (possibly making an incorrect choice) 

    Bottom line, has anyone documented what is and, more importantly, what isn't protected beyond the broad statement that "Content IS and Service Apps are not protected". For example, it appears that there may be issues with content under a Managed Path. I can restore content into root sites but have been unsuccessful for any content under a managed path.

    I'd love to recommend DPM to clients, but there are too many questions right now.


    Matthew McDermott, MVP SharePoint


    Wednesday, January 22, 2014 4:12 PM
  • Hi,

    <snip>
    Bottom line, has anyone documented what is and, more importantly, what isn't protected beyond the broad statement that "Content IS and Service Apps are not protected".
    >snip<

    Please review this blog, it still applies to latest sharepoint / DPM versions.

    http://blogs.technet.com/dpm/archive/2010/05/10/how-to-be-sure-that-your-sharepoint-farm-is-fully-protected.aspx

    I will have one of our dpm sharepoint engineers try to help with the other questions. 


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Wednesday, January 22, 2014 4:32 PM
    Moderator
  • Thanks Mike, 

    That post is pretty generic for SharePoint 2010 and DPM 2010. I am specifically talking about SharePoint 2013, SQL 2012 and DPM 2012. Considering what is at risk and the competition from 3rd parties like AvePoint, I'd like to know how DPM competes.

    I look forward to responses to the specifics above.


    Matthew McDermott, MVP SharePoint

    Wednesday, January 22, 2014 4:41 PM
  • **Is there any documentation on when it does not work?

    -> I am not aware of any situations where it does not correctly restore the user and time/data appropriately.

    **Is there any reference for when you would restore the document and not the associated library item?

    -> I’m not totally sure what you are asking here.  If you are talking about restoring a document for instance, the restore process just includes selection of the file and then picking the options to use for the restore. 

    **Is there any documentation on why you can only associate one item in a recovery? I see for document libraries that I can pick the document or the item, but not both. When would I choose one or the other?

    -> Since we are leveraging the SharePoint API for doing the restore, the limitation is likely in there.  Unfortunately, the only option in this case is to restore each file one at a time.  The good news is that you should hopefully be leveraging an optimized ILR and that means the process is much faster.  This is something that will happen if it is able to, so there are no settings to tweak or manage for this.

    -> If you want to check to see if you are using ILR, you can look at the jobs immediately after doing a restore.  If you see 3 straight SharePoint Import/Export entries, then it is optimized.  If you see one disk restore and then two SharePoint Import/Export entries, then it is using an unoptimized ILR process.

    **Is the version history included?

    -> Yes, when restoring a file with SharePoint ILR, it will also restore all previous versions and version history with associated user names.

    **After running through the Restore dialog several times, each time supplying the exact same info, I also wonder if there is a way to supply a "Restore Template" (or simply "Save as Default" so that I don't have to constantly repeat the same procedures (possibly making an incorrect choice)

    -> The only way to do something like this would be to create a script in PowerShell that would do what you want.  I don’t have anything like this created already and haven’t played with anything like it.

    **Bottom line, has anyone documented what is and, more importantly, what isn't protected beyond the broad statement that "Content IS and Service Apps are not protected". For example, it appears that there may be issues with content under a Managed Path. I can restore content into root sites but have been unsuccessful for any content under a managed path.

    -> I’m not familiar with “Managed Path”, so I can’t talk to that without more knowledge on it.  I can tell you that there are some limitations around protecting a farm with a SQL Always On back end and SQL filestreams that are not local.  Outside of that, I would have to see what is going on in order to better address the question.

    I hope this helps some.


    Thanks, Chris - [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights

    Friday, January 24, 2014 6:12 PM
  • Thanks Chris!

    Clarification so you may complete this thread.

    **Is there any documentation on when it does not work?

    -> I am not aware of any situations where it does not correctly restore the user and time/data appropriately.

    I discovered this right away buy not selecting the correct restore option. (Apply the security settings of the recovery point version)

    **Is there any reference for when you would restore the document and not the associated library item?

    -> I’m not totally sure what you are asking here.  If you are talking about restoring a document for instance, the restore process just includes selection of the file and then picking the options to use for the restore. 

    In the list of restorable items there is a pair available, one is the document and the other is the library item. It has to do with how DPM is displaying the SharePoint content. Very confusing.

    **Bottom line, has anyone documented what is and, more importantly, what isn't protected beyond the broad statement that "Content IS and Service Apps are not protected". For example, it appears that there may be issues with content under a Managed Path. I can restore content into root sites but have been unsuccessful for any content under a managed path.

    -> I’m not familiar with “Managed Path”, so I can’t talk to that without more knowledge on it.

    This is disconcerting. Managed Paths are everything in SharePoint. In order to create 1000s of sites under a URL the "Sites" managed path is presented so I can create sites under "http://intranet/sites/SharePoint/" and "http://intranet/sites/SQL" and "http://intranet/sites/HR", etc. Sites is the out of the box path, for the My Site Host it's "personal" though as an admin I can create different paths.

    I may have 100s or 1000s of sites under the "sites" managed path. So far I have been unable to restore any content to these sites. I really hope it's something I am doing wrong. But others have raised this issue and I have yet to see any resolution.

    Again, thanks for the conversation.

    Matthew McDermott, MVP SharePoint

    Friday, January 24, 2014 6:34 PM
  • Bump, any word on the restoration to a managed path? I have searched around and seen others report the issue but I have not seen a resolution. 

    I have been unable to get any content to restore to Sites or Personal managed paths.

    Thanks!

    M


    Matthew McDermott, MVP SharePoint

    Tuesday, February 4, 2014 12:49 PM
  • Hi, I think there is no difference on being or not under a managed path, in terms of DPM restoration. We have web applications with many managed paths and we have had no issues restoring site collections. After all DPM uses the SharePoint API under the hood and that means that a restore of a site collection is done via a Backup-SpSite from an unattached database, then restore-spsite from the extracted data.

    I hope this clears your question.

    I agree with you that sometimes the documentation is not very clear and uses vague statements. In my experience, the most clear statement of what you get backed up with sharepoint protection is:

    - Admin DB
    - Config DB
    - All databases marked as Content Database (i.e. all content databases attached to web applications at the moment of the Recovery Point creation)

    one thing is to backup the configuration DB, and another is to be able to restore it, but that is another problem.

    Everything else (service applications, service application DBs, every other thing not included into the content databases) must be protected in other ways.

    Hope this helps

    Roberto

    Thursday, February 20, 2014 2:01 PM
  • Hi, I think there is no difference on being or not under a managed path, in terms of DPM restoration. We have web applications with many managed paths and we have had no issues restoring site collections. After all DPM uses the SharePoint API under the hood and that means that a restore of a site collection is done via a Backup-SpSite from an unattached database, then restore-spsite from the extracted data.

    I agree with you that sometimes the documentation is not very clear and uses vague statements. In my experience, the most clear statement of what you get backed up with sharepoint protection is:

    - Admin DB
    - Config DB
    - All databases marked as Content Database (i.e. all content databases attached to web applications at the moment of the Recovery Point creation)

    (as a side note,one thing is to backup the configuration DB, and another is to be able to restore the farm with it, but that is another problem).

    Everything else (service applications, service application DBs, every other thing not included into the content databases) must be protected in other ways.

    Hope this helps

    Roberto


    • Edited by Roberto MD Thursday, February 20, 2014 2:02 PM
    Thursday, February 20, 2014 2:01 PM
  • Roberto,

    Thanks, I agree that it should not make a difference, but I have not been able to restore any content, documents or list items to any sites under a managed path. For all my web applications restore works on the root site collection but fails for all site collections under managed paths.

    M


    Matthew McDermott, MVP SharePoint

    Thursday, February 20, 2014 3:51 PM
  • Strange.... in my experience, the only issue when recovering whole site collections is that there must exist a site collection with that name previous to the restore (that is, DPM will not CREATE a non-existing site collection when restoring one, but MERGE its content with an existing one), and that both site collections (the one being restored, and the existing one) must have been created using the same site collection template.

    This latter condition "obliges" us to keep a thorough documentation on existing site collections, including its base site template. when we want to "restore from scratch" a site collection, we create an empty site collection based on the same site template and then restore it with DPM.

    HTH

    Roberto

    Friday, February 21, 2014 6:10 AM
  • Roberto,

    I am not recovering a site collection. I am attempting and failing to recover single items into a list or library.

    M


    Matthew McDermott, MVP SharePoint

    Friday, February 21, 2014 3:07 PM
  • Matthew,

    Again in my experience, the only way to debug this kind of problems is, unfortunately, push the verbose knob to the metal, and dig into the logs to find some hints... CmdletsWrapper*.log on the WFE side tend to be the most interesting when dealing with SharePoint restoration.

    At least I can assure you that indeed, it is possible to restore individual items... 

    Regards

    Monday, February 24, 2014 8:33 AM
  • OK, I'll give the logging a try.

    Thanks!


    Matthew McDermott, MVP SharePoint

    Monday, February 24, 2014 3:54 PM