Transaction logs increasing rapidly.

We have 4 Exchange databases (Exch-2010 SP3) and observed that transaction logs are generating more on one of the database which causes disk space issue.

Can someone guide how we can identify the reason for increasing transaction logs for particular database.
sanjayambreAsked:
Who is Participating?
 
smangognaCommented:
You have to run a full backup to delete unecesary log files
0
 
sanjayambreAuthor Commented:
We have run full backup but my question is how we can identify the reason for generating huge no of transaction logs, is there any tool to find out.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
EEhotlineConnect With a Mentor Commented:
Install ExMon on the server and see if you can identify a client that may be hitting the database hard.

http://www.microsoft.com/en-us/download/details.aspx?id=11461


Aso try:

http://blogs.technet.com/b/exchange/archive/2012/01/31/a-script-to-troubleshoot-issues-with-exchange-activesync.aspx

A script to troubleshoot issues with Exchange ActiveSync
0
 
Adam BrownSr Solutions ArchitectCommented:
Generally transaction logs will increase on a single database because the mailboxes on that database are making more changes than the other databases. This can be because there is more mail going to those users, or those users are sending more mail, or there are a lot of large attachments on those mailboxes. In general, the only thing that causes transaction log growth is an increase in the number of transactions. If one database is generating more logs than the others, you can try to distribute some of the users on that database to other databases. Other than that, there really isn't much you could do about it. Transaction logs record everything that every user does in Exchange, so you just have to deal with it if one database records more logs or balance the users across your databases more efficiently.
0
 
AmitConnect With a Mentor IT ArchitectCommented:
Single mailbox or DB corruption can also cause abnormal logs. Run mailbox repair database PS command. No downtime required, however better to run after production hours. Check event logs for any errors.

Steps you can find here
http://blogs.technet.com/b/exchange/archive/2010/08/23/3410708.aspx

If still no luck, create new db and move all mailboxes to new db and remove old db.
0
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.