Exchange Transaction logs Fills disk

[excessum]

The 5MB logfiles fills the harddrive.
4-5 new logfiles per. minute.
Thats 20-25MB per. minute.
I run backup every night, and the logfiles gets deleted by backup. But the drive gets full before the backup runs.
Any tips?

excessum

 

[PeriyurParthi]

i hope some thing worng with server. the log files contiains the mail details like when it was sent,by whom, where and so on. you can see it by opening the log files. if it is created a 4 to 5 perminute means the message flow is huge. check in the queue or confirm your server is not spammed.
if your drive gets full, you can free up the disk space by deleting *.dmp, *.tmp *.$$$ *.log files from the harddisk.
if you really need a huge space then u can transfer the logfiles directory to new a another drive (D), by clicking the First Storage Group-properties-change the transaction log files DIR path to your D; drive
hope this helps
parthi

 

[excessum]

Thanks for the reply.

I have checked for spamming. There are not many messages in queue. There are 400 users connected to this exchange.
I use the D Drive. 8BG partision. Fills up in one day. I have another exchange server with 600 users. It uses 200MB.

 

[SSonnier]

I am having this trouble also. We haev fewer than 25 accounts on this exchange server. I do not back up to tape over teh weekends and lately, a 15gig drive will fill up after 2 days. How can I tell If we are being spammed and where all this traffic is coming from. This does not make sense to me.

 

[dpflkr]

Is there a specific reason you have email logging turned on? If you are not monitoring email traffic, you can turn logging off by opening up Exchange System Manager, opening up "servers", right clicking on your email server name and unchecking the logging and message tracking options.

You might also want to check your "badmail" file. This is where all of the undeliverable mail goes to.

One other thing to check is your queues under the SMTP virtual mail server. To get there:

Click Servers
Click Server name
Click Protocols
Click SMTP
Click Default SMTP virtual server
Click Queues

If there are a lot of "retry" entries there, those are all emails that you are trying to send a NDR to. Those will fill up your badmail and log files quickly.

You can see what emails are in there by right clicking them, clicking "enumerate messages" the double click on them. If there is nothing important trying to be sent, right click and then click "delete all messages - no NDR"

I make a habit of checking these and clearing the badmail folder daily.

Hope this helps!

 

[ericwasewe]

Hello I seem to be having the same problem. We've never had our transaction logs grow so quickly before. We have about 600 accounts and in the last two days I have had to clean out the logs. I now have circular logging enabled and removed message tracking. Our queues are fine. Any suggestions

 

[excessum]

We had to create a new database and move the mailboxes.
It workes fine now.

 

[chubilly]

Normally, when the backup is done, all the log files get purged. But the last few days it did not get purged out.
So I made a mistake and manually deleted the transaction log files. Now the backup will not finish as it sees errors.
What should I do now or how do I rectify the problem?
Thanks in advance.

 

[dcb333]

Make sure your not scanning with anti-virus software or backing up the Mexchange)drive.

 

[MattOP]

YOu can fairly safely,

Stop Exchange
Delete all log files or at least move to new Directory
Restart Exchange Infor Store

Trans logs files will be auto recreated in the MDBDATA dir when the info store starts.

BOOM! Should be up and running... If not you'll need to check our your dbs integrity.

 

[raksexchange247]

hi,

with a full backup the transitional files get purged. if you have deleted your log files you can use eseutil to check the integrity of the database and route out the bits that are causing the bother. this wil mean loss of some emails, atleast you've got your exchange back up and running..

rakesh

 

[excessum]

Hi,

I used eseutil but that did not solve the problem. So I had to manually move all the mailboxes to a new database.
Problem solved.

-Paal-