Exchange 2010 Circular Logging

If circular logging is enabled how long before logs are flushed and at what limits. Is there a way to set a limit size like anything above 100mb for example?
Who is Participating?
Shibu KuttanConnect With a Mentor Senior Server AdministratorCommented:
There is no way to limit the log file to 100MB.

If you enable circular logging, once the log file is committed to database the log file should be cleared

The recommended way to save the disk space is disable the circular logging and scheduled the Exchange full backup in off business hours. Once the exchange backup is done it will cleared the transition log files.  So you can save the disk space also get the exchange backup.
agonza07Connect With a Mentor Commented:
There doesnt seem to be any options on limiting the size of the log. It sorta makes a reference to keeping one log, which the previous paragraphs states is only 1MB for regular logging, so it might be limited to 1MB, or to how fast the server can commit the transactions.

Although it is not recommend it as a best practice, you can configure Exchange to save disk space by enabling circular logging. Circular logging allows Exchange to overwrite transaction log files after the data that the log files contain has been committed to the database.

In Exchange 2010, circular logging is disabled by default. By enabling it, you reduce drive storage space requirements. However, without a complete set of transaction log files, you can’t recover any data more recent than the last full backup. Therefore, in a normal production environment, circular logging isn’t recommended.

In the standard transaction logging used by Exchange 2010, each database transaction is written to a log file and then to the database. When a log file reaches one megabyte in size, it’s renamed and a new log file is created. Over time, this results in a set of log files. If Exchange stops unexpectedly, you can recover the transactions by replaying the data from these log files into the database. Circular logging overwrites and reuses the first log file after the data it contains has been written to the database.
If i remember correctly, after you've made a full backup of the exchange, it will start purging the transaction logs
Simon Butler (Sembee)ConsultantCommented:
After turning on circular logging, the logs will start to flush out a few minutes later. You will need to dismount and remount the database for the change to take effect. Depending on how many logs there are will depend on how long they take to remove.

Ideally doing a backup of the Exchange database is the best way to reduce the logs.

CiscoAznAuthor Commented:
For Exchange 2010 there's no need to dismount/mount the DB after turning on/off circular logging.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.