The error -32770 occurs during checkpoint creation in BDRShield due to various reasons, including:1. Checkpoint creation failure for Appaware enabled backups when the VM is in a "Saved" or "Paused" state.2. Insufficient storage space in the checkpoint location for the configured VM, causing the failure of creating child disks (avhd/avhdx).3. The virtual hard disk (VHD/VHDX) of the virtual machine being on a compressed or encrypted drive, which is not supported.4. Manual production checkpoint creation failure for Appaware enabled backups with writer status check enabled.
Solution 1: Change VM StateChange the state of the VM(s) to running or off if they are in a "Saved" or "Paused" state using Hyper-V Manager or Failover Cluster Manager.Solution 2: Checkpoint Location SpaceCheck the checkpoint location of the problematic VM in Hyper-V Manager. Right-click on the VM, go to settings, then checkpoint, and ensure sufficient free space is available.Solution 3: Drive Propertiesa) Disable drive compression: Right-click on the drive where the backed-up VM's virtual hard disks (VHD/VHDX) are located. Go to Properties -> General tab and disable "Compress this drive to save disk space." Reschedule the backup.b) Decrypt the drive: If encryption is enabled, disable it. After disabling encryption or compression, ensure the VM is accessible in Hyper-V Manager and reschedule the backup.Solution 4: Change Checkpoint Type1. Attempt to create a Production checkpoint for the problematic VM.2. In Hyper-V Manager, right-click on the VM, go to Settings -> Checkpoints.3. Change checkpoint type to Production checkpoints (uncheck "Create standard checkpoint if the guest does not support production") and apply.4. Ensure "Production-only" text is displayed in the left panel under checkpoints.5. Right-click on the VM in Hyper-V Manager, click on checkpoints, and verify checkpoint creation success. Resolve any Windows errors and verify with steps before rescheduling the backup.Solution 5: Enable Backup Service and Restart VSS RequestorEnable Backup service from Hyper-V Integration Service and restart VSS Requestor (vmicvss) in the Guest machine.