254 results:
Hyper-V Cluster backup fails: CBT log mismatch with VM owners
Hyper-V cluster backup fails with "Unable to generate delta using CBT" due to mismatch between CBT log files and number of VM's preferred owners.VMware VDDK backup fails: Snapshot not taken due to no state change
VMware VDDK backup fails with snapshot error: "Snapshot not taken since the state of the virtual machine has not changed since the last snapshot operation."VMware backup job fails to complete with schedule disabled
VMware backup job fails with "Backup Interrupted by Scheduler" if no schedule is set and job runs longer than 5 minutes in AhsayOBMVMware Run Direct VM fails to boot: "Operating System not found"
VMware Run Direct restore may show success, but VM fails to boot with "Operating System not found" if backup is on a network drive with auto power-on enabled.Error 577: Windows can't verify driver during Hyper-V Run Direct
Hyper-V Run Direct restore fails with Error 577: Windows cannot verify the driver’s digital signature due to unsigned or damaged system file.Error: NFS service not running during VMware Run Direct restore
NFS Service must be running and ports 111, 1058, 2049 open for VMware Run Direct restore to work with Ahsay on Windows.Backup Error: Failed to flush buffer to this destination
Backup fails with "Failed to flush buffer to this destination" due to unstable network connection between AhsayOBM/AhsayACB client and backup destination.HTTP Error 400: Download failed during AhsayACB installation
AhsayACB install fails on Windows or MacOS X with "HTTP error 400: Bad request" when downloading files. Check your internet connection and retry.Error: Invalid sClientid shown after selecting Google Drive restore
Restore fails with "[GDriveManager.getAppName] Invalid sClientid: null" error after selecting Google Drive as the backup destination in AhsayOBM/ACB.File Backup Error: "[IOException] [NixUtil.c][read] Invalid argument"
AhsayOBM file backup on Linux fails with "[IOException] [NixUtil.c][read] Invalid argument" error shown in the backup log.