URGENT - PRIV1.STM TOO BIG

URGENT - PRIV1.STM TOO BIG (Full Version)

All Forums >> [Microsoft Exchange 2003] >> Information Stores

Message

oset@libero.it -> URGENT - PRIV1.STM TOO BIG (28.Feb.2006 12:38:55 PM)
The size of priv1.stm on my exchange 2003 standard (SP1) server has reached 16.2 GB, while the priv1.edb file is about 0,3 GB so I've extended the database size limit to 17 GB from the registry. I have about 350 mailboxes on that server, and most of them (i think about 340) are used as pop3 mailboxes: users from outside locations download their messages with pop3 client software (like OL Express...) and the messages are deleted from the mailbox after the download; about 10 users use owa to access the mailbox, but only a few messages are leaved in the mailbox. Checking the total amount of mailboxes dimension I reach about 3 GB. So, the question is: if I have 3 GB of messages in the mailboxes, why the database size (priv1.edb+priv1.stm) is over 16,5 GB? Other details: 1- the server has been fresh-installed 1 year ago, and the streaming file has increased its size of over 14 GB between march and april 2005 (maybe a virus?); after that, the size of the .stm file is growing up in a way that I can say "normal" 2- After on-line defragmentation I can see there are 25 MB of free space, so I think that off-line defragmentation will not resolve my problem. 3- I would not upgrade to SP2 now, because I can't get the risk to stop that business now. Can someone suggest me anything? I'm thinking to export messages (exmerge?) and to delete the priv1.stm file, (In this way Exchange should create a new priv1.stm, right?) but I'm not shure on what to do? Thank you everybody for help.

Lancy -> RE: URGENT - PRIV1.STM TOO BIG (28.Feb.2006 1:40:32 PM)
In ESM Check the size of each mailboxes. The growth can be due to various reasons. Example: when someone sends an email with a attachment. the NDR email size will be more than email sent. this can lead to growth in databse. Secondly check the option in users outlook, if they are to set to keep a copy of messages on server. Event id 1221 doesnt report the free/white space on *.stm file. you can check this using esetuil /ms. since most people are using pop3/ imap/owa, you priv1.edb has grown less, and there is less white space in it. This is the answer to question 2. The best way is perform an offline defrag of priv1.edb. It will shrink your priv1.stm file too. also make sure you run isinteg. although not required, probablyto avoid users complaining "unable to open any attachments".

oset@libero.it -> RE: URGENT - PRIV1.STM TOO BIG (28.Feb.2006 6:15:39 PM)
If I add the size of each mailbox i get about 2,9 GB I've already checked outlook client options, and the option to keep a copy of message on the server is not enabled Also, I've already tried to do an off-line defragmentation, but I only gained 19 MB of free space. I think it's very strange and I also think that the .stm file is corrupted. Marco

gsherman -> RE: URGENT - PRIV1.STM TOO BIG (28.Feb.2006 6:35:30 PM)
If he goes to service pack 2 doesn't that eliminate the 16GB barrier and raise it to 75GB

Page: [1]