254 results:

  1. AhsayOBM File backup fails: Shadow Copy snapshot missing

    File backup on AhsayOBM/AhsayACB v7 ends with error: "Snapshot for Shadow Copy Set is missing, backup terminate." indicating VSS snapshot failure.

  2. AhsayRDR connector not auto-migrated to AhsayCBS during upgrade

    When upgrading AhsayOBS and AhsayRDR (v6) to AhsayCBS v7.5.0.0, RDR connector settings are not automatically migrated if using the installation executable.

  3. AhsayOBM auto update fails on CentOS/RHEL – "Cannot run fuser"

    AhsayOBM auto update fails with "Cannot run program fuser" if the PSmisc package is missing on CentOS/RHEL, even when Auto Update Agent (AUA) is enabled.

  4. AhsayCBS does not auto-suspend backup account after AD user is deleted

    In AhsayCBS with Active Directory Integration enabled, backup accounts are not automatically suspended when the corresponding AD user is deleted.

  5. Backup data not restorable after converting to Destination Pool

    Backup data becomes unrestorable if a single storage destination is converted into part of a Destination Pool via the AhsayCBS console.

  6. AhsayOBM backup fails during space freeing up – log corrupted error

    Backup with retention enabled fails during space freeing up. Error: Log file is corrupted, caused by NullPointerException in usage statistics log.

  7. Cannot access AhsayOBM backupset created via AddBackupSet.do API

    AhsayOBM prompts for encryption key when accessing a backupset created via AddBackupSet.do API using "DEFAULT" encryption type.

  8. Cannot set network drive as Userhome on Windows

    Adding a network drive as User Home in AhsayCBS on Windows fails with error: "The file/folder '\' does not exist."

  9. AhsayOBM cannot back up Google Drive items with underscore in name

    CloudFile backup for Google Drive fails if file or folder names contain underscore (_). Error: Parent directory does not exist is shown in the report.

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