Hyper-V 2019 VM hosting SQL Server 2019 - Production checkpoints cannot be created

Question

I'm trying to run a Veeam backup for our Hyper-V virtual Windows Server 2019 server which hosts SQL Server 2019. I'm unable to get fully consistent backups because it always fails to create a VM recovery checkpoint.

When running a production-only checkpoint in Hyper-V manager for the same VM, I get the error message "Checkpoint operation failed. Production checkpoints cannot be created."

This is the only server that I get this error for, but it is the only one we have that is running SQL Server 2019. I've researched numerous articles and tried a number of different things, including, but not limited to:

• checking permissions and even adding permissions - there is nothing different about permissions for this one VM than any of my other VMs;
• verifying that I have plenty of disk space for the folder where the snapshots are located;
• verified that the status of the VSS services on the the SQL server are in line with what they are supposed to be (vssadmin list providers);
• fully patched and restarted each of the 2 Hyper-V hosts in the cluster;
• fully patched and restarted the target virtual machine;
• checked the Hyper-V host's Hyper-V-VMMS Admin event log - there is no more error information other than "Checkpoint operation failed" and "Production checkpoints cannot be created".

If I shut down the virtual machine, the production only checkpoint succeeds. It is while the server is in a running state that the production-only checkpoint fails.

Any insight into the source of this issue and a solution for it would be greatly appreciated.

Answer 1

Hi Rochelle,

Hope you're doing well.

This error can occur due to a variety of reasons, including insufficient disk space, insufficient memory, or incompatible hardware.

1. One possible solution to this issue is to change the checkpoint type from production to standard checkpoints.

2. If the issue persists, you may want to check if the virtual machine has enough disk space and memory available.
3. To find the root cause of this issue, we suggest you go to the Microsoft Customer Service Center to open a Premier-level case so that with their permission level and resource, Microsoft could provide you with better help on your request.

I hope this helps.

Best Regards

Answer 2

Hi,

I have the same problem, have you managed to resolve this problem ? 

Good day