We have a 2-node DAG setup in our lab environment. We don't backup our lab environment, so our log files have been accumulating for several months now. I just enabled circular logging on all of the mailbox databases, but the logs have yet to delete themselves. I've tried dismounting and remounting the stores, activating different copies, etc., but I still have tons of log files going all of the way back to December. What can I do to trigger a cleanup of these log files? They have to have been written to the database by now.

Hi Charles, Can you confirm all DB copy's are in healthy state. You can remove logs manually also since you dismounted databse but It can be last action. Any evet log you can seein eventviwer.Anil MCC 2011,ITIL V3,MCSA 2003,MCTS 2010, My Blog : http://messagingschool.wordpress.com

Give it some time to allow for some log generation. How long did you wait? Try sending a message larger than 1MB if nothing happens after awhile.

Apears like some log files are still in use. ( got stucked ) Is it possible for you to move all the logs of one database to another drive. The file which is in use will wont alow you to move. To overcome this you have to manually move all the mailbox database from one server to mount on different server and check for the issue. If no Luck Few steps where you can run without any problem 1. disable the circular login option for all the databases 2. Activate All the Database on first DAG Member using Move-ActiveMailboxDatabase -Server "Second DAG Member" -ActivateOnServer "First DAG Member" -MountDialOverride "None" | Sort_object -Property name | ogv 3. Make sure all the Databases are active on first member server using Get-MailboxDatabasCopyStatus -Server "First DAG Member" | where{$._status -eq mounted} | Measure-Object 4. Check whether the replication health is normal using Get-MailboxDatabaseCopyStatus -Server "First DAG Member" Get-MailboxDatabaseCopyStatus -Server "Second DAG Member" If any problem you have to go for reseeding for example "Get-MailboxDatabasCopyStatus -Server "First DAG Member" | where{$._MailboxDatabaseCopyStatus -eq failed} | Update-MailboxDatabaseCopy" 5. Check whether Content Index State in normal using Get-MailboxDatabasCopyStatus -Server "First DAG Member" | where{$._ContentIndexState -eq failed} | Sort Name | ogv Get-MailboxDatabasCopyStatus -Server "Second DAG Member" | where{$._ContentIndexState -eq failed} | Sort Name | ogv 6. If any problem with the contend index state, Update it using Get-MailboxDatabasCopyStatus -Server "First DAG Member" | where{$._ContentIndexState -eq failed} | Update-MailboxDatabaseCopy -CatalogOnly Get-MailboxDatabasCopyStatus -Server "Second DAG Member" | where{$._ContentIndexState -eq failed} | Update-MailboxDatabaseCopy -CatalogOnly If everything is normal now, Run a Service health check using Test-ServiceHealth -Server "Server Name" Now Enable the circular Login option for Single Database and check it. Still if you have issue, for a first time take a backup using exchange application aware backup utility to purge the bulk logs once and enable circular login. Inform if you are facing any issue