Troubleshooting Error -32770 When Creating Checkpoint in BDRSuite
The error -32770 occurs during checkpoint creation in BDRSuite 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 State
Change 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 Space
Check 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 Properties
a) 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 Type
1. 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 Requestor
Enable Backup service from Hyper-V Integration Service and restart VSS Requestor (vmicvss) in the Guest machine.
Related Articles
Troubleshooting Checkpoint Creation Errors in KVM Environment
KB ID: 221004 Cause: The KB article focuses on problems that occur specifically within the KVM hypervisor environment during the creation of a checkpoint for a virtual machine. These errors can disrupt normal operations and may signify underlying ...
Troubleshooting Guide: BDRSuite Backup Failed - Internal File System Error
KB ID: 102180 Issue: Backup operations have failed due to an internal file system error within BDRSuite. This error occurs when a specific backup job in BDRSuite possesses a negative chunk file ID value, resulting in job failure. Cause: The failure ...
Troubleshooting: Invalid Guest Credentials Error in BDRSuite
KB ID: 115073 Cause: When running a VM backup or replication job with app-aware options enabled, you may encounter the "Failed::Invalid guest credentials" error. This error occurs when the guest credentials provided for the guest machine are ...
Troubleshooting AppAware Runtime Errors in BDRSuite
KB ID: 105062 Summary: This knowledge base article provides a comprehensive list of runtime errors related to the AppAware feature in BDRSuite (Backup and Disaster Recovery) and offers potential solutions for each specific error. When encountering ...
Error Creating Dump Location in MS Outlook Backup
KB ID: 34 Error Message: Encountering the error: "Error while creating the dump location <Dump Location> - MS_Outlook." Cause: The configured dump location for the specified backup schedule is either inaccessible, or BDRSuite lacks sufficient ...