Problem while dumping backup d...

Join our new BDRSuite Community Forum and connect with fellow members for better collaboration and support!

Hi all

We have an Exchange Database backup running from the Client Server to Our server offsite.

It started with a full backup and then continued to run incremental.

It failed and will only re-run if I force it to run a full backup. It will then re-run as an incremental backup until it gets to Sunday to which it will then fail. It does not work after this, we are presented with the error message above.

edit retag flag offensive close merge delete

asked 2015-07-07 10:33:03 -0500

This post is a wiki. Anyone with karma >75 is welcome to improve it.

1 reply

Re: Problem while dumping backup data in Client Side. Error : Database Snap process of store(s) failed.

by emmanuel

The error message "Problem while dumping backup data in Client Side . Error :Database dump process of store(s) failed.

The warning message "Database dump process of store(s) failed..." would occur in one of the following conditions :

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 MailStore is added to existing Storage Group which was already configured for backup.

Solution 3:

Cause 4:

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

Solution 4:

Configure full backup for the remaining Information Stores temporarily. And later you can delete this backup schedule 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 for backup.

Solution 5:

In this case, this issue can be resolved by configuring additional full backup in VembuOnlineBackup. 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 VembuOnlineBackup, 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 ... (more)