Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I've finally found the root cause of my transaction log problem few months ago, it seems that one of the mailbox in my exchange server storage group caused this problem.

Does anyone have any suggestion of what to do to diagnose it further or perform anything that is non disruptive as it is currently running in production ?

Thanks

share|improve this question
2  
can you link to your old problem or describe further? –  pablo Feb 27 '11 at 22:42
    
when the daily full backup missed just one day only this storage group with this particular mailbox out of space. –  Server System Specialist Feb 27 '11 at 22:45
2  
I assume you're talking about serverfault.com/questions/229398/… but if your log files volume fills up after missing one backup then either that server is being used as cthulu's very own spam portal to the whole earth or the log file volume is very much incorrectly sized for the job its being asked to do. That's pretty much all there is to it imho. –  RobM Feb 27 '11 at 23:12
1  
I should add that if its a spammer then the fact that its hitting your mail database suggests a legitimate account which has been compromised, so they can send mail as an authenticated user. –  RobM Feb 27 '11 at 23:20
    
LOL very good finding Robert, only this one particular mailbox which is used by the help desk team in production causing problem, whenever i moved it around to different storage group, it always grows the Transaction log until it is full and causing the whole mailbox in that particular storage group stops sending and receiving email. –  Server System Specialist Feb 27 '11 at 23:30

1 Answer 1

up vote 2 down vote accepted

I had this problem a couple years ago on one of my 2003 Exchange servers. 1 user had an item in her outbox that was causing our logs to grow like crazy. Deleted the item and the problem disappeared. It's about that time that I lost faith in Exchange 2003...

If you don't know which mailbox is causing this, you can find out from ESM. Drill down to the logons of the mailbox store. Add the column for total ops and sort by that. You'll probably find a user with a ton of ops (like over 100). That's your culprit.

share|improve this answer
    
thanks for your reply Jason, in the Exchange Management Console 2007 it is not possible to view that :-| let me have a look with ExMon –  Server System Specialist Feb 28 '11 at 0:23

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.