9.5 Hyper-V 2016 Known Issues

[rogerdu]

Annnnddd... Dynamic Disks... its all I'm gonna say. They're not supported for Production Snapshots...

One fixed, the customer wants to leave the other, so no Application Aware backups for you!

[mb1811]

Veeam Case # 03676525

This case ist related to Server 2019 but it hits since Server 2016.

I call it the 9% Issue:
While perfoming a Snapshot via ANY backup tool, VM's get stuck in a state: "Creating Snapshot 9%"

https://social.technet.microsoft.com/Fo ... rum=ws2016

microsoft-hyper-v-f25/failed-to-create- ... 98-30.html

Hardly shutdown the VM's and reboot the Hyper-V host...

[MDS_UK]

Re the "9% issue" - see below also
https://social.technet.microsoft.com/Fo ... f=required

[ChristineAlexa]

Another fix I didn't see in here, and will add to the list to help save someone else a few hours of hunting

- Symptom - Errors Similar to the below, where %1 is the VM name and %2 is the Virtual Machine ID)

'Checkpoint operation for %1 failed. (Virtual machine %2) Checkpoint operation for '%1' was cancelled. (Virtual machine ID %2) '%1' could not initiate a checkpoint operation: Element not found. (0x80070490). Error code: '32789'. Failed


If you have MPIO enabled on the VM,
- ensure you didn't accidently check "Add Support for SAS Devices".
- You may see errors in event log for volumes that don't exist not mounting.

To uncheck that box (since you can't in the interface), (You most likely will need to reboot afterwards, even if not prompted)
- Open a Powershell session in the VM
- Type the following command: Disable-MSDSMAutomaticClaim -BusType SAS

Once you have reboooted, follow the normal settings for Production Checkpoints, and it should work finally.

[Quibus]

Does anyone know a smooth script that can merge snapshots together after an incident like this?
I have a VM that has 213 .avhdx files ... sigh...

[nmdange]

I had to modify the script to do what I needed, but this should be a good starting point
https://gallery.technet.microsoft.com/s ... e-72a96c17

[Quibus]

Thank you nmdange!
This was what is was looking for

[bcrusa]

I would like to share my experience that I had solved the issue with updating NIC drivers.

[fsr]

So, still no patch from Microsoft for the "Checkpoint operation failed" issue? The only option continues to be restarting the two services every time the VM starts?

[Wilian]

Hi All,

Does anyone know how to fix that?
I`m facing exactly the same problem with Windows Server 2016?

[Vitaliy S.]

Wilian, that's a pretty long thread with all sorts of issues, so can you please clarify what problem do you have? Thanks!

[davidkillingsworth]

I just want to add that I fixed this issue with a brand new setup with Hyper-V 2019 and Veeam 10.

New Dell PowerEdge Server stand alone server.
New Windows Server 2019 Hyper-V host stand alone server.
3 New Windows Server 2019 VM guests
1 New Ubuntu 20.04 Server VM guest
Veeam Backup & Replication 10.0 Community Edition.

The issue I was having was that the backup and checkpoint would get to 7% or 50% and freeze. The backup job froze, then VM guests froze. I was not able to gracefully shut down the VM guests. When I tried to reboot the Hyper-V host, it froze.

I had to use the Dell iDrac card to physically restart the Hyper-V host.

After changing the checkpoint type to Standard in the VM's settings, then rebooted all VM guests and VM host, I ran the backup again and the checkpoint succeeded in a few seconds and the backup ran without any problems.

[sunnyIT20]

Having this issue myself. One guest alone has 335 avhdx files sized 5g-20gb for a total of 2.5tb, just made aware as storage low alerts triggered. Have a couple other guests with same issue on a 2nd hyper v host. Backups have run successfully without error for last 3 years. No errors creating new checkpoints in hyperv mgr. Hosts and guest are all server2021R2, have all KBs mentioned in these posts. Veeam 9.5u4. Have not tried and would like to avoid manual merge process. Any advice or recent updates to this issue? Any reason why it wouldnt be easier to just create a replica than use that and delete old avhdx?

If not my attempts will consist of these two links mentioned here prior:
https://docs.microsoft.com/en-us/troubl ... -vms-fails
https://www.altaro.com/hyper-v/clean-up ... heckpoint/
https://gallery.technet.microsoft.com/s ... e-72a96c17

[wishr]

Hi Sunny,

Welcome to the forums!

What particular issue out of those discussed in this thread are you referring to?

Thanks

[LarsBorris]

Another fix I didn't see in here, and will add to the list to help save someone else a few hours of hunting

- Symptom - Errors Similar to the below, where %1 is the VM name and %2 is the Virtual Machine ID)

'Checkpoint operation for %1 failed. (Virtual machine %2) Checkpoint operation for '%1' was cancelled. (Virtual machine ID %2) '%1' could not initiate a checkpoint operation: Element not found. (0x80070490). Error code: '32789'. Failed


If you have MPIO enabled on the VM,
- ensure you didn't accidently check "Add Support for SAS Devices".
- You may see errors in event log for volumes that don't exist not mounting.

To uncheck that box (since you can't in the interface), (You most likely will need to reboot afterwards, even if not prompted)
- Open a Powershell session in the VM
- Type the following command: Disable-MSDSMAutomaticClaim -BusType SAS

Once you have reboooted, follow the normal settings for Production Checkpoints, and it should work finally.

Thank you SO much! This was exactly my issue.
You saved my day. Have a great one. Cheers.