BLOG ������

Exchange 2013/16 - Circular Logging

Problem

Let's be clear about this, the correct way to flush/clear the Exchange logs is to perform a backup of the mailbox database in question, with an 'Exchange aware' piece of backup software. This will clear down the logs properly.

Why Do We Need Logs?

Well I'm glad you asked, if there's a problem, and we lose the database, we can 'play' the log files back into the database to restore any messages that were 'lost' e.g. because you restored from a backup taken at 22:00 hours last night, and it's now 10:00 hours the following morning. The logs let us get the email that came in after the backup had finished. This is why after a successful backup the logs are usually cleared.

Stop Waffling My Servers Down!

OK so you put your log files on a system drive? It's filled up with logs, and taken the server down. Either because you're a doofus, or you are doing an Exchange migration, and now theres a ton of logs, and you didn't follow my Exchange 2016 Migration Walkthrough.

Solution

Luckily I've caught this one early! (There's an Exchange 2012 to 2016 migration going on, hence the large amount of space taken by Exchange log files).

Enable Exchange 2016 / 2013 Circular Logging from EAC

From within the Exchange Admin Center > Servers  > Databases > Select your Mailbox DB > Edit > Maintenance > Enable Circular Logging > Save.

Then you need to restart the 'Microsoft Exchange Information Store' service, (run services.msc).

Enable Exchange 2016 / 2013 Circular Logging from EAC

Run the following commands;

Set-MailboxDatabase {Database-Name} -CircularLoggingEnabled $True
net stop "Microsoft Exchange Information Store"

net start "Microsoft Exchange Information Store"

Note: To disable it again.

Set-MailboxDatabase {Database-Name} -CircularLoggingEnabled $False
net stop "Microsoft Exchange Information Store"

net start "Microsoft Exchange Information Store"

Now things should look a bit tidier.

Don't Forget: Logging is a good thing TURN IT BACK ON!

Post your comment:

Post your comment by Guest :

Verify Code :