Exchange 2013 circular logging question
Hello,
We need to do a number of large mailbox moves and we are cautious of our log file location filling up between backup/truncation.
Can we enable circular logging on our databases (all of which are DAG protected) If so is there anything we need to be aware of before we do this?
We need to do a number of large mailbox moves and we are cautious of our log file location filling up between backup/truncation.
Can we enable circular logging on our databases (all of which are DAG protected) If so is there anything we need to be aware of before we do this?
cwstad2
One thing to take into account. To enable circular logging you will need to dismount and then re mount each database
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Perfect thanks
There is no need worrying about taking a full backup immediately after disabling circular logging if you have 4 database copies. There are enough copies for activation in case of failure. Exchange 2010 and 2013 uses CRCS or continuous replication circular logging in a DAG which runs of the replication service instead of traditional circular logging which worked off the JET database engine. If you have no database copies, it would default to tradition JET logging, requiring a db dismount remount. You do not need to worry about incremental backup, one full backup a week is fine. Microsoft fully supports a 4 db copy DAG with CL enabled. We have it set in production in a Exchange 2010 organization. Most admins do not know the difference between traditional vs CRCL as pretty evident in this post. Just use it and there is no need to worry about anything if you have enough db copies. Disable it when the mailboxes have moved.