Handling Inconsistent Incremental Backups in BDRSuite for Exchange Server Databases

Handling Inconsistent Incremental Backups in BDRSuite for Exchange Server Databases

KB ID: 109105
Issue:
The last Incremental Backup of the database +<currDBName>+ appears to have been executed from another application instead of BDRSuite  for Exchange Server. The last Incremental Backup executed by BDRSuite for Exchange Server was at [+<lastIncrementalBkpTime>+].
Cause:
This inconsistency in backup sets occurs when using another backup software in conjunction with BDRSuite for Exchange Server to back up Exchange Server Databases.
Solution:
To address this issue and ensure data consistency, it is crucial to configure and schedule Exchange database backups using only one backup software. The problem arises when both Vembu NetworkBackup and another backup software attempt to back up the same Exchange Server storage group, leading to changes in the database dump reference. As a result, both sets of backed-up data may become inconsistent.
To avoid this, follow these steps:
  1. Edit the backup job for your Exchange backups by navigating to the page 'Backup' -> 'List Jobs' -> <backup_name> -> 'Edit Backup Configuration.'
  2. Enable the option 'Run additional full backup after saving this configuration.'
By scheduling an additional full backup, you ensure that BDRSuite for Files and Application handles the Exchange backups consistently, minimizing the risk of data inconsistency across multiple schedules.

    • Related Articles

    • Exchange Transaction Log Not Purged After Successful Backups

      KB ID: 83 Cause: The issue of Exchange transaction logs not being purged after successful backups in Vembu's Exchange Server Plugin is attributed to the utilization of Microsoft's API (VSS for Exchange 2003/2007/2010). This API is responsible for ...

    • Mismatched Incremental Backup Time with BDRSuite Database

      KB ID: 110004 Cause: If you were using another backup software concurrently with BDRSuite, inconsistency in backup sets might occur, especially when backing up SQL Server database(s) using multiple applications. This inconsistency arises from SQL ...

    • Exchange Server Backup aborted

      KB ID: 101023 Cause This error will occur due to the following reasons: The database is not mounted (ERROR CODE: 109102) If circular logging is enabled for the database (ERROR CODE: 109106) If the backup was taken by third-party software ((ERROR ...

    • Backup aborted

      KB ID: 101005 Product: BDRSuite Backup Server Cause This will occur due to the following reasons: Backup configuration stored in the server and client is incompatible. When the Backup storage location is inaccessible to the backup server. If you ...

    • Circular Logging Enabled - Cannot Perform Incremental/Differential Backups

      KB ID: 109106 Issue: When attempting to perform incremental or differential backups, you may encounter an error due to circular logging being enabled for the storage group/databases designated for backup. Solution: To resolve this issue, follow these ...