Expect log sequence 'xxx' but found '...\E000xxx.log'

"Expect log sequence 'xxx' but found 'SERVERNAME\Microsoft Information Store\First Storage Group\E000xxx.log'"

This error occurs when the log sequence of MS Exchange was altered by other backup software, e.g. NTBackup. Thus when the Advanced client next performs a MS Exchange backup, the Exchange log sequence would not match the one that it is expecting. With the broken sequence, the Exchange server cannot be restored to its latest state.

To resolve this problem, you need to deactivate all other backup software that is operating on MS Exchange, and then you need to perform a Full MS Exchange database backup manually via the Advanced client.

Alternatively, instead of backing up transaction logs during the weekdays, you can consider doing Full Exchange Database backup on a daily basis with the In-File Delta option enabled. This should avoid interference from other backup software while keeping the amount of upload data to minimal.

This error could also occur, if the user has changed the minimum size for In-File Delta to a value smaller than the corresponding Exchange log file size, i.e. 1MB for MS Exchange 2007 and 5MB for MS Exchange 2000/2003. The Advanced client would then generate deltas for Transaction log backups, thus causing the expected log sequence error.

Was this answer helpful?

 Print this Article

Also Read

The statement BACKUP LOG is not allowed while the recovery model is SIMPLE

If you received this error message: "[Microsoft][ODBC SQL Server Driver][SQL Server]The...

CExBackup::backupFile:WriteFile: Error Number 0x6: The handle is invalid

If you see this error message: "CExBackup::backupFile:WriteFile: Error Number 0x6: The handle is...

An incremental backup cannot be performed when circular logging is enabled

If you get the following error message: "CExBackup::backupService:HrESEBackupSetup: Error Number...

The process cannot access the file because it is being used by another process

If you get the following error message: "The process cannot access the file because it is being...