none
Can't restore Entire VM from backup RRS feed

  • Question

  • Hi,

    I tried restoring two different jobs and they fail with the following error:

    The VSS application writer or the VSS provider is in a bad state. Either it was already in a bad state or it entered a bad state during the current operation. (ID 30111 Details: VssError:The writer experienced a non-transient error.  If the backup process is retried,
    the error is likely to reoccur.
     (0x800423F4))

    I checked the vm before it was backed up and after it was restored (recreateing a new vm using vhdx) and there are no errors in any of the vss writes.

    Any help?

    DPM 2019 with latest update running on Server 2019 Standard.

    Thanks,

    Jerry


    • Edited by SilentCow Tuesday, April 14, 2020 2:40 PM unknown.
    Tuesday, April 14, 2020 2:40 PM

All replies

  • More details. I'm trying to recover to a different Hyper-V Host. No Clusters.

    Other pages I came across said it happened because it exceeded 260 characters. That's not happening here.

    Also tried checking and unchecking Backup (volume snapshot ) checkbox in Integration settings.

    • Edited by SilentCow Thursday, April 16, 2020 8:42 PM
    Thursday, April 16, 2020 8:41 PM
  • Hi,

    Could you provide some more information about your Hyper-V environment?

    • What is the operating system version of both source and destination Hyper-V hosts?
    • What is the Hyper-V virtual machine configuration version?
    • How is the Hyper-V storage configured?
    • Are the Hyper-V hosts fully patched and up-to-date?

    Also check the DPM log for more clues:

    DPM server

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

    Hyper-V server

    • %ProgramFiles%\Microsoft Data Protection Manager\DPM\Temp\DPMRACurr.errlog

    You can upload the logs to Microsoft OneDrive / Google Drive and share the link here.

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Friday, April 17, 2020 12:08 AM
  • Thanks Leon. I will check the logs and let you know what I find.

    Hi,

    Could you provide some more information about your Hyper-V environment?

    • What is the operating system version of both source and destination Hyper-V hosts?

    Source Host is Server 2016 Standard. Destination Host has been attempted on Server 2016 Standard and 2019 Standard.

    • What is the Hyper-V virtual machine configuration version?

    9.0

    • How is the Hyper-V storage configured?

    Each Host has its own Storage from SAN.

    • Are the Hyper-V hosts fully patched and up-to-date?

    Yes

    Also check the DPM log for more clues:

    DPM server

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

    Hyper-V server

    • %ProgramFiles%\Microsoft Data Protection Manager\DPM\Temp\DPMRACurr.errlog

    You can upload the logs to Microsoft OneDrive / Google Drive and share the link here.

    Best regards,
    Leon

    Friday, April 17, 2020 4:49 AM
  • Hi Leon,

    I have uploaded the logs:

    https://send.firefox.com/download/2834d636997b75e1/#Lc3VJ8Gvuq1qch2GTrBYKQ

    One thing I noticed right off the bat. The time in the logs don't match the time on the servers.

    IE I ran the test at 11am and the logs show I ran it at 17:00

    Thanks for taking the time to look at the logs.

    Friday, April 17, 2020 6:09 PM