Why my Exchange Server 2007 transaction log gets full

Question

I'm having problem in one of the partition of the Exchange Server 2007 SP 2 transaction log, it is installed on my Windows Server 2008 with the configuration as CCR.

In one of the storage group, the transaction log partition goes down quickly to low ([from 30 GB into 0 KB in just over the weekend) when the backup missed just one day thus rendering the whole mailbox on that Storage group inaccessible.

Is there any way to identify what could be the root cause of this problem and how to rectify this ?

Any comments and suggestion would be greatly appreciated.

Thanks.

score 7 · Answer 1 · answered Jan 31 '11 at 23:40

7

Exchange transaction-logs only get cleared after a successful backup. In your case, I would examine your backup system's backup logs for clues as to why the backups are failing.

answered Jan 31 '11 at 23:40

sysadmin1138

133,124
18
176
300

1

This is the answer. DO A BACKUP NOW! – Antonius Bloch Feb 01 '11 at 01:15
3

@Albert: 30GB of log files in a weekend? The log drive filling up is not the only issue you need to look at. How in the world is your Exchange Server accumulating 30GB of transaction logs in a weekend? I would suggest looking into that. – joeqwerty Feb 01 '11 at 03:27
@Joe, that's why I don't know for now any pointer to the investigation / culprit is appreciated. – Senior Systems Engineer Feb 02 '11 at 04:05

score 1 · Answer 2 · answered Feb 01 '11 at 23:58

1

I've seen Blackberry Enterprise Server cause massive amounts of transaction logging in a short period of time before. Are you using BES in your environment?

Is there anything else happening on weekends that might cause a lot of email activity? eg, scripts or applications that generate email alerts?

answered Feb 01 '11 at 23:58

Paul Cunningham

281
1
4

Yes there is BES installed in my domain, but of course it is installed in different server. – Senior Systems Engineer Feb 02 '11 at 04:06

score 1 · Accepted Answer · answered Feb 02 '11 at 04:01

This is correct - A Backup will automatically clear your logs for you. I also have a CCR environment - The transaction logs are exactly what they're called. Every "transaction" or change regarding mail (logs are like your instructions to your database that say "here are your changes!") - need to be "written" to your Storage Group Databases. First, your Active Node (in the cluster) will be creating the initial transaction logs on your server. The storage group databases (.edb files) are then "seeded" to your Passive Node in your network. This initial seed is usually done at the time your cluster is created - or if you rebuild / repair a storage group database...Once seeded, the only thing that moves between the nodes are the transaction logs. The logs are created from the active node - and are then sent over to the passive node to "update" the passive node's .edb files or Storage group databases. If your Active node cannot pass those logs to the passive node, they can fill up very fast. Basically, do a back up - but another place to check would be network connections (between the two nodes or File Share Witness Communication. Also check your Fail-Over Cluster logs / System Application Logs on the nodes - these will both be FULL of useful information as to why or where there could be problems.

Why my Exchange Server 2007 transaction log gets full

3 Answers3

Linked