Exchange logs, checkpoint file and moving logs
Hello All We are running Exchange 2007 (CCR) on Windows 2008 Server. The other day, we experienced an issue where we almost ran out of space on one of our log drives. We had to carry out a dismount, move the logs via Ex Management Console to a another location, and then remount. This raises some questions for us...based on the article here: http://www.msexchange.org/articles/Exchange-log-disk-full.html Questions: 1. Let's say we encounter the same problem again. We're not sure if a backup will finish before the space runs out. Is there any way to find out which logs have been commited and which not? The article mentions running ESEUtil /mk to interrogate the CHK file, however this can only be done when the DB is down, correct? 2. If we do dismount the store and run /mk, I'm still confused as to how we know which files have been commited and which not (the article doesn't really go into that!). Example, on my test machine, I have dismounted the store and the value is: Checkpoint: (0x53, 8, 16). I understand that I'm only interested in the 0x53, but how do I convert this into a log file? And is it anything before (and including) that log file I can move? 3. When Exchange dismounts a store gracefully, aren't ALL log files for that store commited(assuming 1:1 relationship between store and SG)? In which case, we could move all the log files? 4. Would failing over to the passive CCR node help at all? Thanks for any help!
December 30th, 2010 2:13pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics