Unsolved
This post is more than 5 years old
5 Posts
0
1165
Hyper-V Backups and VSS Errors
Hello forums! This is my first post here, I wanted to check here before I open either a MS case or Networker case.
I am trying to backup Hyper-V VMs using Networker, and I followed the integration guide to a T. My version is 9.2.1, and HyperV is running on Server 2016. When I kick off a backup, I can see the checkpoint being created in HyperV manager, however the job subsequently fails and I get a VSS error in the Event log of the HyperV host machine. Link to the Networker server logs:
Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {89300202-3cec-4981-9171-19f59559e0f2}. Routine details PostCommitSnapshots({6ee1a43b-a821-49ef-aefa-a58e7228d44e}, 1) [hr = 0xffffffff].
Operation:
Executing Asynchronous Operation
Context:
Current State: DoSnapshotSet
Prior to the first backup run, vssadmin list writers shows the Hyper-V writer having no error / ready. After the backup runs and fails, the Hyper-V writer is in a Failed state, showing a timed out error:
Writer name: 'Microsoft Hyper-V VSS Writer'
Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
Writer Instance Id: {9df1e599-3ba8-4a3f-bfc6-2c6a03fc609c}
State: [9] Failed
Last error: Timed out
ble1
2 Intern
2 Intern
•
14.3K Posts
0
August 23rd, 2018 07:00
This sounds like an issue with writer itself so I would suggest MS case. Having both might be good idea and MS likes to push back when not using their software so there might be some ping-ping before someone really takes a closer look at what is going on.
ttobey
32 Posts
0
August 28th, 2018 10:00
With hyper-v vss writer failed have you checked the hyper-v-vmms\admin event log?
That will show the VM(s) that is causing an issue. Then you can trouble shoot each VM that has an issue.