IT Employment

Ask something
Discussion Locked

Exchange 5.5 private stores

0 helpful
3 replies

by netwrangler

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I currently run an Exchange 5.5 server. It hit the 16GB limit on Friday. I ran a eseutil to defrag it. The priv.edb size reads 14.7 GB. I then deleted about 8GB's of user space by killing old accounts. The problem is that the priv.edb reads the same. Does anyone know why?

thanks - Pat

3 replies

by chris..

Just because you kill an account and so forth doesn't mean that the rather dumb EDB's shrink. If you want to recover that 8GIG (damn can you say mailbox size limits and regular maintenance?) rerun the eseutil to recompact the EDB's

by netwrangler

Chris,

thanks for the help but I had already done that. I ended up changing the IS maintenance window to always and just letting it run. It flagged the files that needed to be purged and finally a 1221 messge for the priv.edb appeared.

I thank you for your comment.

Pat

by chris..

You'll eventutually want to turn off that IS maintenance running all of the time. But just from my experience I've got my team running quarterly eseutil jobs to keep the EDB's from getting ugly. It's real easy just to forget about doing that level of maintenance especially if the system doesn't seem to be having issues. You'll also thank yourself for migrating to Exchange 2k or even 03 now that it's out. The internal management of the EDB's is so much better than 5.5!

Hope this helps..

This discussion is closed to new replies.