Exchange share HUGE. mailboxes not?

sdotbrucato

[H]ard|Gawd
Joined
Oct 7, 2005
Messages
1,722
Please excuse my ignorance on the subject, but I recently recieved a low space alert from a server I administer. It's an SBS03 box, and exchange is on my 200GB partition. I have about 100GB worth of files and what not. and my exchange share is reaching 80GB. Now I'm serving up about 8 users and 10 e-mail addresses, and none of them are over 500MB (strict enforcement on limit). Why the hell is this share so big?!

EDIT:Well Im probably going to have to start a new thread for this, but I went to log into OWA and I got this error "HTTP/1.1 503 Service Unavailable". This is after Im presented the OWA login screen, and I enter my credentials. >.<
 
Last edited:
Thanks Shockey, I found that myself too. I'm remoted in ATM, apparently these are supposed to be getting flushed after backups, but it hasnt been for about a week now? (backup logs are fine, eventviewer is looking good, I resetup NTBackup and I'm running that now, hopefully this flushes the logs.
 
Thanks Shockey, I found that myself too. I'm remoted in ATM, apparently these are supposed to be getting flushed after backups, but it hasnt been for about a week now? (backup logs are fine, eventviewer is looking good, I resetup NTBackup and I'm running that now, hopefully this flushes the logs.


lol no problem. Happy i could help. Never played with exchange. Hoping to here shortly :p in esx
 
Take a look at the content of the MDBDATA directory. If your backup is failing or improperly supporting Exchange....you'll see log files start to accumulate because they are not being flushed. These specific log files will each be 5,120KB in size. If you do find a ton of them...sort by date and manually delete a whole crapload of them up until say a week ago.

But before shooting right for the log files, take a look at the size of the priv and pub .EDB files...they'll make up the meat of the directory.
 
Last edited:
Take a look at the content of the MDBDATA directory. If your backup is failing or improperly supporting Exchange....you'll see log files start to accumulate because they are not being flushed. These specific log files will each be 5,120KB in size. If you do find a ton of them...sort by date and manually delete a whole crapload of them up until say a week ago.

But before shooting right for the log files, take a look at the size of the priv and pub .EDB files...they'll make up the meat of the directory.

NTbackup ran to completion last night/this morning and it's still huge. The log files are still their, and my .EDB file is still 75GB.

I'm going to have the users archive and cleanup their boxes, but I don't see what that has to do with this, considering 10 boxes x 500MB is not 75GB!

What the hell!
 
NTbackup ran to completion last night/this morning and it's still huge. The log files are still their, and my .EDB file is still 75GB.

I'm going to have the users archive and cleanup their boxes, but I don't see what that has to do with this, considering 10 boxes x 500MB is not 75GB!

What the hell!

The EDB file being the most of it...guess your backup is doing OK and you don't have many of those 5,120 log files. Believe me..if your backup is failing for months on end...you'll have kajillions of those 5,120 log files. It's normal to have like 50 of them...I forget the time intervals...I think every 20 minutes or so one is made..so you'll have a handful until the next time backup sweeps though.
 
Back
Top