This article explains how to check the committed transaction logs in exchange server. The disk space management is more important, since the transaction logs get accumulated in faster phase. Sometimes, the committed logs may not be recycled after taking the backups. The committed transaction logs are no need any more in such cases, just only occupies some disk space. Here we are going to check how to find the committed transaction logs using the eseutil.
In Exchange, there will be a checkpoint file for each storage group and one for the directory. The checkpoint file is a file of special note which plays a big role in keeping your exchange server database in order. The checkpoint file (edb.chk) tracks which entries in the transaction log files have already been recorded in the database, and thus which ones will need to be replayed during a restoration situation. The checkpoint file thus speeds up recovery by telling the ESE-Extensible Search Engine exactly which log file entries need to be replayed and which do not-thus preventing extra writing during the restoration process. So what is ESE, here we go, The Extensible Storage Engine (ESE) is a low-level database engine that is used internally by Windows for all sorts of things like Microsoft Exchange message store, Active Directory database, Microsoft Updates, Local Security Policy, etc.
When you try to identify the last committed log file for a storage group, note that the storage group prefix applies to the checkpoint file and to all of the log files. For example, the default first storage group's checkpoint file name is E00.chk, and its log files are E00xxxxxx.log (where xxxxx is the hexadecimal sequence number of the log file).
To check the status/details of the checkpoint file
eseutil /mk “the full path to the checkpoint file”
eseutil /mk "C:\Program Files\Exchsrvr\MDBDATA\E00.chk"
Microsoft(R) Exchange Server(TM) Database Utilities
Copyright (C) Microsoft Corporation 1991-2000. All Rights Reserved.
Initiating FILE DUMP mode...
Checkpoint file: C:\Program Files\Exchsrvr\MDBDATA\E00.chk
FullBackup time: 00/00/1900 00:00:00
IncBackup time: 00/00/1900 00:00:00
Signature: Create time:09/24/2001 17:10:26 Rand:522553071 Computer:
( off, 202, 30300, 1365, 10100, 128, 10240, 97940)
Operation completed successfully in 1.192 seconds.
In the above sample output, please find the checkpoint details (marked in bold red),
Checkpoint: (0x6A,1119,3D) – it means 0x6A = E000006A.log is the last committed log file, the logs sequentially above this value is committed to the database already.
Hope the above information will helps you in checking the committed logs and also in managing the disk space management.