Circular Logging in Disaster Recovery

Best Practice (Litmus Test)

Professionals:  Think of disaster recovery, they disable circular logging 99% of the time

Amateurs: Think Circular Logging is best practice for database logs

Why is Circular Logging not best practice?

During disaster recovery, if you have over-written the transaction logs then you can only restore as far as the last backup.  When all the logs are available, Exchange automatically replays the logs and recovers all the transactions.

What is Circular Logging?

Exchange, SQL and Active Directory databases all rely on transaction or write-ahead logs.  Events can be quickly written to the logs, then later 'committed' to the main database file.  Circular logging over-writes these transaction logs to save disk space.

How Transaction Logging Works

When a new piece of mail arrives, a transaction is written to the log.  If the server is busy there will be a delay before the information is committed to the main EDB database file.  A separate pointer called a checkpoint file maintains a record of how much of the log has been written into the EDB database.

Disaster Recovery of Exchange Stores

Each Exchange Storage Group has one log for up to five individual stores.  The best practice of having multiple stores is to reduce the time needed to restore in disaster recovery conditions.

When disaster strikes and you have to restore an exchange store you need a full backup of the EDB database and all the logs since the the last backup.  So if you allow circular logging to over-write some of the logs, then you lose all data since the last backup.  However, if you disable circular logging, then you Exchange magically replays all the logs and brings back the Exchange store to how it was before the disaster.  This re-reading the logs is called a hard recovery and happens automatically.

Where do you check the circular logging setting?

1. Open the Exchange Administrator, double-click Servers.
2. Select the server which has the storage group you want to enable circular logging.
3. Right-click the storage group, and then click Properties.
4. On the General tab, click Enable circular logging, and then click Yes.

Why does such a potentially harmful setting exist?

The one time you may need circular logging is if your disk is full.  When you first install a database you always think 'no way will the disk ever get full' - experience teaches it will!

Another of Guy's Litmus Tests - Performance Monitoring

Professionals install ipMonitor (40% off until Sept 26th)
Consequently they can see instantly which servers are short of resources, and which are running smoothly.  

Amateurs
Keep their fingers crossed that the servers have enough memory and disk space.

Free Download of SolarWinds ipMonitor

Sign up to my new Ezine and get a free Best Practice ebook. 

 *