Skip to main content

Backup fails on a single Hyper-V instance

Thread needs solution

Build 11.5.37975 - server Windows 2012R2 Std.

On one single hyper-v client, the backup consistently fails with the error below (name of machine changed). All other instances backup just fine.

ProtectCommand: Failed to execute the command.
Additional info:
--------------------
Error code: 41
Module: 307
LineInfo: e6792a5ee190dda6
Fields: $module : agent_protection_addon_vs_37975
Message: ProtectCommand: Failed to execute the command.
--------------------
Error code: 32834
Module: 114
LineInfo: c35c04057128fda9
Fields: $module : disk_bundle_vs_37975
Message: Backup of virtual machines has failed.
--------------------
Error code: 32853
Module: 114
LineInfo: c35c04057128fdeb
Fields: $module : disk_bundle_vs_37975
Message: Not all virtual machines have been backed up.
--------------------
Error code: 32852
Module: 114
LineInfo: c35c04057128fe3d
Fields: $module : disk_bundle_vs_37975
Message: Failed to back up virtual machine '185-christian'.
--------------------
Error code: 32786
Module: 114
LineInfo: 28314c961de7d2c2
Fields: $module : disk_bundle_vs_37975
Message: Failed to prepare for backing up.
--------------------
Error code: 3
Module: 329
LineInfo: 1cd98aae889424f9
Fields: $module : disk_bundle_vs_37975
Message: Backup has failed.
--------------------
Error code: 1060
Module: 1
LineInfo: d1ab7fa1e56ec6ca
Fields: $module : disk_bundle_vs_37975
Message:
--------------------
Error code: 13
Module: 149
LineInfo: d1ab7fa1e56ec81c
Fields: $module : disk_bundle_vs_37975
Message: Failed to perform the requested operation.
--------------------
Error code: 236
Module: 16
LineInfo: 7bb42efe3c733241
Fields: $module : disk_bundle_vs_37975
Message: Internal error: Attempt to access emulated disk for non-initialized object.
--------------------
Error code: 94
Module: 83
LineInfo: 383ffdb092990e22
Fields: $module : hv_srv_vs_37975
Message: Failed to open virtual disk file 'D:\HyperVdisks\14-Christian.vhd'.
--------------------
Error code: 212
Module: 83
LineInfo: 383ffdb092990dd9
Fields: $module : hv_srv_vs_37975
Message: Failed to create a multi-volume snapshot where files are located:
C: \HyperV\Machines (virtual machine file location),
D: \HyperVdisks\ (virtual machine snapshot file location),
D: \HyperVdisks\14-Christian.vhd (virtual disk file location).
--------------------
Error code: 207
Module: 83
LineInfo: 383ffdb092990dca
Fields: $module : hv_srv_vs_37975
Message: Failed to mount the volume snapshot.
--------------------
Error code: 33
Module: 7
LineInfo: e24f93d0b8d8c9c7
Fields: $module : hv_srv_vs_37975
Message: Failed to create volume snapshot.
--------------------
Error code: 50242
Module: 16
LineInfo: 14181c22ef45b0f6
Fields: $module : hv_srv_vs_37975
Message: Failed to start creating the volume snapshot.
--------------------
Error code: 50281
Module: 16
LineInfo: 14181c22ef45a9e9
Fields: $module : hv_srv_vs_37975
Message: VSS writer 'Microsoft Hyper-V VSS Writer' with class ID '66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE' has failed to process the snapshot.
--------------------
Error code: 65520
Module: 0
LineInfo: bd28fdbd64edb8ea
Fields: code : 2147754996, $module : hv_srv_vs_37975
Message: Unknown Win32 error
--------------------

0 Users found this helpful

Followup:

Latest update from MS (KB2883200) have fixed the problem.

There must have been a problem with VSS which MS fixed, as everything works now whether VSS is on or off. Before it gave the error above when VSS was on, but only for that single Hyper-V instance.