We had a problem where tons of exchange 2007 transaction log files were being created thus filling up the drive hosting these logs. I was tempted to just double clicking on a few of the log files but was not sure if that would or could make matters worse. What would be the safest way to view these files on the fly? Could I copy a few to say \temp and open them there?

You can't view it, if you open it you will see codes and all weird latters in the notepad... The issue you have is growing log files, how long its been happening? Database file is also growing or just log files. You need to troubleshoot growing Log File issue.... Gulab | MCITP: Exchange 2010-2007 | Lync Server 2010 | Windows Server 2008 | Skype: Exchange.Ranger | Blog: www.ExchangeRanger.Blogspot.com

Could I copy a few to say \temp and open them there? Opening a transaction log won't provide very useful information for human eyes. I've tried for fun (in practice environment) and it's just gibberish. You can't read email that way, or see if there is any important information you need to save. Transaction logs filling up a drive usually happens when you do not perform backups, in particular a backup that truncates the logs whose data is committed (entered) into the database. What are you doing to back up your mail server? How are you backing it up?

You can view word patterns in the logs if you are troubleshooting: http://blogs.technet.com/b/mikelag/archive/2009/07/12/troubleshooting-store-log-database-growth-issues.aspx Troubleshooting Exchange 2007 Store Log/Database growth issues

We use Backup exec 2010 R2. The backups are running fine and when they run the transaction logs are being committed afterwards, as they should be. For this storage group the logfile location was the local C: of the exchange server - I know Bad thing - this is now corrected. What happened was that the night before the backup ran, committed all the logs correctly and then this event began; during the evening it used up all the available space on the C: and in the morning No Emial. We freed up 10GB by deleting old IIS logs to get email working again. Using windows explorer, I navigated to the directory on C that hosts the log files for this particular storage group and the items count was incrementing at an alarming rate. This was the point that I wanted to see what was accounting for all these logs. What should I have done? Besides the obvious - not having an exhange log file on the C:. Last night I move them off of the C.

We use Backup exec 2010 R2. The backups are running fine and when they run the transaction logs are being committed afterwards, as they should be. For this storage group the logfile location was the local C: of the exchange server - I know Bad thing - this is now corrected. What happened was that the night before the backup ran, committed all the logs correctly and then this event began; during the evening it used up all the available space on the C: and in the morning No Emial. We freed up 10GB by deleting old IIS logs to get email working again. Using windows explorer, I navigated to the directory on C that hosts the log files for this particular storage group and the items count was incrementing at an alarming rate. This was the point that I wanted to see what was accounting for all these logs. What should I have done? Besides the obvious - not having an exhange log file on the C:. Last night I move them off of the C. I would check the link I posted earlier if this happens again: http://blogs.technet.com/b/mikelag/archive/2009/07/12/troubleshooting-store-log-database-growth-issues.aspx You could also use the Process Tracking Log tool: http://blogs.technet.com/b/exchange/archive/2011/10/21/updated-process-tracking-log-ptl-tool-for-use-with-exchange-2007-and-exchange-2010.aspx My first step is always to throw on Exmon and see if a mapi client is hitting the server hard. http://www.microsoft.com/download/en/details.aspx?id=11461

Please find below link for your reference http://support.microsoft.com/kb/959559 Backup your exchange database with windows backup to flush the logs

We use Backup exec 2010 R2. The backups are running fine and when they run the transaction logs are being committed afterwards, as they should be. For this storage group the logfile location was the local C: of the exchange server - I know Bad thing - this is now corrected. What happened was that the night before the backup ran, committed all the logs correctly and then this event began; during the evening it used up all the available space on the C: and in the morning No Emial. We freed up 10GB by deleting old IIS logs to get email working again. Using windows explorer, I navigated to the directory on C that hosts the log files for this particular storage group and the items count was incrementing at an alarming rate. This was the point that I wanted to see what was accounting for all these logs. What should I have done? Besides the obvious - not having an exhange log file on the C:. Last night I move them off of the C. I would check the link I posted earlier if this happens again: http://blogs.technet.com/b/mikelag/archive/2009/07/12/troubleshooting-store-log-database-growth-issues.aspx You could also use the Process Tracking Log tool: http://blogs.technet.com/b/exchange/archive/2011/10/21/updated-process-tracking-log-ptl-tool-for-use-with-exchange-2007-and-exchange-2010.aspx My first step is always to throw on Exmon and see if a mapi client is hitting the server hard. http://www.microsoft.com/download/en/details.aspx?id=11461

Please find below link for your reference http://support.microsoft.com/kb/959559 Backup your exchange database with windows backup to flush the logs

Hi, Some points for your reference: 1 Parse the transaction logs and find whether there're users which are causing the issue for transaction to grow. 2 Move mailboxes to another store , renew the DB file and move mailboxes back. 3 Upgrade your Exchange 2007 to the latest SP and RU. Thanks. Rowen TechNet Community Support

Hi, Any update?Rowen TechNet Community Support