Our Exchange 5.5 box has been producing an ESE97 error in its logs.
Event ID:105, Source: ESE97, Type: Error, Category: Logging/Recovery
Description: MSExchangeIS (267) The database engine has stopped the backup with error -1811.
This occurs when our Backup Exec attempts to perform a differential backup, the ESE97 starts the backup...MSExchangeDS (236) The database engine is starting an incremental backup...but on the second go of the MSExchange IS, the above log is produced.
MS article Q178934 says that this is a JET_errFileNotFound error, and that the error signals that a transation log is either missing of corrupt. It recommends that the IS be stopped, and all .log files in \exchsrvr\mdbdata and the edb.chk from the \exchsrvr\mdbdata be moved to a temporary directory. It then recommends restarting the IS and performing an online backup.
Veritas has an article that mirrors this one, however it recommends (smartly), a flat file backup before removing the logs It also aims the article at 5.0, but the MS article says this info applies to 5.0 and 5.5.
My concern is in the accuracy of these articles. Like others, I've been stung by the inaccuracy of these articles and, with an issue as serious as removing the logs/edb.chk and starting the IS, I wanted to check with and get the opinion of an expert first. As well, the event I am experiencing starts with "MS Exchange IS (267)" whereas the MS article refers to (190) and (202) and the Veritas article refers to (329).
Your advice would be appreciated.