267 results:

  1. AhsayOBM Unable to do Offsite backup (Error initializing bptree)

    Offsite backup fails with "Error initializing bptree" if the index file is corrupted due to an unexpected shutdown or crash during a previous backup job.

  2. 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."

  3. VMware 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.

  4. 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.

  5. 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.

  6. 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.

  7. 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.

  8. Hyper-V Granular Restore error "Failed to list file"

    Granular restore of a Hyper-V VM fails with "The volume does not contain a recognized file system" error when mounting the virtual disk in AhsayOBM.

  9. "Connection refused" error when enabling AhsayCBS Replication

    Fix the "Connection refused" replication error in AhsayCBS caused by an incorrect SSL Port or Network configuration settings

  10. Failed to enable replication on AhsayCBS

    "Failed to mkdir" or "Failed to list path" error when enabling replication caused by incorrect replication receiver settings