We are having an issue with Exchange 2010 SP2 in which one of the mailbox databases is creating a huge amount of transaction logs and we are having to run backup jobs during the day to clear logs to prevent filling the volume that holds the logs. The amount of space for the transaction logs of the affected database (18GBs) is more than twice the amount generated by the next biggest data base (8GBs), and three to four times the size of the rest. Is there a tool or utility I can use that will allow me to identify the mailbox , or mailboxes that are causing this? This database is similar in size and number of mailboxes of several others, yet it is generating 18 GBs of Transaction logs per day, vs 3 - 4 GBs per day of the other databases with a similar number of MBs.
I am assuming there is one MB that is somehow corrupted, or looping something and causing this problem. But so far I have found no method of identifying the MB.
I have looked at KB articles and toyed with the Get-MessageTrackingLog power-shell command, but I don't see how I can limit the output by MBdatabase.
Thank you in advance for any assistance you can provide.
Ken Merrigan