Hi We are running Exchange 2007 SP2 with CCR. Today, we had an issue where the transaction logs were growing very quickly. I was worried we'd run out of space on the drive! Luckily, that stopped and they went back to normal. We ran a full backup and the problem didn't re-occur. In case this happens again, I had some questoins: 1. Is there anyway to check which mailbox is causing the transaction log growth? 2. If the logs do grow and it looks like we're going to run out of space, what's the best thing to do? 3. Does Exchange 2007 have the same checkpoint depth as 2003? And, in particular, this issue - http://support.microsoft.com/kb/905801/en-gb PS: We do run a full backup every night. Today something odd happened where the logs were growing very quickly, so I would like to trace what caused that, hence the questions.

On Tue, 23 Nov 2010 18:16:18 +0000, TomD1976 wrote: > > >Hi We are running Exchange 2007 SP2 with CCR. Today, we had an issue where the transaction logs were growing very quickly. I was worried we'd run out of space on the drive! Luckily, that stopped and they went back to normal. We ran a full backup and the problem didn't re-occur. In case this happens again, I had some questoins: 1. Is there anyway to check which mailbox is causing the transaction log growth? Not quickly. You can examine the log file for strings. You can wade through the message tracking logs. You can see if the SMTP log files on the HT servers are also growing rapidly and, if they are, you may find the sender there. >2. If the logs do grow and it looks like we're going to run out of space, what's the best thing to do? Compress a lot of old log files (not ideal, but it will get you breathing room). Run an incremental backup. Enable circular logging (again, not an ideal solution, but one that'll get you through the crisis). >3. Does Exchange 2007 have the same checkpoint depth as 2003? And, in particular, this issue - http://support.microsoft.com/kb/905801/en-gb The log files in 2007 at 1/5 the size of those in previous releases. The checkpoint depth has been increased by about 5 times to accomodate the larger number of log files: http://support.microsoft.com/kb/925817 > >PS: We do run a full backup every night. Today something odd happened where the logs were growing very quickly, so I would like to trace what caused that, hence the questions. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi Tom, If you want to check which mailbox is causing the transaction log growth, I think the Exchange User Monitor (Exmon) server side will help you. Sort on CPU(%) and look at the top 5 users that are consuming the most amount of CPU inside the Store process. Check the Log Bytes column to verify for this log growth for a potential user. If that does not show a possible user, sort on the Log Bytes column to look for any possible users that could be attributing to the log growth. If it appears that the user in Exmon is a ?, then this is representative of a HUB/Transport related problem generating the logs. Query the message tracking logs using the Message Tracking Log tool in the Exchange Management Consoles Toolbox to check for any large message that might be running through the system. Best regards, Serena