Users may encounter the error message "The database missed a previous full backup before the incremental backup" in BDRSuite Client. This can occur due to various reasons, and the article provides solutions based on the specific cause.

Cause 1:

If the circular logging option is enabled or changed without restarting the Microsoft Exchange Information Store service or running a full backup.

Solution 1:

Disable circular logging, restart the Information Store service, and perform an additional full backup before proceeding with incremental backups.

Cause 2:

Incremental or differential logs backup is performed after a successful restore, and a full backup has not been run.

Solution 2:

Check the option "Run additional full backup after saving this configuration" in the "Edit Exchange Server Backup Schedule" page and proceed with incremental or differential log backup.

Cause 3:

A new Mail Store is added to an existing Storage Group configured for backup.

Solution 3:

Check the option "Run additional full backup after saving this configuration" in the "Edit Exchange Server Backup Schedule" page and proceed with incremental or differential log backup.

Cause 4:

Incremental backup is hindered when one Information Store in a Storage Group lacks a full backup.

Solution 4:

Temporarily configure full backup for remaining Information Stores and delete the schedule later if not needed.

Cause 5:

Inconsistent data in the local dump location prevents appending incremental backups, possibly due to multiple backup software configurations.

Solution 5:

Configure additional full backup in Vembu BDR, ensuring no conflicting backup schedules from other applications. Schedule full backups less frequently for each application.

Additional Recommendations:

1. Ensure no conflicting backups by other applications or Windows Native backup.
2. If using multiple backup applications for redundancy, schedule full backups less frequently for each application to avoid overlap.
   

After addressing the identified cause, run an additional full backup (if not done after changes) and proceed with further incremental backups.