Read time 4 minutes
In Exchange Server, Circular logging is not enabled by default. Circular logging is a mechanism in which the Exchange Server automatically overwrites individual transaction log files once their data has been successfully committed to the database. This proactive approach prevents the transaction log files from continuously growing, effectively conserving valuable hard disk space.
The term “circular” refers to the practice of deleting log files on a rotating basis when the disk space limit is reached, following a Last-In, First-Out (LIFO) queue approach. Circular logging is a constituent of JET (Joint Engine Technology). All the versions of Exchange Server use it, and one can enable or disable this component through admin.
Enable circular logging in Exchange 2010 using Exchange Management Console with the few steps below.
For Exchange 2010, you can enable Circular logging by executing the following command:
Note: To make the changes to circular logging settings effective, perform any of two – Restart the Microsoft Exchange Information Storage Service, or Dismount and mount the databases.
You can also use the alternate command mentioned below to perform the action for all databases.
You may encounter a condition where database storage space is filling up continuously. Once you reach a certain threshold point of storage, there could be a failure in mounting the Exchange Database. Now, before you enable circular logging to free up space in your database, you must make a copy of the log and database. This must be done to have a backup of the database and to replay the logs again when required.
When you employ Exchange Server with VSS ( Windows Volume Shadow Copy Service) backup infrastructure having circular logging enabled, remember that you need to disable circular logging before the next backup. If you fail to do so, you won’t be able to take full or incremental backup.
If you have it enabled during the incremental backup, the log files that are needed are truncated as the previous backup is not available. So, the intended backup will fail. Therefore, when you want to perform VSS backups, turn circular logging off.
In the event of data loss, there exist several viable solutions for recovering Exchange Server data. Among these, it stands out as a top-tier choice for repairing corrupt Exchange database files, with the added advantage of not needing log files for the recovery process. Additionally, an EDB to PST converter can efficiently extract data from Exchange backup files, offering another effective avenue for data retrieval.
When you enable circular logging in Exchange 2010, you free up disk space for users. This space provides more storage to keep your data on the Exchange Server. However, circular logging is a manual data management strategy.
Here, we provided you with the techniques to enable circular logging with the issues that you can face while enabling it. If for any reason, you can’t dismount or re-mount the database, use Kernel for Exchange Server. This tool allows you to recover, repair and restore your Exchange mailboxes and database.