Active-Active Not Supported for Shared VHDX in VM Group Another somewhat common error message is "Active-active not supported for shared VHDX in VM Group." This error is sometimes displayed with. Veeam B&R 9.5/10 Error message 32768 - Windows server 2019 HyperV All integration services (including backup) are enabled for VM. Then click on Guest Processing on the left section, and then click on the Test Now button to start checking the credentials that you set for this job. KB1857: Unable to allocate processing resources - Veeam Software Veeam Free Backup and Replication Script Error 32774 To resolve the problem is necessary reinstall the component LocalDB, as showed in figure 1. It seems that our production server hasn't any checkpoint. 1) System information from the affected server. Understood. Now we can take the checkpoint of the VM. The same operation fails when trying to take a Snapshot via vSphere client with the option "Snapshot the virtual machine's memory" unchecked and the "Quiesce guest file system (Needs VMware Tools installed)" option enabled. That might be quickest way to get this resolved :) Thanks guys! To access the utility, right click any volume and choose Configure Shadow Copies. Correct, with the "Take crash-consistent backup instead of suspending VM" option the application running inside will not be prepared for backup and that might cause issues with restores, so you may want to leave this setting unchecked. Briefly, I recommend the following steps to solve these kind of problems. Running the "vssadmin list writers" command might also show the SqlServerWriter in a "Non-retryable error" state. The checkpoints under the Hyper-V manager are stuck at 9%. Reasons for this include: Too many jobs are running at a time for the number of concurrent tasks set across all proxies available to the job that failed. Troubleshooting Veeam B&R Error code: '32768'. Failed to create VM ... 2) Logs with information about VM checkpoints operations and failures related to Hyper-V VMs snapshots/checkpoint creation failure. Find the checkpoint location of the problematic VM in Hyper-V Manager by right clicking on VM -> settings -> checkpoint and check whether the drive has enough free space .