Transaction Log for one mailbox group growing to over 20 GB's in under 15 hours.
I have an Exchange 2007 server and one of our Mailbox databases is generating a log file of over 20 GB's in under 15 hours. the rest of the logs for all the othere mailboxes are all under 300 MB's for the same time frame. is there a way to trouble shoot this and find out what or who is causing this issue.
August 13th, 2010 5:58pm

Hi, These may the reasons behind: SMTP issues or Store issues If the issue is that only the Logs are growing then the first thing we can do to analyze this issue is to stop the SMTP service and check whether the logs are still growing or not. If it still grows then it is not certainly a SMTP issue. It can be a store issue. Possible SMTP Issues are spamming or increased mail flow. Possible STORE Issues are Corrupt mail stuck in the queue and 3rd party software accessing a particular mailboxRegards from www.windowsadmin.info
Free Windows Admin Tool Kit Click here and download it now
August 13th, 2010 8:24pm

I have had to Enable circular logging to keep the log files from filling the database. this has cleaned out the logs and I have started to build more logs now after I disabled Circular Logging. I am not sure if that would rule out the Corrupt store issue you posted above. becasue it still happens after the enable/disable is done.
August 13th, 2010 8:31pm

Chris, I faced similar issues few months back. In three hours time, one drive ~100 GB got filledup and the DBs got dismounted. By the time the monitoring alerts came in, DBs were down. I was able to manage it some how. But it was a tough time to do the postmartam. Here is what I checked: 1) Any mail looping - A creates a rule to forward messages to B and B creates a rule to forward messages to A 2) Review the tracking logs for the last few days and compare it with the last one. This will give a hint if there was a huge amount of email flow due to some unknown reason. 3) File level scanner without exclusion - In few cases, File level scanners without proper exclusion set can cause similar issues. I couldnt get much clue from any of this. To dig further, a case was opened with the MSTS - but no luck as from the logs, they couldn't conclude anything. This link will give more idea on what I told. http://technet.microsoft.com/en-us/library/aa996191%28EXCHG.65%29.aspx Good luck ! -Shaba-
Free Windows Admin Tool Kit Click here and download it now
August 13th, 2010 9:27pm

I would install Exmon on the server and see if any client is hammering it: http://www.microsoft.com/downloads/details.aspx?FamilyId=9A49C22E-E0C7-4B7C-ACEF-729D48AF7BC9&displaylang=en ALso take a look at this blog: http://blogs.technet.com/b/mikelag/archive/2009/07/12/troubleshooting-store-log-database-growth-issues.aspx Troubleshooting Exchange 2007 Store Log/Database growth issues
August 13th, 2010 9:35pm

Thanks Shaba, I will try those option after hours not to impact Product. AndyD, I tried Exmon it was installed when the server was build but the byte logs are at 0 and there is no users names in the Exmon. so that really didn't help me unless it was not install correctly or I missed a step with setting up what I wanted to track.
Free Windows Admin Tool Kit Click here and download it now
August 13th, 2010 9:43pm

ExMon will show all mapi clients that are connected to the store. You have to let it run. I beleive the refresh is set to 1 minute before you'll see the active connections.
August 13th, 2010 9:47pm

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

Other recent topics Other recent topics