none
Microsoft Windows Server 2012 R2 - Hyper-V VM Backup using System Center's DPM 2016 RRS feed

  • Question

  • All,

    We are trying to backup our VM's on our hosts using DPM 2016.

    When we attempt to do so, the backup fails and upon research found the following error on VSS Writers:

    Writer name: 'Microsoft Hyper-V VSS Writer'
       Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
       Writer Instance Id: {946060dd-70fa-4626-9048-0da3b92fd2f9}
       State: [8] Failed
       Last error: Retryable error

    We have contacted our Hardware support for our HP Servers and they have directed us to Microsoft Support.

    Has anyone had any experience of this before?

    Thanks,

    Chris


    • Edited by Chris Hues Monday, February 12, 2018 2:38 PM
    Monday, February 12, 2018 2:37 PM

All replies

  • Hi,

    Have you tried a Reboot of the Host?


    Michael Seidl (MVP)

    SYSCTR Senior Consultant, Blogger, CEO

    Blog | Twitter | Facebook | LinkedIn | Xing | <gs class="GINGER_SOFTWARE_mark" ginger_software_uiphraseguid="b20c25e1-ebdb-4cb1-a897-4ff1194322b3" id="333df8bc-cb59-4815-8367-e43852c47131">Youtube</gs>

    Note: Posts are provided "AS IS" without warranty of any kind, either expressed or implied, including but not limited <gs class="GINGER_SOFTWARE_mark" ginger_software_uiphraseguid="5fcf26ba-4413-4e1b-82cc-926df9aab4d3" id="1169328e-a7f9-424a-ab08-d2a077ba252f">to the</gs> implied warranties of merchantability and/or fitness for a particular purpose.


    Tuesday, February 13, 2018 6:31 AM
  • When this happens, which is rare these days, a reboot of the hyper-v host usually fixes it.
    Wednesday, February 14, 2018 10:16 AM
  • Hi Michael,

    We have rebooted the host on several occasions as that's a regular part of our Windows Updates process.

    This, along with restarting the Hyper-V Virtual Machine Management service, fixes the issue for a short time (maybe 1 or 2 days) and then goes back to the error above.

    Thanks,

    Chris 


    • Edited by Chris Hues Wednesday, February 21, 2018 5:51 PM
    Wednesday, February 21, 2018 5:50 PM
  • Question
    You cannot vote on your own post
    0

    Hi Christian,

    We have rebooted the host on several occasions as that's a regular part of our Windows Updates process.

    This, along with restarting the Hyper-V Virtual Machine Management service, fixes the issue for a short time (maybe 1 or 2 days) and then goes back to the error above.

    Thanks,

    Chris 

    Wednesday, February 21, 2018 5:50 PM