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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MDB Logs

Status
Not open for further replies.

ankit0680

Technical User
Sep 26, 2006
38
US
Hello,
I am running Exchange 2003 sTandard, with abotu 25 GB in my Store. Today is 10/23 between 10/4 adn today my MDBlog folder has 1871 log files, each being 5.1 MB. We are doing 100 Files a night, this is killing my files, is thier somethign wrong with this,and how can I control the number of logs?
 
One thing you could do is run an extra backup, since running one purges all the files. Or you could get more disk space and let things be. Or you could enable circular logging, which would keep the number of logs down, but reduces the ease of recovery in a disaster situation.

BUT... you may already have circular logging turned on and are still seeing lots of logs. This would indicate a problem with your I/O subsystem. If you have that large a store, that active a userbase, and your mdbdata folder is on a RAID with only 2-3 spindles, this problem could just be a result of sluggish write performance due to your disks being overworked.

Check out this article for more on circular logging:

ShackDaddy
 
Another thing you can do is lower the retention time, if you have a decent backup at least.

Marc
[sub]If 'something' 'somewhere' gives 'some' error, expect random guesses or no replies at all.
Free Tip: The F1 Key does NOT destroy your PC!
[/sub]
 
To reinforce what ShackDaddy says, a FULL backup using an Exchange aware backup solution should flush those log files.

What's up with your backups?

Pat Richard, MCSE MCSA:Messaging CNA MVP
Want to know how email works? Read for yourself -
 
We Use Veritas. I run a differential nightly and a full every week but logs are two weeks old?
 
Pat's right. Your full backup might not be flushing the transaction logs into the Exchange database if you aren't running the BE Exchange Agent.

"Exchange aware" backup solutions know to trigger the log truncation/flush. Even NTBackup is "aware" in this way, so we sort of take it for granted, but Veritas/Symantec want you to license that functionality.

ShackDaddy
 
THanks. I thought we were running the exchange agent but I will verify.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top