• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 632
  • Last Modified:

Exchange 2010 Log Files

The Exchange Server 2010 disk space is filling up and I noticed almost 70GB worth of log files in C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database.  The database file itself is only 75GB and it doesn't seem that the log files should be the same size as the database.  Is the truncation not working properly?  What do I need to do to truncate these logs?  I assume I can't just delete them by hand?
1 Solution
Seth SimmonsSr. Systems AdministratorCommented:
you need an exchange-aware backup product which will clear the logs
we have used backup exec with the exchange agent and works just fine
don't delete manually
fallriverelectricAuthor Commented:
Ok I was just starting to think that was the issue because the logs start around the time we switched backup solutions.  We used to use CA ArcServe and it took care of this, but we are now using Dell vRanger and it apparently does not.  Is there any other way to handle this?
Seth SimmonsSr. Systems AdministratorCommented:
vranger is for vmware
sounds like that is taking care of the virtual machine itself but still need something to handle exchange specifically

you could enable circular logging though not recommended for recovery reasons
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

You need to enable Circular Logging on the exchange server, this is done through the exchange management console.
Mohammed TahirCommented:
My suggestion is instead of enabling circular loggin on exchange databse use Exchange aware backup software to backup exchange database because  by enabling circular logging, you reduce drive storage space requirements. However, without a complete set of transaction log files, you cannot recover any data more recent than the last full backup. Therefore, in a normal production environment, circular logging is not recommended.

Muralidharan RAssociate ConsultantCommented:
Enabling circular logging will create an issue while you are restoring/replaying log files.
But still i will not be a problem if you are having multiple passive copy and lag copy.(minimum of one passive & one lag copy of DB)

* If you enable circular logging, you could not replay the logs while you DB issue.
* but if you have passive copy still you could use that..
* if any problem with the logs and it affected both (active & passive) then you ahve still the lag copy which does not affect..

I would suggest,  if you have passive copy and lag copy of DB, then you can enable circular logging...
Vijaya Babu SekarAssociate Ops ManagerCommented:
Transaction log will truncate, if you do the Full bakcup or Incremental Backup, better you can do full backup. still you have problem, you can refer the below article

if your environment is site resiliency with DAG. you should increase band width other wise you can face log truncation issues


fallriverelectricAuthor Commented:
Been working with vRanger who says their backup solution can handle this with VSS.  Configured it, will watch it over the weekend and update next week.
fallriverelectricAuthor Commented:
As it turns out, vRanger is exchange-aware and we didn't realize it.  Got it configured correctly now and the logs are truncating.  Thanks for the help!
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.

Join & Write a Comment

Featured Post

Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now