locked
How to prevent Exchange 2000/2003/2007 transaction logs from completely filling up the disk. RRS feed

  • General discussion

  • Exchange logs should always be cleared through the recommended procedure of performing a full, Exchange-aware backup.  However, if backups fail to clear the logs or other circumstances cause an accumulation of log files to the extent that it fills the disk partition, Exchange service can no longer function and Exchange Stores will dismount.  In this scenario, it is sometimes difficult to bring the stores back online, as log files should never be removed manually.

     

    To prevent this problem the following procedure is recommended.  For this procedure you must have access to a Microsoft SQL server.

     

    Using a Microsoft SQL Server create a new database called "ExchangeBufferFile" with an initial file size of 1GB.  Detach the database, then locate the database file and copy the ExchangeBufferFile.mdf to the Exchange Server's transaction log partition.  Once the file is there, delete the database from the SQL server.  This will remove the database from the SQL administration tool view, as well as remove the data file and related logs from the SQL server.

     

    In the above scenario, where the log partition fills up completely and shuts down Exchange services, you can delete the Exchange Buffer File and mount the stores to restore service for the end-users.  This will also provide additional time to clear Exchange logs through recommended practices as needed.

    Friday, March 13, 2009 4:24 PM

All replies

  • Please do some fact checks before you lead others in the wrong direction.

    As I mentioned on your other IDENTICAL post(s):

    Haha, this is an "interesting" approach!  I suppose along these lines, an even easier approach would be to copy the Exchange installation directory into the log folder and then simply delete it when you get to capacity!

    Seriously though, this is much more intelligently accomplished by deleting the committed log files manually, which CAN be done safely as described here:

    How to remove Exchange Server transaction log files (2000/2003)
    http://support.microsoft.com/kb/240145

    Insufficient Free Space Remaining on Transaction Log Drive (2007)
    http://technet.microsoft.com/en-us/library/bb219028.aspx

     




    Mike Crowley: MCT, MCSE, MCTS, MCITP: Enterprise Administrator / Messaging Administrator
    Sunday, March 15, 2009 12:05 AM
  • This all boils down to the fact that a sucessful backup whether is be using NTBackup or a 3rd party backup should be committing the transactions logs.  If you are getting a sucessful backup and this is not occurring, then there's another issue going on.  If you are just going to ignore the building transaction logs then you might as well enable circular logging which would solve the problem without having to do any custom scripts.
    Tuesday, March 17, 2009 3:11 PM
  • Well said.
    Wednesday, March 18, 2009 1:07 PM