Hi,

I tryed to enable Circular Loggin on Exchange 2010 SP3 with DAG, but is not as expected.

We tested:

* Enable Circular logging on database

* Dismounted active database

* Suspended and resumed the database copy

* Restarted the Information Store service

But the logs are still growing, we are trying to enable it to save disk space.

I will appreciate any advice to enable the Circular Logging on DAG Databases.

Best regards,

Try to use "Set-MailboxDatabase" cmdlet with "CircularLoggingEnabled" parameter set to $True and give us an output.

• Edited by Slava Fedenko 15 hours 53 minutes ago

In DAG you don't need to dismount/suspend/restart, it will take effect almost immidiately.

When you say log is still growing, did you check whether the old logs are deleted?

Another point to check, do you have lagged DB copy?

Thanks Slava.

I checked all Databases and the paramater "CircularLoggingEnabled" is configured $True already.

Best regards,

Manuel

Hello Li,

Before I created the database copy Circular Logging was selected and the old logs were deleted, on the databse folder I had only 22 files.

When I created the database copy, I removed Circular Logging and reactivated after copy ends, now I have 210 files on the folder and are increasing.

I think that Lagged DB copy is not activated, I ran the command Get-MailboxDatabase -Identity MailboxDatabase01 -Status | Format-List and I get this information:

* ReplayLagTimes: 00:00:00 (in both DAG servers)

* TruncationLagTimes: 00:00:00 (in both DAG servers)

Do I need chage this parameters?

I will appreciate any advice.

Best regards,

Manuel

It is regarding DAG -https://technet.microsoft.com/en-us/library/dd335158(v=exchg.150).aspx - Using replay lag and truncation lag options

Try to use "Set-MailboxDatabase" cmdlet with "CircularLoggingEnabled" parameter set to $True and give us an output.

• Edited by Slava Fedenko Friday, July 24, 2015 3:35 PM

Try to use "Set-MailboxDatabase" cmdlet with "CircularLoggingEnabled" parameter set to $True and give us an output.

• Edited by Slava Fedenko Friday, July 24, 2015 3:35 PM

Hi Manuel,

In a DAG we don't need to restart anything after enabling circular logging as mentioned above, the existing logs should start truncating after a minute or two.

After it enabled, Exchange will still write to the log volume but the new logs will be truncated as soon as it the data has been written to all database copies in the DAG. If the issue persists, it might be caused that the log files are not able to be copied to all nodes, so circular logging or not, logs won't be deleted.

Thanks

BTW looks like no one mentioned that using circular logging with DAG is not recommended practice.

Hello 

Please check with below command if all the copies are healthy and shipping to passive copies.

Get-mailboxDatabaseCopyStatus

also check the content index state status.

try to remove passive copies and then enable circular logging again to verify the issue.