266 results:

  1. Log files missing after AhsayCBS install/upgrade on Linux

    After installing or upgrading to AhsayCBS v7.3.2.0–7.5.0.0 on Linux, context log files (e.g. cbs_context_*.log) may not be generated in the logs folder.

  2. VMware Granular Restore error "Failed to list file (the media is write protected)

    Granular Restore shows "Failed to list file (the media is write protected)" when mounting a Windows 10 VM disk from a VMware ESXi/vCenter backup set.

  3. Client download page can't localize product names with brackets

    AhsayCBS 7.5.0.2 can't customize AhsayOBM/ACB product names on the client download page for languages with brackets, like Chinese or Portuguese (Portugal).

  4. Incorrect "Another backup job is running" error on Hyper-V backup

    Hyper-V VM backup shows incorrect "Another backup job is still running. Backup skipped." error, even though no other job is in progress.

  5. Network drives not shown as image spool path in System Backupset

    When creating a Windows System Backupset in AhsayOBM, network drives may not appear as selectable destinations for the image spool path, despite being accessib

  6. MS Exchange Mail-Level backup fails: Job interrupted, no schedule set

    Exchange Mail-Level backup jobs over 5 minutes fail with "Backup Interrupted by Scheduler" if no backup schedule is configured in the backup set.

  7. Excessive threads on AhsayCBS after setting SFTP destination

    Configuring an SFTP Predefined Destination for backup or replication may cause AhsayCBS to generate a large number of threads on the server.

  8. AhsayOBM cannot backup network folder on Windows 10 Build 1803

    On Windows 10 Build 1803, backing up network folders with names starting with "#" (e.g. #folder) fails - folders listed after are not properly detected

  9. Incorrect "Another backup job is still running" error on Oracle Backup

    Oracle backup shows incorrect "Another backup job is still running. Backup skipped." message in client interface or report, despite no job running.

  10. AddUser.do API fails to set GMT+/-xx:30 or GMT+13:00 timezones

    Using AddUser.do API to set timezones like GMT+05:30 or GMT+13:00 results in incorrect assignment (e.g. GMT+13:00 is set as WST) despite status showing OK.