2373 results:

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

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

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

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

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

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

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

  8. Duplicate databases shown under empty DAG in Exchange backup set

    When creating an Exchange mail-level backup set, databases may appear duplicated under an empty DAG group if the group has no member server in multi-DAG setups.

  9. AhsayACB/OBM installs as CloudBacko Home from CBS 7.7.0.0 installer

    Installing AhsayOBM/ACB from CBS 7.7.0.0 download page may show CloudBacko branding due to incorrect installer branding configuration.

  10. Cannot perform MS SQL differential or log backup in ODBC mode

    When running a MS SQL differential or transaction log backup in ODBC mode, a full backup is performed instead due to a database reference mismatch.