Exchange 2003 Frequent Rapid Growth of Transaction logs

We are having issues on 3 of our servers wherein the transaction logs that reside on a separate drive frequenty experiences rapid growth. What we do is enabling circular logging and disable when its back down to small drive size. When we don't do it, it crashes information store.

We opened a case with microsoft and they can't see anything after reviewing our servers message tracking and transaction logs.

Can someone please shed us some light??

Thank you!
Who is Participating?
syseng007Author Commented:
I solved the issue by dismounting the datastores and recreating a new upstream of transaction logs.
Glen KnightCommented:
How long does it take to fill the transaction logs?
How many mailboxes are on the server?
Are they high use mailboxes? Lots of emails?
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

Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Run ExMon to understand which user is generating max CPU and maybe its some issue with his Mailbox or machine compromized

- Rancy
Simon Butler (Sembee)ConsultantCommented:
Primary cause of this problem in recent months has been only one thing.

Apple devices. iPhone, iPads etc.

It can be just one device, it will cause a loop and that can generate a high amount of logs.
If you allow ActiveSync devices then you need to ensure that the iOS is kept up to date, and I mean right up to date. On Exchange 2003 there are limited ways to discover what people are using, so you will have to just nag people to update.

AmitIT ArchitectCommented:
Log growth depends on several factors and determining the root cause require lot of monitoring and troubleshooting. Here is one article which talks about all steps

Whenever you have issue next time use it. According to my exp, major contributor for log growth issues are:

1) Hung backup
2) IOS
3) Virus or spam attack, if you don't have mailbox limits
4) Undersized servers which includes (CPU, RAM, Disk Space)

Hope this helps
syseng007Author Commented:
@demazter How long does it take to fill the transaction logs? probably a week
How many mailboxes are on the server? 2 datastores (1 datastore has 900, 2nd datastore has 125 mailboxes)
Are they high use mailboxes? Lots of emails? Yes.
syseng007Author Commented:
We found out that our backup team stopped the backup on our exchange servers for a week.
AmitIT ArchitectCommented:
You have great backup team. Better you implement monitoring tool, which can check db backup status.
syseng007Author Commented:
@amitkulshrestha - Tell me about it. What monitoring tool we can use? Can we go by event iDs?

Also, because of this situation two of our servers are having issues. The logs are not truncating now.  I ran a full ntbackup myself to see it and the logs didn't truncate. working with Microsoft takes forever. Is there a way we can work on this?

Please advise!

Thank you.
AmitIT ArchitectCommented:
Yes you can do it via script. here is the link

If logs still not purging. My suggestion is to create new db and move the mailboxes and get rid of old db.
syseng007Author Commented:
I solved my own issue.
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.