OPERATIONAL DEFECT DATABASE
...
...
BugZero found this defect 1653 days ago.
This article documents how to force Hyper-V 2016 or newer to create a Production Checkpoint.
Forcing Hyper-V to create a Checkpoint in ProductionOnly mode is used as an isolation step when troubleshooting a Veeam job that fails to create a Recovery Checkpoint with Application-Aware Processing or Hyper-V guest quiescence enabled.
It is imperative that all steps be followed precisely to ensure the test results are valid.
The following troubleshooting steps are provided as a courtesy. Veeam Support recommends that you contact Microsoft Support for assistance if the Hyper-V environment cannot create a Production Checkpoint in ProductionOnly mode. If the Production Checkpoint process immediately fails with "Production checkpoints cannot be created.", check the following: Ensure that services within the Guest OS of the VM in question are configured correctly: Volume Shadow Copy is set to Manual startup type. Hyper-V Volume Shadow Copy Requestor service is set to Manual startup type. Hyper-V Volume Shadow Copy Requestor service is Running. Check the Integration state on the Hyper-V host where the VM is located: Check the VSS Integration status using the following PowerShell command:
