VSS errors Windows Server Backup of Hyper-V RRS feed

  • Question

  • Hi,

    we have a fully patched Windows Server 2012 R2 Hyper-V host running 4 VMs, also fully patched Windows Server 2012 R2.

    Originally we had 2 VMs on the host and configured Windows Server Backup for the server and it has been working just fine.

    However now when we have set up two more VMs the backup fails for the newly added VMs with the error message "The writer experienced a non-transient error".

    On the VM the VSS Writer logs error 12293.

    Here's the strange thing:
    When running Windows Server backup from inside the VM the backup succeeds.

    Also when running a third party tool (Ahsay backup) from the host the backup succeeds, (This is also VSS based...?)

    Any ideas what might be causing this?

    Friday, March 3, 2017 8:19 AM

All replies

  • Ok, some more research on my own:

    I just made is that integration services versions differ!

    The failing VMs are fully patched together with the Host. The successfull VMs were not fully patched!

    The failing VMs have Hyper-V Integration Services 6.3.9600.18398 while the successfulls runs earlier version 6.3.9600.16384...

    So I did I some research on Integration services and found this article: https://social.technet.microsoft.com/wiki/contents/articles/33796.hyper-v-integration-services-list-of-build-numbers.aspx

    So, I ended up uninstalling https://support.microsoft.com/en-us/kb/3172614 from the host.
    This did not revert the affected VMs, however when setting up a new VM it had 6.3.9600.16384 (that's the Windows 2012 R2 RTM version)

    I tested backupfor the newly created host, and "WOW!" it works like a charm! :)

    So my conclusion here is that the latest version of Hyper-V intagration services is not working in my enviroment.

    The remaining qustions are if it's possible to downgrade on the guest side for the failing VMs...?
    Uninstalling the patch above from the guest does not downgrade Version.
    Neither does "Setup /uninstall" that only says that theres a newer version installed....

    Any ideas?

    • Edited by PeterSWE Friday, March 3, 2017 6:32 PM
    Friday, March 3, 2017 6:31 PM
  • have you looked at re-registering the VSS writers? it sounds like the 3rd party backup products have their own writers, and it's the native Wndows writers are screwed.

    check for errors

    vssadmin list writers

    re-register the hyper-v writers


    • Proposed as answer by Leo Han Thursday, March 16, 2017 7:15 AM
    Friday, March 3, 2017 9:11 PM

  • Hi,
    Are there any updates on the issue?
    You could mark the reply as answer if it is helpful.
    Best Regards,

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, March 16, 2017 7:15 AM