Exchange Information Store Size Issue

I have a customer running Exchange 2003 SP2 on Server 2003 Standard.  They reached the size limit for the information store and it was dismounting.  I explained the limit and made them clean up the boxes and put limits on the size for the users to not reach the limit, however the store continues to dismount everynight with the same error.

Exchange store 'First Storage Group\Mailbox Store (FRANZMAIL)': The logical size of this database (the logical size equals the physical size of the .edb file and the .stm file minus the logical free space in each) is 25 GB. This database size has exceeded the size limit of 18 GB.

This database will be dismounted immediately.

I looked into it further and I found some weird stuff.  The exchange server has a seperate hard drive to hold the exchange data so  D:\ExchangeMDBData\MDBDATA contains all logs and .stm and .edb files.  The folder is 28.2 gb and contains logs that are up to 3 days old.  The D: drive is a 250 gb and has no other information stored on it, however it shows that it only has 82.8 GB free.  

I have 2 questions:

1.  My users mailboxes add up to approximately 8.5 gb now and have been like that for 2 days.  So I shouldn't be past the size limit there, but it still is stopping the information store.  How do I fix that?

2.  Why is my D: drive missing about 110 GB of space?

I would really appreciate any ideas.  Thanks in advance.  

Who is Participating?
This article on Microsoft Technet explains how the database limit is enforced on Exchange 2003 SP2.

As for the missing space, I would suggest running a tool on the drive to see where the space has gone. Something like Treesize from Jam Software will be fine. It will show you if the data is stored in hidden files etc.

You don't have to stick with an 18gb limit. That is the default limit on Exchange 2003 SP2. The maximum limit is actually 75gb, which requires a registry change to increase.

There was a change in the way that the limits are handled in SP2. The physical size is no longer used. It is the amount of data. Therefore if you have 25gb database but there is 8gb of free space (Aka white space) in the database then the database should not mount. Look for event ID 1221 to see how much space there is.

However I would simply make the registry change to increase the amount of email that can be stored.

As for where the space has gone, shadow copies is a common user of space.

jessewendtAuthor Commented:
So what exactly is included in the database size?  I want to understand exactly why it is still dismounting.

Shadow copies are not enabled, that was my first guess.  Any other ideas?

Thanks for the help.
So what exactly is included in the database size?  I want to understand exactly why it is still dismounting.
After you add the registry key to increase the database size to 75GB you must restart information store service to take effect.You would normally see an event indicating the database size new limit to 75Gb.Did you get that event ??
IF not,restart the information store service(this will dismount the if you need any downtime do it in off office hours.It wont take more than 2 minutes,anyways)
Note:it is better to dismount the databses,before the service is restarted.
jessewendtAuthor Commented:
It turns out I had indexing enabled on the drive so it was using a lot of space.  I adjusted the max size limit  of the info store and everything seems to be working great now.  Thanks for the help.
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.

All Courses

From novice to tech pro — start learning today.