Forum Discussion
Hyper-V guest Backup in VSS
Hi Puntos,
You can check it in the Hyper-V manager, go to the settings of the VM and go to Management - Checkpoints. Check also under Management the Integration Services, is the option Backup (volume shadow copy) checked? If this is checked (the default) then the VM is using VSS to create a checkpoint. If you want a "freeze" of the VM (paused state) then you must uncheck it. But personally, I think it’s better to use the VSS option.
Regard,
Erwin
Hi Erwin,
Thx for the quick reply ;). The option "backup" under vss is checked.. read about a bug that it could be unchecked and checked again for it to take. (tried that) It freeze the machine so I dont think it useses the Backupoption even if its checked. Thx for the guidance.
- ErwinvanDijkMay 30, 2017Brass Contributor
Hi Puntos,
Did you restart the Hyper-V Volume Shadow Copy Requestor (vmicvss) after the turn off/on off Backup?
You can check the Application eventlog for the Task Category ShadowCopy events 2001, 2003 and 2006, or maybe you see errors there?
A test to be sure if VSS is the one who stops your backup from working is the following:
- Stop the Hyper-V Volume Shadow Copy Requestor (vmicvss) service on the VM
- Create a backup
Be aware that this procedure will pause your VM during the backup! So don’t do this in production time!
Hope this helps you further, if VSS is working I would suggest to consult with your backup vendor again.
Regard,
Erwin
- Pontus AnkarbågeMay 30, 2017Copper Contributor
Hi there again,
The backup still freeze when i shut down the vmicvss.. In the log of the vmhost where the guest is. I got following error (4000) Failed to connect to virtual machine 'bkbupdmz01' because there is no mutually supported protocol for VM: (Virtual machine ID 223A61EB-75E9-4494-AE75-36978840CC40). Framework version: Negotiated (0.0) - Expected (3.0); Message version: Negotiated (0.0) - Expected (4.0)."
Is there anything that need to be open on the network for this to be working?
Regards Pontus Ankarbåge
- ErwinvanDijkMay 31, 2017Brass Contributor
Hi Pontus,
Looks like a problem with the Integration tools, is the VM using the latest updates?
Don't no how to reinstall them using Server 2016, this is changed from the Server 2012 R2 procedure.
Regards,
Erwin