none
DPM 2019 - problem with Hyper-V VM recovery from Azure Cloud Backup. RRS feed

  • Question

  • Hello,

    We are evaluating Azure Cloud Backup with our DPM 2019 10.19.260.0.

    Our DPM server is on a physical Windows Server 2019.

    After I created the Vault and did the necessary on the DPM server, I created a protection group for a Hyper-V VM.

    The backup to cloud seems to be working ok as no error arised.

    Now, when I try to recover that VM, I can see this critical error at then end of Recovery from staging area:

    Affected area: RCT\testserver
    Occurred since: 01/05/2020 10:43:31
    Description: The recovery jobs for Microsoft Hyper-V RCT\testserver that started at 01 May 2020 10:22:26, with the destination of host.contoso.ch, have completed. Most or all jobs failed to recover the requested data. (ID 3111)
    An unexpected error occurred while the job was running. (ID 104 Details: Unknown error (0x80041024) (0x80041024))
    More information
    Recommended action: Retry the operation.
    On the Jobs tab in the Monitoring tasks area, group jobs by type to view details of the recovery jobs.
    Retry the recovery job...
    Resolution: DPM automatically changes this alert's status to inactive 10 days after it is issued.To dismiss the alert, click below
    Inactivate

    Now, if I tred to import the VM in Hyper-V with the downloaded data, it seems to be ok BUT the problems are:

    - Why does it raise a critical alert ? I can't validate the project for a production if critical alerts are there.
    - Even if that VM could be recovered, I can't trust something to be a 1:1 correct recovery if errors come with the recovery.

    Can someone help us with that please ? Thanks in advance.


    Friday, May 1, 2020 12:47 PM

Answers

  • Hi,

    How big (in GB) is the virtual machine that you recovered?

    How big is (in GB) is your staging area for the recoveries?

    I would suggest to check the DPM logs for any more clues why this error appears, you'll find the DPM log here:

    DPM server:

    • %ProgramFiles%\Microsoft System Center\DPM\DPM\Temp\MSDMCurr.errlog

    Please don't post the log file here, instead upload it to a Microsoft OneDrive / Google Drive and share the link, it would also help if you can tell during what time and date you performed the recovery so that there's no need to go through the whole log file.

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    • Marked as answer by dd-cges Monday, May 18, 2020 2:31 PM
    Thursday, May 7, 2020 8:55 AM
  • Hi,

    I forogot to come back here to say I found why this happened (but don't understand why it's doing that nor why Microsoft can't have an error code to help more).

    This was because the VM had mapped drive to an ISO file. If you remove that map, do the backup to cloud and test to recover the Hyper-V VM, it's working fine.

    Thanks to everyone who replied this post.

    • Marked as answer by dd-cges Monday, May 18, 2020 2:33 PM
    Monday, May 18, 2020 2:33 PM

All replies

  • Nobody can help me on that issue ?

    Help would be appreciate.

    Thursday, May 7, 2020 7:57 AM
  • Hi,

    How big (in GB) is the virtual machine that you recovered?

    How big is (in GB) is your staging area for the recoveries?

    I would suggest to check the DPM logs for any more clues why this error appears, you'll find the DPM log here:

    DPM server:

    • %ProgramFiles%\Microsoft System Center\DPM\DPM\Temp\MSDMCurr.errlog

    Please don't post the log file here, instead upload it to a Microsoft OneDrive / Google Drive and share the link, it would also help if you can tell during what time and date you performed the recovery so that there's no need to go through the whole log file.

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    • Marked as answer by dd-cges Monday, May 18, 2020 2:31 PM
    Thursday, May 7, 2020 8:55 AM
  • Hi,

    I forogot to come back here to say I found why this happened (but don't understand why it's doing that nor why Microsoft can't have an error code to help more).

    This was because the VM had mapped drive to an ISO file. If you remove that map, do the backup to cloud and test to recover the Hyper-V VM, it's working fine.

    Thanks to everyone who replied this post.

    • Marked as answer by dd-cges Monday, May 18, 2020 2:33 PM
    Monday, May 18, 2020 2:33 PM