KB ID : 89
Published : Jan. 19, 2016
Created : Jan. 19, 2016
Last Modified : June 26, 2016

Normally, this error would occur if the log files are not purged properly during the previous full/incremental backup or the archive bit was not reset properly in the previous full/incremental backup, and also due to any of the following reasons:

Cause 1

If the circular logging option is enabled or the circular logging option has been changed and the information store has not been restarted at least once after the change or a full backup has not yet run after the change.

Solution 1

Disable circular logging and after changing the circular logging option, restart the Microsoft Exchange Information Store service once and check if the incremental backups run successfully thereafter. If this does not resolve the issue, try running an additional full backup before proceeding with the incremental backups.

Cause 2

After a successful restore, if incremental or differential logs backup is performed before running a full backup then Exchange Server backup report will display the above error message.

Solution 2

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

Cause 3

If a new Mail Store is added to existing Storage Group which was already configured for backup.

Solution 3

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

Cause 4

This issue could arise when Vembu BDR is trying to run an incremental backup on an Information Store in a Storage Group where even one of the remaining Information Stores in the Storage Group has not been configured for full backup at least once. In such a situation, Exchange Server will not allow Vembu BDR to purge the logs files for the configured Information Store.

Solution 4

Configure full backup for the remaining Information Stores temporarily and you can delete this backup schedule later if this backup is not needed.

Cause 5

If the backup data existing in the local dump location is inconsistent to append the incremental backups due to the reason that “Information Stores” might have been configured with 2 different backup software’s for backup.

Solution 5

In this case, this issue can be resolved by configuring additional full backup in Vembu BDR. You can schedule an additional full backup for your Exchange Server backup schedules by editing the Exchange Server backup schedule. You can do this by going to the page ‘Backup -> List Backup Schedules -> <backup_name> -> Edit Backup configuration’ and enable ‘Run additional full backup after saving this configuration’ in ‘Advanced Settings’. Before scheduling additional full backups in Vembu BDR, you should disable/remove Exchange Server backup schedules configured with other software or Windows Native backup.

Make sure that your Exchange Server is not backed up by any of these:

1) A backup software.

2) Native Windows Server Backup which uses VSS to create snapshots and purges logs after the backup completes.

If you wish to backup the Exchange Server databases using multiple backup application for added redundancy, then we would suggest you to configure only “Full Backups” of the Exchange Server databases. In this method, Vembu BDR/other backup application will backup the full Exchange Server database for every backup schedules. This will take more time and bandwidth. Therefore, you may have to schedule this full backup of Exchange Server data less frequently and also make sure that one application starts the full backup schedule only after the other has completed it.

After checking all the above things, we would recommend you to run an additional full backup[if not yet run after the changes] successfully and then proceed with further incremental backups.

edit retag flag offensive close merge delete