Exchange Transaction Logs

We have implemented an exchange 2010 server on a 2008 R2 box. For some reason, it seems that there is an excessive amount of log files on the hard drive at any given time. Usually anywhere between 10000-40000. We have to run a backup every two hours just to keep the disk space under control. This organization has about 60 mailboxes and a database at about 55gb. Why would transaction logs be written to the disk so freaquently?
Who is Participating?
LesterClaytonConnect With a Mentor Commented:
Any mailbox changes which occur will trigger transactions.  Included in this (and not limited to) are:

Mailbox imports
Mailbox moves
Users Archiving stuff

Check to see if there are any mailbox moves in progress - this is usually the culprit.

What you can do is turn on circular logging on the databases in question, until all the moves or imports are complete, and then turn it on again afterwards before you do another full backup.
StarfishTechAuthor Commented:
Thanks, yes we are in the process of moving mailboxes but actually we haven't been doing this the past few days and the logs are still out of control. Is there any danger to circular logging as long as we are backing up the database regularly?
Circular logging poses no danger, except that if your server crashes, any transactions made since the last backup are lost, as you are unable to replay them to the database.

Let's hope the server doesn't crash to soon :)
Madan SharmaConnect With a Mentor ConsultantCommented:
you can control these logs by using some tools
check the link:-
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.