Exchange 2010 Transaction Logs

Posted on 2011-02-18
Last Modified: 2012-06-27
I am trying to understand Exchange 2010 transaction logs as explained On the link above.
I can't understand some terminology such as:
write-ahead transaction logs
checkpoint files
the in-memory database  Versus the on-disk database
write-ahead logging.
page-based writes and checkpoints.

I also want to confirm whether it s true that neither the incremental nor the differential back up of exchange clears up the log files and checkpoint files except for the Full back.

Question by:jskfan
LVL 29

Accepted Solution

mass2612 earned 500 total points
ID: 34924664

Ok the transaction log can be complicated however some consider it more important than the database file so its good to have a good understanding of it. Write ahead transaction logs and write ahead logging are pretty much the same thing.

One of the first things to remember with databases including Exchange is that data is not modified on the disk. The data is written to memory and modified and then the modified data needs to be committed (written back to the disk). Many databases including Exchange write the modified data to a transaction log first for resiliency and recoverability. Therefore when Exchange updates data and the data needs to then be written back to the database the entry is first written to the transaction log before then being written finally to the database. When you look inside a transaction log you see a list of entries such as begin transaction, insert, update, delete, end transaction.

The checkpoint file keeps track of the relation between the log files and the database.

In memory database or the DB cache is basically pages from the database that are currently being stored in memory. If the data in the in memory page is different to the data in the database on the disk then the page is considered dirty. This just means that the data has been changed and is different than what's on the disk. If the page in memory has not been changed then the page is clean. When an application needs to modify data in a database it must read the data into memory and then change the data in memory. Finally that changed data must be written to disk. The on disk database is the data in the EDB files on the disk.

A page is the smallest unit of data in Exchange and in Exchange 2010 its 32kb.

A full and an incremental backup purges the transaction logs however a differential backup does not purge the transaction logs.

Incremental backups

Differential backups


Author Closing Comment

ID: 34950149
Thanks for your explanation

Join & Write a Comment

In this article, we will see the basic design consideration while designing a Multi-tenant web application in a simple manner. Though, many frameworks are available in the market to develop a multi - tenant application, but do they provide data, cod…
Local Continuous Replication is a cost effective and quick way of backing up Exchange server data. The following article describes the steps required to configure Local Continuous Replication. Also, the article tells you how to restore from a backup…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…

760 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

20 Experts available now in Live!

Get 1:1 Help Now