Exchange 2013 Old Log Files
Exchange 2013 - I do a nightly backup of my exchange server with a Barracuda Backup device and have been noticing the space growing. Looking at the server I found folders for each of my databases that contain .log files dating back to April. File names resemble E02001BE9A0.log, E02001BE9A1.log, E02001BE9A2.log, etc. the E02.chk file in each folder has today's date on it. All together these old log files take up about 1 TB of data. Can someone tell me what these are? I've tried opening, but it's garbled. Can they be deleted? If so, how? I really need help sorting this out.
Check your backup options. There should be in the specific Exchange part, about deleting the logs AFTER a SUCCESSFUL backup.
transaction logs. never delete manually.
sounds like the backup is not cleaning up the logs once it finishes
sounds like the backup is not cleaning up the logs once it finishes
ASKER
Yeh...I thought the problem was with the Barracuda not deleting the logs after the backup, but I'm getting no assistance there. I just need to get these files deleted now.
To save customers with no backup solutions, I had to delete the logs (you can't blame me for bad work though, I was brought in after the fact, and they had no backup in place and had to get running fast).
If you still have time, you really need to dive into this matter. Clearing logs after a successful backup run, is essential for every average backup program, let alone a major big brand.
Please provide the exact software version (full name, edition, but also exact version nr).
If you still have time, you really need to dive into this matter. Clearing logs after a successful backup run, is essential for every average backup program, let alone a major big brand.
Please provide the exact software version (full name, edition, but also exact version nr).
ASKER
Kimputer - - I agree I need to find out why this is not working, but for now I just need to free up the space because I can't get a backup. I'm running Exchange 2013.
The dirty way to keep Exchange running is then to delete the oldest logfiles, try to keep the files that are made after the last successful backup.
ASKER
can I just delete with File Explorer or do I have to dismount the databases first and then delete?
i would run a windows server backup (vss full, not copy) and that will purge the logs cleanly
that will buy more time to investigate the barracuda issue
again, never delete transaction logs manually
that will buy more time to investigate the barracuda issue
again, never delete transaction logs manually
you cannot simply delete the files, this is not the way to clear space. if you misdelete file you cant open your exchange anymore. Usually after you backup the file will delete by itself. Try to backup one more time. Try to restart your server and try to backup again see can or not.
Just enable circular logging, that would clear up log files, without any manual intervention. Once logs are cleared, disable circular logging and take full backup and continue with full backup everyday.
ASKER
Update - I started a windows server backup, but do not have a drive I can plug into the server. Doing the backup across the network to a nas. Backup has been running for 3 days. Waiting to let it finish to see if it cleans up the log files. Will report back with results.
ASKER
Update - windows server backup (vss full, not copy) completed last night and did not delete E??????.log files dating back to April. Now, what would the experts advise to do?
after you backup the drive still full?
Did you read and tried my solution?
ASKER
Amit - I have not because I was intimidated by enabling the circular logging. I've read more about now and will try this tonight.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Amit - THANK YOU THANK YOU THANK YOU. This was the solution. I also followed along with https://www.petenetlive.com/KB/Article/0001224. Got everything cleaned up. I'm now going back to the Barracuda Backup this weekend and see how it goes. Again, thanks for your help and patience.
Glad to help you.