Larry
Thu Mar 27 04:33:44 PDT 2008
Thanks SG, KJ:
What I get for posting without reviewing my notes. :-(
Jump in anytime. One of the reasons I come here is to clear my own cobwebs.
:-)
For NorthWest, and others reviewing this thread (if any) here is an MS link
on the subject, which contains several additional links, including the reg
entries to expand the store after applying SP2, and links to removing the
"white space" inside a "bloated" store after removing all the excess stuff
stored within.
http://support.microsoft.com/kb/828070
The above has been updated, sort of, to include the limits with SP2, how to
expand the limits and give warnings:
http://technet.microsoft.com/en-us/library/aa998066.aspx
In SBS there are actually four files involved here, and as SG points out, it
is the combination of the two for each set that causes the issue:
priv.edb + priv.stm
or
pub.edb + pub.stm
While I think it would be unusual in SBS, one might see public folders go
over the limit, particularly if they are being used as mail containers, with
the same issues as private db, i.e using them as file servers.
--
Larry
Please post the resolution to
your issue so that all can benefit.
"kj [SBS MVP]" <KevinJ.SBS@SPAMFREE.gmail.com> wrote in message
news:e1OY%23k8jIHA.1188@TK2MSFTNGP04.phx.gbl...
> SuperGumby [SBS MVP] wrote:
>> nope, 16GB per store, single pub, single priv, possible 32GB total.
>> Same as Exchange Standard.
>>
>> SP2 automatically raises the limit to 18GB, per store.
>> The 'temp expansion' possible on pre-SP2 systems is to 17GB.
>
> Yes, it can just as the 16GB, 18GB, or other configured maximums. I'm not
> fully behind the 10GB value, but agree completly on the excessively large
> stores, RAM, dedicated server, and all the rest.
>
> Also for the OP and others, a store *can* be offline size reduced
> following recovery of unusual circumstances (ie email bloat on unlimited
> mailboxes). It's not something worthwhile doing for normal operating
> procedures and has risks attached. This can and does happen and all the
> online whitespace defrag won't help get that 8GB "in use" store that has
> been database expanded to 32GB down to a backup manageable level.
>
> Specifically, the offline defrag creates a brand new database
> reconstructed from the bloated database. It's not something the casual SBS
> admin would want to attempt, but it can be done, and if necessary, MS
> support can help esnure the success and contigiency.
>
>>
>> The 'combination' is the total size of store_name.edb +
>> store_name.stm.
>> Sorry Larry, had to step in.
>>
>> I do not know if a 75+GB store can be 'temporarily expanded' to 76GB
>> but IMHO anyone running a 75GB store (possible 150GB total) on a
>> system limited to 4GB of RAM, and providing another gazillion other
>> things, is abso-freakin-lutely NUTS. Large stores (ie. >10GB) belong
>> on dedicated servers. If immediacy of mail access justifies the
>> expense of running a large store it also justifies the dedicated
>> server to run it on (and that server should not be subject to a 4GB
>> RAM restriction, or doing another thousand things).
>>
>> "Larry Struckmeyer" <lstruckmeyer(at)mis-wizards(dot)com> wrote in
>> message news:%2365P%23X6jIHA.748@TK2MSFTNGP04.phx.gbl...
>>> Hi:
>>>
>>> Exchange Standard, without SP2, is limited to a combined store of
>>> Public and Private data bases of 16 GB, whereupon it will stop. There is
>>> a temporary expansion available to 18 GB to give you the
>>> chance to extract all those 3 GB videos that are stored there.
>>>
>>> With SP2, and the appropriate registry tweaks, you can incrementally
>>> or all at once raise the limit to 75 GB. Where users use the Store
>>> as a file cabinet, it would be suicide to go to 75, as once you hit
>>> that limit your done.
>>>
>>> Don't now what reader you are using for the news groups, but any NNTP
>>> reader, such as Outlook Express, is galaxies better than the web
>>> interface.
>>>
>>> --
>>> Larry
>>>
>>> Please post the resolution to
>>> your issue so that all can benefit.
>>>
>>>
>>> "Northwest Upgrades Plus" <andyn@nwupgradesplus.com(donotspam)>
>>> wrote in message
>>> news:1F30C3E4-8198-40D8-B0BE-9A34E930F2D2@microsoft.com...
>>>> My apologies. For some reason when I select the link in my e-mail
>>>> nothing comes up. I was not aware that there had been a respose. I
>>>> think what I will
>>>> do is to have all users clean up their mail boxes to see if that
>>>> helps. I read somewhere that at 16GB Exchange starts having
>>>> problems. Is this correct?
>>>> --
>>>> Thanks for your help.
>>>>
>>>>
>>>> "Larry Struckmeyer" wrote:
>>>>
>>>>> Hi NorthWest:
>>>>>
>>>>> My suggestion is that you look to making an image and then
>>>>> incremental images, then backing up the incremental images over
>>>>> the inet. www.storagecraft.com
>>>>>
>>>>> and others.
>>>>>
>>>>> It is not really possible, nor practical to "shrink" the exchange
>>>>> store except by limiting the amount of stuff that users put there.
>>>>> It is not meant to be used as a file server.
>>>>>
>>>>> I think you were given this type of advice a few days ago in this
>>>>> group. --
>>>>> Larry
>>>>>
>>>>> Please post the resolution to
>>>>> your issue so that all can benefit.
>>>>>
>>>>>
>>>>> "Northwest Upgrades Plus" <andyn@nwupgradesplus.com(donotspam)>
>>>>> wrote in message
>>>>> news:B3004771-DCB2-4DAF-AF2D-0FAC95DDA60B@microsoft.com...
>>>>>> Is there any way to compress or otherwise shrink the file
>>>>>> Priv1.edb that
>>>>>> resides in the Exchangesrvr directory? I have a client that is
>>>>>> using off
>>>>>> site
>>>>>> backup and this one file is about 20GB in size and takes forever
>>>>>> to backup.
>>>>>> Any suggestions would be appreciated.
>>>>>> --
>>>>>> Thanks for your help.
>
> --
> /kj
>