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

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.
3 Solutions
You have to run a full backup to delete unecesary log files
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.
Install ExMon on the server and see if you can identify a client that may be hitting the database hard.


Aso try:


A script to troubleshoot issues with Exchange ActiveSync
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!

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.
AmitIT 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

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

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

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