Exchange 2007 Log disk Full
What to do if you are almost out of space:
If you Exchange log disk is almost, but not completely, out of space, there’s time to act in a cautious and methodical way. If you can perform a full backup of all the Exchange databases in the storage group, that will purge out the old logs automatically, and free up space. If you cannot perform a full backup of all the databases, and it looks like you are going to run out of space before you can, continue on with the next section.
What to do if you are completely out of space:
If you can perform a full backup of your database, Exchange will purge out all the old logs it no longer needs, which should free up significant space. Of course, you should have been doing that anyway, and if you were, you probably wouldn’t need this article. If you cannot do a full backup, here is what you can do:
Determine the path and name of your database log check file. It will be in the database log directory, and will be named E0x.chk. Open an administrative command prompt, and run this command, filling in the appropriate path to your bin directory and your check file, and changing x to the correct number for your database. pathtobin\eseutil.exe /MK pathtologs\e0x.chk [enter] That will return a value such as Checkpoint (0x35EA,1B33,A4)
That first value, 0x35EA, indicates the oldest log file you will need to recover your database. If your database is E0, then that file is E035EA.log. Take any files older than that one, and move them to another location. Don’t delete them until you are absolutely certain that you have a valid full backup and won’t ever need to restore an older backup. Here’s a tip: they compress really well. In the absolute worst case scenario, compress all the older files in place a few at a time to buy yourself some more time. Don’t try to do them all at once though, as your compression utility may take the last bit of available space while trying to compress all the files. Start with the very oldest, and work your way forward to the last file you need to save for database recovery.