- Product Version:
Servosity Pro: All
OS: Windows - Problem Description:
When performing a MS Exchange server backup, the following error message is received in the backup report:
Example when *.edb is missing: Backup Logs No. Type Timestamp Backup Logs 1 Info YYYY/MM/DD hh:mm Start [ Windows platform (Support), ServosityPro x.x.x.x ] 2 Info YYYY/MM/DD hh:mm Start running pre-commands 3 ... ... ... * Error YYYY/MM/DD hh:mm The last backup jobs of *.stm (YYYY-MM-DD-hh-mm-ss) and *.edb (none) don't match for database 'SERVER\Microsoft Information Store\First Storage Group\Mailbox Store'
or
Example when *.stm is missing: Backup Logs No. Type Timestamp Backup Logs 1 Info YYYY/MM/DD hh:mm Start [ Windows platform (Support), ServosityPro x.x.x.x ] 2 Info YYYY/MM/DD hh:mm Start running pre-commands 3 ... ... ... * Error YYYY/MM/DD hh:mm The last backup jobs of *.stm (none) and *.edb (YYYY-MM-DD-hh-mm-ss) don't match for database 'SERVER\Microsoft Information Store\First Storage Group\Mailbox Store' Errors found while validating your backup files. Please run a full backup to correct the problem. - Cause:
A valid MS Exchange server backup consists of a matching pair of files database.stm and database.edb. The backup checks the creation timestamp of these 2 files to ensure they are syncronized. If the error message above is received, it implies that during a previous backup, there was a problem backing up either the database.stm or database.edb file. More recent versions of MS Exchange have dropped the database.stm file from a backup set and do not suffer from this problem. - Resolution:
To resolve the issue, please perform a full MS Exchange server backup manually via the Servosity Pro console by clicking "Backup" from the main Servosity Pro window. Please select your Exchange backup set, select "Database", click "Options", select "FULL" under "In-file delta type", and then click OK.
Please allow this backup to run to completion. You may still receive the same error as above, but since an In-file delta FULL backup is being performed, the database.stm and database.edb files will be uploaded in their entirety. The problem will be resolved on the next subsequent backup job.