A client of ours recently installed TrendMicro OfficeScan on their Exchange 2007 server / Windows 2008 R2 Standard, however, they didn't configure OfficeScan to exclude the \Microsoft Exchange Server\Mailbox directory. Trend got in the way and attempted to quarantine a transaction log file stating that there is a virus infection within the log file itself. Ever since that, Backup Exec has been saying that the consistency check cannot be completed because of transaction log file corruption. I would like to know a safe way to delete the log files manually without losing any mail content. I have yet to try Windows Backup to see if the logs purge out but I doubt they will. I have done disaster recovery in the past with Exchange 5.5 with manual logs deletion, however, I do not know how Exchange 2007 responds to this.

If they have missed being deleted in the past, then they will not be deleted in future. I would try moving the log file location (out of office hours), and then deleting (or, for now, moving) what log files are left. Or, if you are feeling brave, just delete the ones that are a lot older than the others. Not much different to what you might have done with E5.5.Outlook Web Access For PDA , OWA For WAP www.owa-pda.com email a@t leederbyshire d.0.t c.0.m

If the database is up, and just throwing errors in the backup, then another option would be to create a new database, move all the data using move mailbox then drop the original. All of its files can then be deleted because they are not required. Simon.Simon Butler, Exchange MVP. http://blog.sembee.co.uk , http://exbpa.com/

Why you don't pick quartine message from trend and put log files in original place then try to take backup so log would be purged. Else safely dismount databse (Once you dismount DB all logs will be commit into DB), you can use eseutil /mh to check LOG status which commited. Then you remove log files from exchange and start mount databse again. Anil

Yes, I have considered that. But OfficeScan never successfully quarantined the log file because Exchange had a hold of it. So the log files are still there, just somehow altered by OfficeScan, thus now corrupted. I will try your method to rectified the situation. Dismount, eseutil /mh, mount.

Hi, Or you can use Exeutil /mk filename.chk to view the header of a checkpoint file to see which logs are commited to database. Please don't forget make a full backup after remove(move) the logs.Frank Wang

Hi ronnieshih, How about your question? Any updates?Frank Wang

Hi ronnieshih, Any updates on your issue?Frank Wang

Hi there, sorry for the delay. I've been on vacation the entire last week. I have not been able to work on this because taking down the Exchange store at this bank will be a weekend outage so I'm waiting for approval from the client to get this accomplished.