How to manually remove Exchange Server 2007 transaction log files
Hi, How do i manually delete transaction log files in Exchange 2007. Did it a few time in exchange 2003 but seems to be diffrent in 2007. So prob just need to commands that will tell me what the last committed log file is.
January 5th, 2010 8:21am

Is there a reason why you dont want to run an incremental or full backup to clear the log files?Mark Morowczynski|MCT| MCSE 2003:Messaging, Security|MCITP:EMA 2K7,EDA Win 7,ES,SA,EA|MCTS:Windows Mobile Admin|Security+|http://almostdailytech.com
Free Windows Admin Tool Kit Click here and download it now
January 5th, 2010 9:34am

Enable Circular Logging, dismount the database and mount the database.If you can't do Circular Logging then you will need to use eseutil /mk to locate the last good log file and move the ones out and eventually delete them.Take a look here:XADM: Using Eseutil to Determine Which Logs Have Been Committedhttp://support.microsoft.com/default.aspx/kb/182961SF - MCITP:EMA, MCTS: Exchange 2010, Exchange 2007, MOSS 2007, OCS 2007 -- http://www.scottfeltmann.com
January 5th, 2010 1:36pm

This KB applies to: Microsoft Exchange Server 5.5 Standard Edition Microsoft Exchange 2000 Server Standard Edition TheWall_RSA wants to "manually delete transaction log files in Exchange 2007." He "did it a few time in exchange 2003 but seems to be different in 2007."Was searching myself for information on this, but did not find any good link. Is the procedure different?MCTS: Messaging | MCSE: S+M | Small Business Specialist
Free Windows Admin Tool Kit Click here and download it now
January 6th, 2010 12:40am

Or you could do daily full backups. When backups are ran it should remove transaction logs that are no longer needed. SF - MCITP:EMA, MCTS: Exchange 2010, Exchange 2007, MOSS 2007, OCS 2007 -- http://www.scottfeltmann.com
January 6th, 2010 3:02pm

I did run a backup after i deleted enough logs to receive mail again. For some reason our monitoring software did not pic up that the server was almost out of space. The backup is now completed but it did not clear the logs. Used windows backup on Win 2008... What could the reason for this be? Windows Server Backup on Windows 2008 prior to Exchange 2007 Service Pack 2 will not delete the transaction logs. Once you install Exchange 2007 SP2, Windows Server Backup includes a plugin which is Exchange aware and your transaction logs will be deleted.
Free Windows Admin Tool Kit Click here and download it now
January 6th, 2010 4:08pm

I did run a backup after i deleted enough logs to receive mail again. For some reason our monitoring software did not pic up that the server was almost out of space. The backup is now completed but it did not clear the logs. Used windows backup on Win 2008... What could the reason for this be? Windows Server Backup on Windows 2008 prior to Exchange 2007 Service Pack 2 will not delete the transaction logs. Once you install Exchange 2007 SP2, Windows Server Backup includes a plugin which is Exchange aware and your transaction logs will be deleted. Great, starting the download now.
January 7th, 2010 1:27am

I just had this same problem, on Win2003 Standard SP2 with Exchange 2007 Enterprise SP2. I opened a case with Microsoft tech support to fix it last night. My D: drive where I keep the Exchange transaction logs was 67.9 GB total. It normally has 66.0 GB of free space and 1.89 GB used space. But, a couple months ago I uninstalled the Backup Exec agent, because I switched to Acronis. But I had not installed Acronis Exchange backup, just regular Acronis backup, so the Exchange logs weren't getting purged. So, last night I had 64.7 GB of transaction logs and only 1.3 GB of free space, which was going to run out in about 12 hours. Here's what we did. The actual fix was to re-install the Backup Exec 11 agent onto the server and back up Exchange, which took about 5 hours. It was nerve-wracking, because Backup Exec showed status of "Consistency Check" for over an hour at the beginning of its job, and I thought it was hung. That backup cleaned out the transaction logs and was the engineer's preferred method. So, I'm back to 66.0 GB of free space like normal. Whew. If that didn't work, here was his proposed solution in his own words: if you want to manually remove log files, then dismount the database manually check the health running eseutil /mh path of the database with database nameif its in clean shut down state then go to log file location then move or remove the all the files and make that location emptythen come back to console, right click on database- go to-properties and you will have option this database can be overwritten by a restore, check that option and applythen re mount the database
Free Windows Admin Tool Kit Click here and download it now
March 14th, 2012 10:58am

Hi As my adviced don't remove tracating logs manually, It will be made your database in dirty state or crupt EDB DATA file or may be some mail will be missed in users mailbox. Should you try to take full backup though Ntbackup which is integrated tools of Windows server. Hope your problem will be resolved.
June 3rd, 2012 10:53am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics