bccadmin
asked on
.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?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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.
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.
Understood that could be because you are using Exchange standard Edition. Yeah you can go ahead with defragmentation...
ASKER
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.
Thank you.
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.