260 results:

  1. MS SQL backup fails: "Cannot start shadow copy, reason=null"

    MS SQL database backup fails with "Cannot start shadow copy, reason=null" error in the backup report, indicating an issue initializing VSS.

  2. Incorrect "Another backup job is running" error on Domino backup

    IBM Lotus Domino/Notes backup shows incorrect "Another backup job is still running. Backup skipped." message, even when no other job is active.

  3. Replication limit 0 Kb/s not enforced; data still replicates

    Replication continues even when traffic limit is set to 0 Kb/s. This is a known issue in AhsayCBS versions prior to 7.7.0.0.

  4. Index migration runs on every job after Exchange DAG backupset upgrade

    After upgrading AhsayOBM v6 to v7.3.2.0–7.5.0.2, Exchange DAG mail-level backup sets trigger index migration during every backup job.

  5. Corrupted index detected during AhsayOBM Data Integrity Check

    Data Integrity Check shows "Index file is corrupted" for a backup destination and prompts user to delete all data to resolve the issue.

  6. Invalid ID error during Office 365 Exchange Online mailbox backup

    Office 365 Exchange Online backup fails for large mailboxes with "[ExchangeStandardFolder.getOrdinal] Invalid ID" error in AhsayOBM backup report.

  7. Troubleshooting problem with missing scheduled backup

    Follow these guidelines to troubleshoot missed scheduled backups and ensure backups run as expected in Ahsay Products

  8. Duplicate Predefined Destinations allowed in AhsayCBS console

    AhsayCBS console allows creation of multiple Predefined Destinations with the same name. This is a known issue in versions 7.3.2.0 to 7.5.0.6.

  9. AhsayOBM continuous backup skips data if file size limit is Unlimited

    With Continuous Backup enabled, setting "Only apply to files smaller than" to "Unlimited" causes no data to be backed up.

  10. RDR License Error shown on CBS not using Redirector module

    AhsayCBS not using Redirector may show RDR License Error and send license alert emails. This is a known issue in versions prior to 7.7.0.0.