It's always best to monitor your drive space as you manage your Exchange server. But there are those times, when you come into a situation where you are out of drive space.
A great resource for information regarding full Exchange log drives can be found here.
But to give you a quick snippet from this article that I have used, along with a backstory:
There have been times in the past where our backup system has run into some issues causing backups of our Exchange 2007 environment to fail. This has subsequently lead to our logs drives to fill up all of the space on the drive.
Typically you have a few solutions in this case:
- Running a backup, either through NTBackup / Windows Server Backup or whatever 3rd party
- Turning on circular logging
- Manually truncating the logs
But in certain cases when a full backup will take too long, you're left with the more drastic options.
In my case, manual log truncation.
-----------------------------------------------
And to do that, I followed these rough steps:
- Determine Which Logs are Committed
- Running eseutil /mk <path to .chk file>
- Typically this file is located in your storage group folder
- The information adjacent to Checkpoint will be the last log that has been committed
- Navigate to the folder containing the logs
- Inside here, you will find the log file matching the hex value you found above
- Move any logs prior to that
- Since all the logs prior to that point have been committed to the database, you can move or delete them BUT make note of the following points before you do
- Deleting those logs will remove your ability to restore you Exchange database to a particular point in time
- With that in mind, it's best to move those logs to a drive that has more space (even an external would be better than deleting them)
 |
| Returned from eseutil |
No comments:
Post a Comment