1GB Log file 4

[sarahm]

Was wondering if anyone can tell me whether I can delete log files (inparticular, todays one which is 1GB in size!)

It's residing in c:\exchsrvr\imcdata\log

There are lots of files in this directory, all ending in .log - the really large one is called l0000000.log

I checked the Exchange administrator and found that logging was set to maximum to all the entries, so set them all to none and stopped and restarted the IMS.

Can I delete these files now?

Also, an event id: 2003 is being logged in the event logs "A new TCP/IP SMTP connection has been made to host 194.131.46.33 (for lr.org), logfile: L0000000.log" - will this stop, now that I've turned off logging?

 

[ikendo]

Yeah, you need to backup you mailbox. Once is backup, it automatically flush out all the log files.
Im using Veritas BE 8.X and its automatically delete those log file.

 

[Grenage]

Yes I believe once the log files are backed up you can delete them. As said above if you are using a backup program such as Backup exec with the exchange add-on there is an option to delete these files after they have been backed up.

 

[sarahm]

Thanks for your help.

What happens if the files get deleted BEFORE the backup...

 

[Grenage]

Thats a good question, I do not have the answer to hand but I believe they are used in the restore process.

There have been a few posts on this subject which you might find a more detailed answer, or someone with a bit more know-how (there are many) will reply

 

[brontosaurus]

If the files get deleted before a backup there's a small chance you'd lose some data in the case of a disaster. YOu should try to do a full backup at least a couple times a week (or more, if possible) to avoid such problems.
As for that Event Viewer message, that's a normal IMC event stating that someone just sent a mail to that IP/domain. If you set all logging to none, those messages will likely stop...(but they're actually good to have around anyway).

 

[sarahm]

I do a full backup on this particular server every night. I gather that the fact that I had so many of the files hanging about suggest that I had better look at what my backup is actually doing (flag to delete after backing up seems like it wasn't set in this case).

Thanks everyone,for all your help and suggestions.

 

[johnny99]

What backupsoftware do you use?

 

[adobbie]

Old thread but in case anyone else is reading this...

DO NOT SELECT "flag to delete after backing up" - this will delete all files selected for backup after the backup completes!! This option is typically used for archiving data - you backup the selected files - e.g. by selecting all files older than a set date then Backup Exec deletes the files from disk! This is NOT the reason why the Exchange logs are not clearing...

Exchange logs should clear after backup when they are committed to the database. If they are not, there is another problem - backup selection? Exchange Agent being used? There are a number of possible causes but I would not recommend just deleting the Exchange logs!! Sort out the backup and this will clear the logs - otherwise, the hard drives will fill up...

 

[zbnet]

Adobbie:

Firstly, I'd be surprised if anyone was basing their current problems on advice from a 2-year-old thread.

Secondly, there is a fundamental error of assumption in the original thread which no one (including you) has spotted. The original poster was talking about the SMTP logs that the IMS makes in the IMCDATA directory - these are directly caused by the IMS logging options being set to maximum, and are nothing whatsoever to do with the email database logging transaction logs. There are big clues in the original post, like the directory name, like the fact that the logging stopped when the IMS logging option was disabled, like the fact that the largest log file is 1GB (transaction log files are alwasy 5MB, no more and no less), etc etc.

I'm not really having a go at you, just trying to stop compounded error and people being even more confused than they should be. The real errors here are people who responded to the original question in error.