none
On-Premise DPM2016 Online File Recovery error ID 220010 RRS feed

  • Question

  • Hi All

    On Premise DPM 2016 RU5 backing up to disk and long term online into Azure.

    Azure Backup Agent version: 2.0.9145.0

    Online Status: Active

    Online Recovery Points taking place one a week and no errors reported. I can see Online Recovery Points available in the Recovery Tab in DPM Console.

    Error Description: I have tried to recovery files from random from our online recovery points, however each time I try recovering a file from Azure i receive an error ID 220010 with no description. 
    I have tried to search around online for this error ID but nothing seems to correspond to DPM.

    This is a concern that our long-term backup integrity is unavailable or even corrupt.

    I've tried recovering other files from different dates in the recovery calendar from azure and each one errors with the same ID 220010.
    The files I have tried to recover are .jpg and .CR2.
    Also tried recovering to original location using that locations permissions and also to an alternate location.

    Can anyone shed light on ID 220010?

    Thanks

    Tuesday, November 20, 2018 5:22 PM

All replies

  • Hello!

    This error is unfamiliar to me, could you provide us with any DPM related errors in the Application log of the DPM server and also the MSDPMCurr.errlog log?
    (Found under C:\Program Files\Microsoft System Center\DPM\DPM\Temp)

    Also check the DPMRACurr.log on the protected server.

    There also exist a newer Update Rollup, you could also try to see whether it fixes the issue.

    Update Rollup 6 for System Center 2016 Data Protection Manager

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, November 22, 2018 8:45 AM
  • Please check log files like Leon said. 

    What you can also try is to create a disaster recovery test. For this you will need to dedicated domain environment with one domain controller and Azure Backup Server which you can download from your Azure Portal. Once all deployed you have an option to "Add External DPM" which will allow you to restore your files from your Recovery Service vault. This way you will create a test for disaster recovery (when everything is gone) and you will also know if your issues are related to your Recovery Service Vault or DPM itself. 

    https://docs.microsoft.com/en-us/azure/backup/backup-azure-alternate-dpm-server


    Microsoft Certified Professional

    [If a post helps to resolve your issue, please click the "Mark as Answer" of that post or click Answered"Vote as helpful" button of that post. By marking a post as Answered or Helpful, you help others find the answer faster. ]


    Thursday, November 22, 2018 2:31 PM
  • Interestingly I've tried a couple of other different file restorations from the same Azure Recovery point had they restored successfully!

    The only errors or warnings I've seen in the logs are: 

    0A4C 33A8 11/21 22:30:10.001 16 Task.cs(235) NORMAL Changing task state from 'Retire' -> 'Succeeded' (1cd8f7d5-fbd8-4c30-9e2b-cd8eeaf96a83)
    0A4C 1B94 11/21 22:30:10.004 11 VhdMountManager.cs(543) WARNING Error while mounting: Microsoft.Internal.EnterpriseStorage.Dls.Wmi.NonFatalWmiException: Query returned zero objects: SELECT * FROM MSFT_Volume WHERE Path='\\\\?\\Volume{0b743ab9-454a-4383-9c2e-20459504f024}\\'
    0A4C 1B94 11/21 22:30:10.004 11 VhdMountManager.cs(543) WARNING    at Microsoft.Internal.EnterpriseStorage.Dls.Wmi.ResilientWmiCommand.GetObject(ManagementScope managementScope, String wqlQuery, Boolean throwIfSingleObjectNotFound)
    0A4C 1B94 11/21 22:30:10.004 11 VhdMountManager.cs(543) WARNING    at Microsoft.Internal.EnterpriseStorage.Dls.StorageManager.VhdMountManager.MountVolumes(List`1 mountVolumeRequests)
    0A4C 1B94 11/21 22:30:10.004 11 VhdMountManager.cs(543) WARNING *** Mojito error was: WMIFailedToExecuteQuery; 0; None
    0A4C 33A8 11/21 22:30:10.021 16 ActiveJob.cs(1224) NORMAL Final task state=Retire(6375e3e3-012e-4635-aa14-c6e94784d502)

    I'll continue to look into this and will take a look at the DPMRACurr.log on the protected server

    Thanks

    Thursday, November 22, 2018 5:17 PM
  • The recovery jobs for Volume E:\ that started at 20 November 2018 16:46:15, with the destination of SERVER.DOMAIN , have completed. Most or all jobs failed to recover the requested data. (ID 3111)

    Thursday, November 22, 2018 5:43 PM
  • So if I understand correctly you are able to restore few files from Azure but not all? 

    What is the overall performance of your DPM server? Do you have enough CPU, memory etc.?


    Microsoft Certified Professional

    [If a post helps to resolve your issue, please click the "Mark as Answer" of that post or click Answered "Vote as helpful" button of that post. By marking a post as Answered or Helpful, you help others find the answer faster. ]

    Friday, November 23, 2018 6:40 AM