Checkpoint files store information that indicates when a transaction is successfully saved to the database files on the hard disk. A checkpoint file is maintained for the series of log files within each storage group. Separate Enn.chk files (where nn refers to the log file prefix for the storage group) point to the oldest log file that has all transactions successfully committed to the database.

Exchange 2000 uses checkpoint files to allow an instance of ESE to automatically replay log files into an inconsistent database during soft recovery, starting with the next unwritten transaction. However, if the checkpoint file is missing or damaged, the soft recovery still occurs; the process simply takes much longer because the ESE has to begin with the first log file it finds and replay all transactions.

The information in this article applies to:

• Microsoft Exchange Server 2003 Enterprise Edition
• Microsoft Exchange Server 2003 Standard Edition
• Microsoft Windows Small Business Server 2003, Premium Edition
• Microsoft Windows Small Business Server 2003, Standard Edition
• Microsoft Exchange 2000 Server