Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
priv1.edb file help!!!
- Thread starter josh0227
- Start date
included in it? It is your mail store.
Since it grows indefinately (sic). Well it doesn't, it only grows when mail arrives faster than it is deleted.
Is there a way that we can defrag it? Yes, your maintenance routine will keep it optimal. This happens automatically.
Since it grows indefinately (sic). Well it doesn't, it only grows when mail arrives faster than it is deleted.
Is there a way that we can defrag it? Yes, your maintenance routine will keep it optimal. This happens automatically.
That is a very common situation – the users do not delete/archive their emails and use the exchange store as a storage for their important documents.
If you are not running the enterprise version of exchange (this is valid for exchange 2003 server too) you are pressed by the 15 Gb limit.
Explaining to the users how to archive their mail can help. Creating a company policy for archiving emails older than a year for example will reduce significantly the size of the mailbox store. When a lot of emails are removed from the mailbox storage in a short interval of time – either by deleting or archiving the size of the store decreases but the change is not equal to the size of the removed data. In such cases it is suitable to perform an offline defragmentation. I’ve seen how the size of the EDB file decreases after such a procedure with 20 – 30 percent.
There are different approaches for performing offline defragmentation depending on the free space available on your hard drive. You might consider also moving the EDB files to a different hard drive or partition depending on the situation.
NetoMeter
If you are not running the enterprise version of exchange (this is valid for exchange 2003 server too) you are pressed by the 15 Gb limit.
Explaining to the users how to archive their mail can help. Creating a company policy for archiving emails older than a year for example will reduce significantly the size of the mailbox store. When a lot of emails are removed from the mailbox storage in a short interval of time – either by deleting or archiving the size of the store decreases but the change is not equal to the size of the removed data. In such cases it is suitable to perform an offline defragmentation. I’ve seen how the size of the EDB file decreases after such a procedure with 20 – 30 percent.
There are different approaches for performing offline defragmentation depending on the free space available on your hard drive. You might consider also moving the EDB files to a different hard drive or partition depending on the situation.
After the users have deleted mail the edb will not shrink. It will retain empty pages, but still consume the same disk size.
If you wish to shrink the database after archival and deletion of messages, you will need to do an offline defrag wtih ESEUTIL.
The normal eseutil that runs nightly will only clean up the empty pages in the database, it will not remove the empty pages. You can see this in the logs. ESEUTIL will do a defrag and tell you your database has 2048MB available in priv1.edb. But if you go look at priv1.edb its the same size as it was yesterday. So its like having a book, from which you erased all the text. The book is still the same size after erasing the words. Offline defrag will allow you to "tear out the emtpy pages".
Robert Liebsch
Stone Yamashita Partners
If you wish to shrink the database after archival and deletion of messages, you will need to do an offline defrag wtih ESEUTIL.
The normal eseutil that runs nightly will only clean up the empty pages in the database, it will not remove the empty pages. You can see this in the logs. ESEUTIL will do a defrag and tell you your database has 2048MB available in priv1.edb. But if you go look at priv1.edb its the same size as it was yesterday. So its like having a book, from which you erased all the text. The book is still the same size after erasing the words. Offline defrag will allow you to "tear out the emtpy pages".
Robert Liebsch
Stone Yamashita Partners
>the 15 Gb limit
16GB
In Exchange 2003 Standard Edition there is a registry setting to allow this to be temporarily bumped up to 17Gb (thus interestingly indicating that the Standard Edition database size limitation is artificially imposed rather than being inherent) to allow users to login and delete mail.
SP2 for Exchange 2003 is supposed to bump up the database size limit to 75Gb
16GB
In Exchange 2003 Standard Edition there is a registry setting to allow this to be temporarily bumped up to 17Gb (thus interestingly indicating that the Standard Edition database size limitation is artificially imposed rather than being inherent) to allow users to login and delete mail.
SP2 for Exchange 2003 is supposed to bump up the database size limit to 75Gb
- Status
Similar threads
- Locked
- Helpful tip
- Locked
- Question
- Locked
- Question