Written by After migrating a couple of servers from an 2012 R2 Hyper-V cluster to an shiny 2016 cluster. Our Veeam failed to backup up some of them.
They got this error:
Failed to create VM recovery checkpoint (mode: Hyper-V child partition snapshot) Error code : 32768
or
I tried updating to latest Veeam 9.5 Update 2, but that didn’t do the trick.
After some research it turns out that the integrated services are not up to date.
They should be pushed with windows update, but there has been some KB that you need to uninstall before you can upgrade the integrated service.
You can verify the version on the following file “C:\Windows\System32\drivers\vmbus.sys”
Download the updates / cab files https://support.microsoft.com/en-us/help/3071740/hyper-v-integration-components-update-for-windows-virtual-machines-tha
For 2012R2 :
Check if these are installed, if so remove them and reboot before you continue KB3063109 and KB3071740.
After reboot install the update by running the following dism command:
Dism.exe /online /Add-package /packagepath:c:\temp\Windows6.2-HyperVIntegrationServices-x64.cab /quiet /norestart
After another reboot your vmbus.sys should be version 6.3.9600.17903
For 2008R2 :
If KB3063109 is installed remove it and reboot before you continue.
After reboot install the update by running the following dism command:
Dism.exe /online /Add-package /packagepath:D:\support\amd64\Windows6.x-HyperVIntegrationServices-x64.cab /quiet /norestart
After another reboot your vmbus.sys should be version 6.3.9600.17903
There’s a lot of misleading information about this issue on the internet but this blog is the solution, and an easy one at that.
On a 2012 R2 server I got this: Failed to finalize guest processing. Error: Failed to take in-guest VSS snapshot COM error: Code: 0x80042308
And 2008 R2 server: Failed to create VM recovery checkpoint (mode: Veeam application-aware processing) Details: Job failed (‘Checkpoint operation for ‘VM Name’ failed. (Virtual machine ID XXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX)’). Error code: ‘32768’.
I moved just over a dozen VMs from ESX to Hyper-V 2016 using Microsoft Virtual Machine Converter and I got this on two 2008 R2 servers and one 2012 R2. None of them had the faulty KB installed, but the Integration Services update worked and brought them all up to 6.3.9600.17903.