Re: opinions on store and mailbox limits

From: mitch (mitch_at_newsgroups.stuff)
Date: 03/22/05


Date: Mon, 21 Mar 2005 21:22:11 -0600

Actually I just ran into this exact problem and per microsoft it is not
designed to handle large individual mailboxes. The actual problem is the
database store being a btree database. You can have problems with
enumeration of the mailbox items. They actually stated that the number of
items is of more of a concern then the size. I have many users on 2 Gigs
each. The often recieve the waiting to retrieve data from "server" pop up.
If you are using outlook 2003 then this will not be as bad and will not
lock up the UI. By splitting the stores we have lessend the problems we now
have 4 stores for 150 users total almost 100 GB.
"Exchange Storage Guy" <brianhenderson2005@gmail.com> wrote in message
news:1111425795.644039.75440@z14g2000cwz.googlegroups.com...
> Rocky
>
> Susan is correct. Enterprise Edition is built to handle almost
> anything, but whoever told you Exchange Enterprise was made to
> accomodate many users with small mail stores - they are also correct.
> All things being held equal... the size of the users mailbox is
> proportional to the amount of IOPS demanded from their inbox... i.e.
> you have two identical users (lets say Joe and Josie) - they do
> everything the exact same, log in same time, check email same time, use
> the same calendar functions, etc... but Josie likes to save her
> attachments to the hard drive after she sees them once. She's doing
> the Exchange server a favor - probably unintentionally. Joe meanwhile
> keeps these large graphics file accumulating in his inbox, and he
> demands a large IOPS power from the disks where Exchange lives and from
> the Exchange server itself. The way to correct can be done a few ways.
>
> 1) "Re-Layout" the Exchange stores to spread demanding users out
> across multiple databases and storage groups in order to meets SLAs
>
> 2) User education - this almost never works but you could ask them to
> start saving files to their hard drive. You could force them to use
> PST's and the problem only gets worse - if it's important data on these
> laptops those PST's aren't getting backed up.
>
> 3) Archiving software - usually licensed through an Enterprise
> agreement or in your case you may get a good deal on a per-seat
> license. For a random example of how it works, archiving software
> shifts 80% of the inactive data on the Exchange server (depending on
> criteria you specify) off to a slower and more inexpensive storage
> medium. The other 20% is made a lot faster.
>



Relevant Pages

  • RE: Database Corruption after Exchange SP 2
    ... Please back up the Exchange 2003 Mailbox database first. ... If you are using any third-party backup program instead of NTBackup ... Press the number of the "Mailbox Store " and press ENTER. ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange Small Business 2000 will not mount stores
    ... but by following the steps in this article the database comes back as ... I start the Exchange services and about 4 hours ... I do get C1041724 when trying to mount the stores and have followed ... The point is that a hard recovery is typically run after a restore to ...
    (microsoft.public.exchange.admin)
  • Re: Exchange recovery storage groups
    ... function to recovery the mailbox store or Exchange database, ... mailbox database from the full Exchange backup. ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: restoring an old mailbox
    ... In Exchange System Manager, expand Mailbox Store, right-click Mailboxes, ... To use a Recovery Storage Group, the Active Directory topology of the ... or moved to a different database or to a different server. ...
    (microsoft.public.exchange.admin)
  • RE: What is prev1.edb and why is it 15 GB?
    ... Create new Outlook profile without using Cached Exchange. ... | Whereas the database was new and everything was available ... Had to manually mount the mail store so it ... | mailbox store, right ...
    (microsoft.public.windows.server.sbs)