Host Machine:
Virtual Machine:
I'm having some problems to create checkpoints on my VM. When i try to do it, Hyper-V goes until 19% of the creating progress, and then this error screen appears:
I've analyzed Event Viewer's logs, and on the Hyper-V Worker > Admin section, it shows the following messages:
'PNSP2013' could not initiate a checkpoint operation: %%2147754996 (0x800423F4). (Virtual machine ID 69EAA8C6-E8E9-4585-97AE-5633F400BB89)[
And I also collected VSSDiag's log, which contains no relevant information (at least for me)
A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error. If the backup process is retried, the error is likely to reoccur. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer. Log:
Operation: PostSnapshot Event Context: Execution Context: Writer Writer Class Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757} Writer Name: NTDS Writer Instance ID: {2b09511a-25fd-47cd-929f-4f1f60cc1594} Command Line: C:\Windows\system32\lsass.exe Process ID: 636NTDS
Some important points to consider:
I can't figure out what the hell is going on... Some help?
This is a known issue for pre-2016 DCs running in VMs on 2016/Win10 Hypervisors.
The problem is the new Production Checkpoint architecture. If you change the Checkpoint type to Standard in the VM's settings, the Checkpoint will succeed.
I just want to add that I fixed this issue with a brand new setup with Hyper-V 2019 and Veeam 10.
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.
After changing the checkpoint type to Standard in the VM's settings in Hyper-V manager, 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.
User contributions licensed under CC BY-SA 3.0