Update 2018 #2: Yet another bug in Hyper-V on Windows Server 2016 has surfaced. Even after removing my backup software I still cannot create a production checkpoint, I get the same error, on the host that works just fine, I never did the production checkpoint / subtree delete. Virtual machines in a cluster with CSV storage - Back up virtual machines hosted on a Hyper-V cluster with Cluster Shared Volume (CSV) storage. Production Checkpoints in Windows Server 2016Working Hard In IT (Virtual machine ID 42241DBC-8270-4E07-850C-462B164E4113) Cannot take checkpoint for 'Guest1-2016' because one or more shareable VHDX are attached and this is not part of a checkpoint collection. Proxies may be unavailable (Shutdown, not connected to the network, etc. (Virtual machine ID xxxxxxxx)'). Failed to create VM recovery checkpoint - Veeam R&D Forums failed to create vm recovery checkpoint - hardy-flap.se For production checkpoints, the Volume Snapshot Service (VSS) is used inside Windows virtual machines, whereas Linux virtual machines flush their file system buffers to create a file system consistent checkpoint. The production checkpoint uses a backup technology inside the guest to create the checkpoint. Added vhd sets on SQL1 and SQL2 Trying to create production checkpoints but ending up with the below error Cannot take checkpoint for 'DB1-LIVE' because one or more shareable VHDX are attached and this is not part of a checkpoint collection. If you want to create checkpoints using saved state technology you can still choose to use standard checkpoints for your virtual machine. Cause. but when I try to start the vm I am getting this message. I cannot create a production checkpoint for the Windows 7 VM from the Hyper-V console ( I unchecked the box that gives an option to create standard checkpoint when it is not possible to create production checkpoint). In such cases, the backup continues as a crash consistent backup, completes with errors, and displays the JPR "Production checkpoint failed for the VM." And the checkpoint creation failed. However, customers with these types of issue should also review the Hyper-V-VMMS . cannot take checkpoint for "New Virtual Machine" because one or more pass-through disk are attached. Cannot create using PowerShell and get the same error: One addition thing I have noticed is that when looking at where the VHDX is stored there is also a AVHDX file even though there are no checkpoints showing. Standard or Production checkpoints in Hyper-V - How to choose Cannot create using PowerShell and get the same error: One addition thing I have noticed is that when looking at where the VHDX is stored there is also a AVHDX file even though there are no checkpoints showing. Is it because the guest is a Windows 7 ? checkpoint operation failed. production checkpoints cannot be created. icacls D:\VMs /grant "NT VIRTUAL MACHINE\Virtual Machines":F /T Second, the issue may be down to a permissions misconfiguration. Under the Management section, select Checkpoints. Then, we select the Virtual Machine setting.

Esther Susan Melling, University Of Chicago Persian Gallery, Articles P