Exchange 2010 Logs taking up too much space

We've put an Exchange 2010 server at a client site, and for some reason one of the log folders keeps filling up and hasn't been cleared out since it was installed in March. Its wasting 166GB of space.

I am having a difficult time locating where the path is for this log folder and how to set it to delete the files after 30 days.
Who is Participating?
Alan HardistyConnect With a Mentor Co-OwnerCommented:
As suggested above - this sounds very much like you haven't backed up Exchange since it was installed.
If you use the in-built software to backup the server, the logs should get purged automatically and then you will have your space back and won't suffer from backpressure which will kick in if space gets tight.
Useful reading: 
Gary DewrellSenior Network AdministratorCommented:
Open Exchange Management Console.
Drill down to Organization Configuration , Mailbox.
Look in the right window and you will see the database path and log file path.
If you are doing regular backups your logs should be taking care of themselves.
Are you backing up?
there are several logs to consider and all the following found using the Get-TransportServer cmdlet

you can update these settings using the Set-TransportServer cmdlet

Set-TransportServer ex2010 -MessageTrackingLogMaxAge 7 MessageTrackingLogMaxDirectorySize 2GB
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

there are also some for Get-MailboxServer
These logs will be the database transaction logs rather than diagnostic logs
(The diag. logs have quite small default size limits ~250MB)

If you delete transaction logs your mailstore will break.
Best option is to employ a backup solution that understands database/exchange transaction logs, once logs are marked as backed up exchange will clear them down.

Otherwise, if you're not bothered about restoring backups with the ability to roll-forward to the point of failure you can enable circular logging on the storage group - this allows the log files to overwrite themselves; the downside being that in the event of failure your data will only be as recent as your last backup.
i only mention the other logs since the first comment covered the database logs and asked about backups
ITD_TechnicianAuthor Commented:
We're using Backup Exec 2010 for our backup solution, and admittedly there are problems with it right now I am trying to work out.

CGretski - How do you enable circular logging. Our backup solution should do a full backup every friday and daily diffs every day once this is working properly.
Gary DewrellSenior Network AdministratorCommented:
Once you have your full backups working your problem should go away.
Alan HardistyCo-OwnerCommented:
I would not enable circular logging.  Backup your server using the article I provided and then you will be fine.
Circular logging will prevent you doing incremental/differential backups.
You're limited to full backups/restores.

Backup exec (with the exchange agent) will mark the transaction logs so exchange can clear them down without enabling circular logging.

Instructions to enable cirular logging here:

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.