.stm files too large

My client's Exchange 2003 priv1 database has .stm files over 78GB in size. The mailbox sizes add up to about 12GB. How do I get rid of these .stm files without crashing the Exchange server or corrupting the database?
bccadminAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

Alan HardistyCo-OwnerCommented:
Firstly - DO NOT DELETE the .STM file.

Check for event ID 1221 in the Application Event Log and look for the entry that relates to the Private Information Store.

How much space is shown as recoverable?

If you have plenty of space available to recover, you can defragment the database by taking the mailstore offline and running:

eseutil /d

To do this you will need 110% of the database size in free disk space.
0
KalluSureshKumarCommented:
If you cant afford to have a down time by running eseutil /d against stm file then please create a new mailbx store and move the mailboxes to the new one and delete old mailbox store.
0

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
bccadminAuthor Commented:
Thank you all for the quick response.

I tried to create a new mailbox store, but got an error that the maximum number of mailbox stores had been reached, even though there is only the one default store.

I'll be adding another drive to be able to run the esutil /d this weekend.
0
KalluSureshKumarCommented:
Understood that could be because you are using Exchange standard Edition. Yeah you can go ahead with defragmentation...
0
bccadminAuthor Commented:
Ran a backup, added drive space, moved the stores, defrag'd, moved stores, tested and ran a backup. All is good and Exchange down to a manageable 12GB.

Thank you.
0
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
Internet Protocol Security

From novice to tech pro — start learning today.