HiWe are running Exchange 2007 SP1 in SCC A/P. We have one store per SG.One of our stores' transaction logs were being generated quickly today. Last night's backups worked fine, so no issue there. So someone moved the oldest transaction logs (via explorer) to another drive to ensure the store didn't dismount.Whatever caused the log generation has also stopped, so we are ok in that respect. However, the problem is that if one of the logs that was not moved hasn't been commited yet, we will have problems.Is there anyway to check which logs have been committed on a live store? I know there is eseutil /mk, but that only works when the store is dismounted.Secondly, if I was to run a backup now to flush the logs altogether, would there be an issue because some logs are in one place and the rest in another?Any help appreciated!

hi,please run eseutil /ml [log file] | find /i "lGeneration" i generation show which logs is closed or committedregardsjeevan

Thanks...Can this be carried out on a mounted store, though?

Hi,"I know there is eseutil /mk, but that only works when the store is dismounted."If you run the cmd, eseutil /mk e00.chk, when the store is mounted, is there any error message?As I know , you don't need to dismount the database to run the cmd.By the way, "So someone moved the oldest transaction logs (via explorer) to another drive "It is not a good idea to move the logs to another drive(explorer) or manually remove them.If you really want to do this as there is no enough blank space left, please first run theeseutil /mk e00.chk to check which logs have been committed to the database, then move or delete logs, after that, please make a full backup.Full backup(or system attendant service) cannot purge logs which move to another drive.Frank Wang