Hi Everyone, I've finally found the root cause of my transaction log problem which grows uncontrolled (when the daily full backup missed just one day only this storage group with this particular mailbox out of space), 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 ? Any kind of help and assistance would be greatly appreciated. Thanks, Albert /* Server Support Specialist */

Not sure which version of Exchange you are using, but this might help: http://blogs.technet.com/b/mikelag/archive/2009/07/12/troubleshooting-store-log-database-growth-issues.aspx ExMon http://www.microsoft.com/downloads/en/details.aspx?FamilyID=9A49C22E-E0C7-4B7C-ACEF-729D48AF7BC9&displaylang=en should help you figure out what is happening with the mailbox if it's something the user is doing. Or it could be some weird rules or recurring items inside the mailbox.

It can be many reasons likely some looping with the mailbox. One issue that comes to mind is the old entourage bug, but again it can be many reasons from rules, scripts, bugs, etc. The links below go over some troubleshooting techniques. Troubleshooting Fast Growing Transaction Logs on Microsoft Exchange 2000 Server and Exchange Server 2003 http://technet.microsoft.com/en-us/library/aa996191(EXCHG.65).aspx#MacintoshEntourageClientsResendBug Defeated by Unexpected Transaction Log File growth http://blogs.technet.com/b/jeff_stokes/archive/2009/01/25/defeated-by-unexpected-transaction-log-file-growth.aspx Exchange: Transaction Log Files Growing Rapidly; Case Scenarios http://msexchangetips.blogspot.com/2006/08/exchange-transaction-log-files-growing.htmlJames Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

I'm using E2k7 SP1 my current solution that I had in mind is: 1. Export mailbox 2. Delete it 3. create same name mailbox 4. Import the mailbox (hopefully the Full access permission and the Send as will be the same). And of course it must be done after office hours./* Server Support Specialist */

thanks for the reply, in this case I don't have any Mac computer connecting to the domain./* Server Support Specialist */

You can try recreating the offending mailbox, it may or may not help. At least it will delete any rules hidden or not that cause possibly be one of the reasons. The mailbox\sendas permissions will not be preserved unless it is inheriting at the DB level or above. You also want to ensure that you're setting mailbox quota limits for both send and receive restrictions. This ensures that when you run into looping issues that it doesn't consume all your disk space shutting down Exchange.James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

ah, ok, that is why I'm doing the four steps defined below. at the moment this MB size is just 600 MB with approximately under 50k email items. So by putting a limit of 1 GB to avoid growing extremely large is that what you suggested ? I will also try to dig around the Transport Message log related to this mailbox./* Server Support Specialist */

Yes by implementing a 1GB send\receive limit your DB size and transaction logs do not continue to grow beyond that point if looping still occurs. The blog post that cn9 provided from Mike Lagase to troubleshoot log growth is probably the best comprehensive troubleshooting steps out there. Troubleshooting Exchange 2007 Store Log/Database growth issues http://blogs.technet.com/b/mikelag/archive/2009/07/12/troubleshooting-store-log-database-growth-issues.aspxJames Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

Perhaps devices gone wild like BES servers but more recently there has been a rash of incidents regarding iPhones etc. http://msexchangeteam.com/archive/2010/06/30/455342.aspx If you want to see if the problem is coming from an internal Device/Machine you can use one of the following MS USER MONITOR: http://www.microsoft.com/downloads/en/details.aspx?FamilyId=9A49C22E-E0C7-4B7C-ACEF-729D48AF7BC9&displaylang=en and here is a link on how to use it http://www.msexchange.org/tutorials/Microsoft-Exchange-Server-User-Monitor.html And of course the previous article I posted http://blogs.msdn.com/b/scottos/archive/2007/07/12/rough-and-tough-guide-to-identifying-patterns-in-ese-transaction-log-files.aspx?PageIndex=2#comments Troy Werelius www.Lucid8.com

Hi Albert, Any update for your issue? Regards! GavinPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

yes, recreating the mailbox solves the problem so far./* Server Support Specialist */