I've got a 3 node active/passiveexchange 2003 cluster. We split our resources between 2of the nodes, with the last 1 being the passive. The issue I'm seeing is the transaction log files are growingat an extreme pace for justparticular storage group on 1 of these actives nodes. the SG has 2 mail stores. As far as I know, I'm just seeing the issue on this one storage group. Has anyone encountered this problem before? What steps can I take to troubleshoot and find the culprit? This weekend I was looking to perform an offline defrag on the DBs in this storage group but in the end is that really going to resolve this issue? We do have public folders, but the replicas are all housed on our bridgehead servers.

Hi,~ You can take a look at couple of below articles, if you didn't already...Troubleshooting Fast Growing Transaction Logs on Microsoft Exchange 2000 Server and Exchange Server 2003http://technet.microsoft.com/en-us/library/aa996191(EXCHG.65).aspxFAST GROWING DATABASES & TRANSACTION LOGS ON EXCHANGE 2000 & 2003.http://exchangeserverinfo.com/2007/06/23/fast-growing-databases--transaction-logs-on-exchange-2000--2003.aspx- You may need to contact Microsoft PSS to work with and to get looping message tools described in this article.~ You can also scan message tracking logs with log parser, if you suspect high mail flow from any user sitting in that DBs/SG.Exchange 2003 statistics with Logparserhttp://anewmessagehasarrived.blogspot.com/2008/03/exchange-2003-statistics-with-logparser.htmlAmit Tank | MVP - Exchange | MCITP:EMA MCSA:M | http://ExchangeShare.WordPress.com

We never did find the exact reason behind this issue. The articles you posted were very helpful, but none of them seemed to point towards a solution. We found that it was 1 particular store in this SG that was causing the problem. We ended up unmounting the mail store, and then running eseutil /g. This didn't find much, but once we brought the store back online we have yet to see the transaction logs go nuts like they were.We did contact Microsoft directly on this, and they too couldn't point us definitely to a possible reason as to why this happened. They told us that either the database was corrupt or possibly it was MAC clients connecting to our exchange server. Honestly I don't think it was either, but issue resolved for now. Can't wait to migrate to 2007!!