Huge pub1.edb file... not sure why!

Hi all... running SBS 2003 Standard. Our Priv1.edb size is around 6GB, the Pub1.edb however is a massive 90gb!! I have looked at the "Public Folders" branch in the ESM and the largest file there is 7MB. Am at a loss as to whats causing this for now. The only thing I can guess at that is causing this is the "Archive Messages" setting on the Mailbox Store "General" Properties Tab. Initially I had this enabled and pointing to an "<domain> Archive"  Public Folder that was already setup but contained within the "Microsoft Exchange System Objects" container. After setting this up I forgot about it but then got a nasty shock when the Public Store dismounted. Backups have been running fine, so logs are flushed and maintenance has been performed on the databases etc..

I tried to access the contents of the "<domain> Archive"  Public Folder but could not. Have since created a new Public Folder and changed archive setting to point to it. My main concern is now to try and get this Pub1.edb size right down.

Any help would be gratefully appreciated!!

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

if you were archiving messages to a public folder then, i guess that the size of that public folder would be contributing towards the total size of you pub1.edb file

is message archiving still enabled?

check the deletion settings on the public folder store.

offline defrag can be run the reduce the size of the public folder database, but it would require 110% of free disk space of the public database size.

have you checked the application logs for online maintenance eventsfor the public store? what does it tell you about free space in that event.
nellsterAuthor Commented:
Thanks for the reply rakeshmiglani. Have checked the events log for last night and over the course of the night I had a few logs like the one below;

The database "First Storage Group\Public Folder Store (COMPUTER)" has 92405 megabytes of free space after online defragmentation has terminated. "

Does this mean that the space should have been free after the defragmentation? Or is it only an offline defrag that will do that?

Deletion settings on public folders are basically non existant. Apart form the Archive Folder there are no mailbox items as Public Folders.

Thought, if I were to adjust the rentention limits and try and delete the initial system "Archive" folder, that should free up some space correct? Wise to delete an object in the Exchange System Object's container?


92405 MB comes to approx 90 GB

this is all white space and will be re-claimed with an offline defrag.

if that Archive folder is no longer required then you can delete it. I would not recommend deleting it from the MESO container. you can delete it from the ESM as well.

before you delete that "archive" folder you need to disable the message archiving or designate another folder/mailbox for mail achiving

How to defragment with the Eseutil utility (Eseutil.exe)

Support WebCast: Microsoft Exchange: Offline Defragmentation with the Eseutil Utility

How to run Eseutil on a computer without Exchange Server

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

nellsterAuthor Commented:
thought that might be the case. Thanks for the reply. Offline defrag on that lot will take an age.. goodie!

Would like to delete the initial Archive public folder but it does not appear in the Public Folder list in the ESM. Only in AD.

Was that folder deleted at some point of time?

in esm, you can check this at two places.

1) expand public folder tree at the bottom of esm and look at the folder
2) expand public folder tree and check the public folder

if the public folder is not listed in esm anywhere then you don't need to worry about it

what is the status of the message archive settings? is that still enabled?
nellsterAuthor Commented:
The origional "Archive" settings for the mailbox store was set to a public folder named "Company Archive". This folder does not show in the ESM Public Folder tree, neither in the Folders tree at the bottom. The only place I could find it was within Active Directory/Microsoft Exchange System Objects where it's type was "Public Folder". If its not listed in the ESM and I don't need to worry about it I am concerned as to how the Pub1.edb became so big, seeing as the accumilated size of all the folders displayed in the Public Folder tree of the ESM is approx 10mb. Very strange.

I have created another Public Folder to Archive to which I can access fine. I have disabled archiving for now.


good, then you are all set. you just need to run the offline defrag on pub1.edb to reclaim the white space.

you can check the above listed kb articles also for online defrag
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.