Discussion Locked

What else is in PRIV.EDB on Exchange 5.

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I've archived over 2GB or mailboxes, but the size of th Priv.edb still show of 15.2GB. What else do I need to do to reduce that size? Is it it true that standard Exchange 5.5 database can not be greater than 16GB.

5 replies

by duwaned

Hi.
Yes it is true that Exchange Private Information stores (Priv.edb) cannot get larger than 16GB in the standard edition. Enterprise edition has no limit though.

To answer your question... Exchange databases, just like any other database needdefragmentation. When data is removed from the priv.edb file, the space that was taken up by the data which was removed is not freed up until the database is defragmented. This is done by running an Exchange command line utlity called ESEUTIL. I would advise that you make a full backup of your server before attempting this! Also run an ISINTEG before doing the defragment. Exchange is meant to defragment its own database in the background, but does not do this efficiently enough. Keep in mind though that running a ESEUTIL on your IS requires free disk space of 110% the size of your priv.edb! YOu can re-direct this to another drive if necessary

Once you have done a defrag, you will probably find that the size of your Priv.edb has gone even lower than the amount that you have just deleted!

Another thing which could have an impact on the space issue is the Tombstone life setting on your Exchange server. Tombstoning determines how long the data remains in the Information store before Exchange marks that area of the database as usable again. Check the properties of your server in Exchange Admin to see what your Tombstone settings are. For details on running ESEUTIL, and ISINTEG, refer to Technet. There are loads of articles explaining how to use these 2 utils.

For details of what I have said here, see Technet article Q255035.

Hope this helps.
Regards.
Duwane

by mckaytech

The answer above is correct both as regards the 16gig limit and the ESEUTIL off-line defrag.

I just thought I would add that what happens at 16gig is that the Information Store stops running with an Event ID of 1112. At this point, you may have uncommitted logs that have not been entered into the database. To recover, you'll need to either upgrade to the Enterprise Edition or perform an off-line defrag using ESEUTIL. Once you've done that, you can re-start the Information Store and the logs should be played forward and committed properly to the database.

Theoretically, if you're going to run the standard version, you should establish mailbox limits that keep you safe. For example, if you have 1500 mailboxes, you could set a mailbox limit of 10meg and your Information Store would never exceed 15gig. I'm well aware of the political challenges of such a limit but as opposed to a server crash...

paul

This discussion is closed to new replies.