Answered by:
Mysterious transaction log file growth

Question
-
About a year ago I had a problem I had to involve Microsoft with. Transaction logs were literally blowing up on multiple mail stores. It took weeks, but the end result was a bad CRM email router.
Recently, I have a similar, much smaller scale issue. I have one mail store log that's going through spurts where something happens and I get 4-6 logs in a one minute period, then it goes back to normal.
I remember when this happened before was that you can't look inside the logs because they're encrypted. Microsoft had to escalate several levels to get someone to look in those logs and still all they could give me an account.
I'm trying to do my due diligence this time before having to go that route. One of the tools they taught me how to use (a little) was Exmon, which monitors active connections to a mailbox server. This wasn't much help berfore but I'm trying to use it again.
There are a couple of users that seem to have consistently high transactions. This is probably due to having multiple devices.
Does anyone know any other way to troubleshoot mysterious log growth?
Tuesday, November 20, 2012 8:20 PM
Answers
-
Follow the process on the link:
If you are still not able to narrow down, i would say This is the kind of issue that's best solved by opening an incident with Microsoft Support Services.
M.P.K ~ ( Exchange | 2003/2007/2010/E15(2013)) ~~ Please remember to click “Vote As Helpful" if it really helps and "Mark as Answer” if it answers your question, “Unmark as Answer” if a marked post does not actually answer your question. ~~ This Information is provided is "AS IS" and confers NO Rights!!
Tuesday, November 20, 2012 11:07 PM
All replies
-
Exchange Version ? Service Pack ? Rollup Update ?
In case if your EXchange Version is Exchange 2010 SP2 then you may run:
Get-StoreUsageStatistics -Server ServerName
Also refer to the info on the links below:
http://technet.microsoft.com/en-us/library/ff477617.aspx
M.P.K ~ ( Exchange | 2003/2007/2010/E15(2013)) ~~ Please remember to click “Vote As Helpful" if it really helps and "Mark as Answer” if it answers your question, “Unmark as Answer” if a marked post does not actually answer your question. ~~ This Information is provided is "AS IS" and confers NO Rights!!
- Edited by PK M Sunday, December 2, 2012 3:33 AM
Tuesday, November 20, 2012 9:55 PM -
Exchange 2007, Rollup 8, SP3
- Edited by Statistic Tuesday, November 20, 2012 9:58 PM
Tuesday, November 20, 2012 9:58 PM -
Follow the process on the link:
If you are still not able to narrow down, i would say This is the kind of issue that's best solved by opening an incident with Microsoft Support Services.
M.P.K ~ ( Exchange | 2003/2007/2010/E15(2013)) ~~ Please remember to click “Vote As Helpful" if it really helps and "Mark as Answer” if it answers your question, “Unmark as Answer” if a marked post does not actually answer your question. ~~ This Information is provided is "AS IS" and confers NO Rights!!
Tuesday, November 20, 2012 11:07 PM -
Thanks for the help. This looks like a very long and drawn out process that I will have to find the time for later.Monday, December 3, 2012 7:48 PM