Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Why so many logs? 2

Status
Not open for further replies.

Smeglor

IS-IT--Management
Jan 16, 2004
70
US
I have about 1450 log files in the MDBDATA subfolder of the exchange folder. Each is 5MB in size and I have several log files per day. How do you read these files? I open it in notepad but much of it is unreadable. Also, why are there so many log files?

I don't know sir...I guess its broke.
 
It's a bad idea to muck with the logs. If you damage or remove a log that has not been committed, your stores will dismaount and the IS will not start. They contain transactions that may or may not yet be committed to the database. The edb.chk, or checkpoint tracks which ones have been committed. Committed logs are truncated [removed] on successful completion of a full online backup with an exchange aware backup agent. You can use ntbackup if you don't have anything else. Choose MSExchange IS when you backup.

 
Thanks.

I don't know sir...I guess its broke.
 
I have enabled circular logging (as of today) to hopefully circumvent this issue - 45GB of log files - Disk full - Exchange halted over the weekend....

Maybe this might be a solution to your problem.
Approach with care as the log files are required for system restores.

We use Backup Exec and perform direct mailbox and public folder backups so the log files are not relevant to us.

Rgds

 
Typically, I found a long time ago, a full backup with native windows backup clears the logs because it commits them. A regular backup should be done to help this keep clear. For the information store anyway.
 
I have the same problem with endless 5MB log files being created in the MDBData folder, almost every 2 minutes! Where can I find the properties of the object for these log files? Can it be turned off or control how often they are made?
 
Stuart, look in the help for circular logging

Marc
If 'something' 'somewhere' gives 'some' error, expect random guesses or no replies at all. Please specify details.
Free Tip: The F1 Key does NOT destroy your PC!

How Do I Get Great Answers To my Tek-Tips Questions? See faq222-2244
 
back up the database using ntbackup or backup exec with exchange agent as this will remove old transaction logs.

<signature for rent>
 
Okay, I must be missing something. I did a backup of the mdbdata folder using Windows backup on my server 2k3 and exchange 2k3. The backup ran just fine. After I was done all the logs were still there. Do I need to do something else to "commit" the logs?

Thanks,

Jon
 
Generally you backup your information store. Information store appears as an option alongside drive letters etc in Exchange aware backup software. Once you do a full backup of the information store, the logs get flushed. NTBackup is Exchange aware as are products such as Veritas and ArcServe (which both flush logs by default on a FUll backup of the Information Store)



Claudius (What certifications??)
 
but if you only do a backup of one store or don't do a full backup none of them will flush.

<signature for rent>
 
I told backup to backup the entire computer (which it did) and the logs still didn't commit. I don't see any location called "information store"

Jon
 
Hi,

When I try to do a backup using windows backup it fails. Here is the error in the report. Any ideas how to resolve this?

Jon

Backup started on 7/27/2004 at 1:24 PM.
The 'Microsoft Information Store' returned 'Backup is already active.
' from a call to 'HrESEBackupSetup()' additional data '-'The 'Microsoft Information Store' returned
'Functions called in an invalid sequence.
' from a call to 'HrESEBackupClose()' additional data '-'
The operation was ended.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top