Exchange Log Files

We are running Exchange 2010, with a suite of GFI applications for Security and Archiving.  We  have been monitoring our Archives and in doing so we have found that our Log files are getting out of hand.  I do not think that these are associated with GFI, and are coming from the Exchange Server.

We have a directory on our "Mail" location called Logs.  It is almost 1TB in size, while our mail archive for the last three years is sitting at 207GB.  When I browse to look at the files in the Logs folder, there are thousands of sequential files, E01000CA970.log, E01000CA971.log, E01000CA972.log, etc  

To get an idea of what these are, I opened one with notepad.  It was the equivalent of opening a jpg with notepad. . . just garbage.  There are a few other files in there though, which leads me to believe that they are Exchange logs.  There are a few .jrs files and one .chk file.  Any ideas?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Will SzymkowskiSenior Solution ArchitectCommented:
Have you checked your the timestamp for these logs? Also, are you doing Full Backup's of these log files? If you are performing Full Backups they should be purged after a Full backup has completed sucessfully.

I would check your Database Log directory in Exchange and see if one of them are pointing to this locaiton.

By the look of the log file name it is Exchange Logs.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Yes, they are Exchange logs, the numbers being that high would indicate that they aren't being flushed though. And the size of course.

You will likely find that they are all the same size (1MB) by default but that there a large number of them.

The transaction logs record every operation on the database (including deletions) but are designed to be flushed once a backup job completes (the idea being that a successful backup will mean you no longer need the transactions to repair the database).

If they are as numerous and as large as you say I would recommend you start your search at your backup system and ensure a) it is actually running properly and b) that it is set to flush the logs on completion.

If that is all in place and you genuinely are generating that many logs between backups you can consider circular logging, but that will break other things like DAGs or replication.
Nick RhodeIT DirectorCommented:
Logs are transactions happening in exchange server.  Typically when a full backup is done on the exchange server these are cleared (flushed out).  If you wanted to flush them you could do a backup of the exchange using windows backup utility.  When was the last full backup taken?  If they are not being purged there is an issue somewhere.  Check the overall health of the exchange server using the utilities in the EMC toolbox
jfdprattAuthor Commented:
I have ran a Health check on the Server from the EMC and there were a few critical issues, but nothing that will cause issues.  They are small things that are left over from the migration that was done before I started to work here.

I did talk to the individual in charge of all of our backups.  Apparently he was looking at things since he wasn't able to get Symantec Backup Exec to work, and was doing Windows Server Backups in the meantime.  The last time he did one was the same day that all of the 1M files in our Logs folder were created.

It looks like it was related to what btassure had to say.  We are going to run a backup tonight and check the logs again tomorrow.  I will report my findings here.
Any idea what the BackupExec issues were?

Either way, there are a few tips for Windows Backup + Exchange 2010 here:

Notably, you need a FULL VSS not a COPY! or it won't clear the logs.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.