Configure circular logging for a mailbox database
Applies to: Exchange Server 2013
When you enable circular logging for a mailbox database, the type of circular logging you get depends on whether or not the mailbox database is replicated using continuous replication:
If the mailbox database is not replicated, it will use JET circular logging. In this case, enabling or disabling JET circular logging will require a dismount and mount of the database.
If the mailbox database is replicated, it will use continuous replication circular logging (CRCL). In this case, enabling or disabling CRCL takes effect dynamically; there is no need to dismount and re-mount the database.
For more information about circular logging and CRCL, see Exchange Native Data Protection.
What do you need to know before you begin?
Estimated time to complete: 1 minute
You need to be assigned permissions before you can perform this procedure or procedures. To see what permissions you need, see the "Mailbox Database Permissions" entry in the Recipients Permissions topic.
Use the EAC to configure circular logging for a database
In the EAC, go to Servers > databases.
Select the mailbox database you want to configure and click .
Check or uncheck the Enable circular logging checkbox, and then click save.
If a dismount and mount operation are required, a warning message will appear. Click OK to close the warning message.
To dismount the database, click More , and then click Dismount. Click yes when the warning message appears.
To mount the database, click More , and then click Mount. Click yes when the warning message appears.
Use the Shell to configure circular logging for a database
This example enables circular logging for database DB1.
Set-MailboxDatabase DB1 -CircularLoggingEnabled $True
This example disables circular logging for database DB1.
Set-MailboxDatabase DB1 -CircularLoggingEnabled $False
See Set-MailboxDatabase for other mailbox database parameters you can configure.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.