Exchange 2013 database logs going large
Exchange 2013 server running on 2012r2 server. Previouslly we had a Veeam replication job that would remove the database logs during the backup but we are in the process of re-doing our DR and the replication job hasnt been running for a while. Our logs have grown very large. What is the best way to manually remove these logs without causing issues? location of logs is c:\program files\microsoft\exchange server\mailbox\mailbox database 1640xxxxx
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
can you please take a screen shot of the offending logs folder after you sort by date? You should see the file E0000CBD7E. If you do, feel free to delete E0000CBD7D and lower.
ASKER
I looked for that file and its not in there, I also did a search of the directory and I got no matching names found.
can you please post a screenshot of your logs directory?
ASKER
Its attached
exchange-SS-.rtf
exchange-SS-.rtf
Thanks for the screenshot, it looks like you are in the right folder, I thought the 8 was actually a B. please run the esentutl.exe /mk command again(like requested above). It should have a new checkpoint file listed. Search for that checkpoint file in the directory you just posted a screenshot of. Do not delete that file, just delete all the E00 log files below it.(I.E. the ones takes before it.).
The file listed under the "Checkpoint" simply shows the latest logs to be committed, so everything prior to that can safely be delted. Its the same thing any backup program does after it finishes a backup.
The file listed under the "Checkpoint" simply shows the latest logs to be committed, so everything prior to that can safely be delted. Its the same thing any backup program does after it finishes a backup.
ASKER
Its attached. How can I format the output of checkpoint so it matches a file name?
exchange-output.rtf
exchange-output.rtf
That is odd. Are you in a DAG environment? Is there more than 1 exchange server? The quickest way for you to get space immediately is just to turn on circular logging for now. If you are in imminent danger of running out of space, I would consider this option before anything else. Once you get everything you need to get done, you can turn it off and go back to your normal backup routine.
When circular logging is enabled, Exchange writes transaction logs as usual, but when a checkpoint file is advanced, the inactive portion of the transaction log is truncated. This is why you need to turn it off once you go back to your normal backup schedule.
When circular logging is enabled, Exchange writes transaction logs as usual, but when a checkpoint file is advanced, the inactive portion of the transaction log is truncated. This is why you need to turn it off once you go back to your normal backup schedule.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I ended up just running a replication job with Veeam and that took care of the logs.
ASKER
I attached a screen shot
exchange-screen-shot.rtf