Hello All,

A legacy Exchange 2003 server crashed and was restored from an offline backup.

Two of the roughly 3k transaction log files from the MDBDATA folder are corrupted. The corruption is at the beginning of the log file series.

Since there is much valid data after these corrupted files is there any way to replay the rest of the log files or repair the corrupted files?

TYIA,

~eric

Give this a shot http://msexchangeguru.com/2013/02/01/jet_errmissinglogfile-528-548/

Hi,

For your question, we need use eseutil /ml log file name to test whether it's corrupted, for example: eseutil /ml e00123ab.log. If the log file fails the test, the following response appears: CORRUPTION DETECTED in log file: Log File Name.

If these solutions are not workable, we can repair the database by using the "hard repair" (/p) functionality of the Eseutil utility. Before you do this, make sure that you back up all the database files in a storage group (*.log files, *.edb files, and *.stm files). For your reference: https://support.microsoft.com/en-us/kb/248122

Thanks

Exchange cannot repair damage to log files because of factors other than torn writes, which will be fixed automatically by the ESE engine. Hardware failures that randomly damage a log file cannot be overcome because the data that was obliterated cannot be reliably reconstructed. ESE event 465 indicates damage that cannot be repaired. (As per Microsoft)

Not sure if it works, but you may give it a try. Guide to repair Exchange Log.

• Edited by Peter Gomes II 22 hours 20 minutes ago