SBS alows for increasing the store limits in the same way that Exchange 2003 standard does. There is little if any difference between the Exchange 2003 Standard and Exchange 200 SBS
As long as you are on the right service pack level and have set the reg keys you can have stores up to 75GB I dont have any suggestions as to what may have changed but there is always a chance that the reg key has been turned back to default. Graeme On Fri, Dec 19, 2008 at 4:36 PM, Erik Goldoff <egold...@gmail.com> wrote: > Hmmmm, not an SBS expert (actually not even a fan) but does that version > of Exchange get rid of the 16gb store limit that Exchange Enterprise does ? > > > > Erik Goldoff > > *IT Consultant* > > *Systems, Networks, & Security * > > > ------------------------------ > *From:* Jim Majorowicz [mailto:jmajorow...@gmail.com] > *Sent:* Friday, December 19, 2008 11:11 AM > *To:* NT System Admin Issues > *Subject:* Exchange Puzzle > > I've got a client (SBS 2003 SP2) that has a fairly large DB for the > Private store. I had set the DB Size Limit in GB to 64 GB, but yesterday at > 5 AM it spontaneously reverted back to 16GB after failing a defrag and of > course dismounted the store. When I checked to make sure it was working > properly after changing the setting back I couldn't help but notice some > discrepancies in the numbers. > > > > The 9690 event that took the DB offline shows the size at 48 GB. At 8 am, > when the 1216 and 9685 events that report the failure to mount (done before > coffee or even a check of the event logs), the size reported was 53 GB. The > 1216 Event after I fixed the DB Size Limit in the registry, still said 53 > GB. > > > > To really confuse me, the Usage Report (Which is what I use to monitor the > size of the store in the first place) shows the total of all mailbox sizes > to be 38,623.8 MB, which is about 37.5 GB... > > > > In the effort of full disclosure, this server is bane of my existence. It > eats SCSI drives for lunch on an almost quarterly basis. It has had a > critical failure in the past year that forced me to restore from backup. > I've been hesitant to ESEUTIL this store because of the trouble I had > getting the damn thing back online after the restore. > > > > Still, I'm a little worried. I don't have anything in either the APP or > SYS logs that show what the heck happened at 5 AM to change the DB Size > Limit, and I'm a little hesitant to blow off a 16 GB gap in reported size > differences as simple whitespace. > > > > Anybody have any insight, or should I just run the ESEUTIL and hope it > cleans up the issue? > > > > > > > > > > > > > > > -- Carbon credits are a bit like beating someone up on this side of the world and sponsoring one of those poor starving kids on the other side of the world to make up for the fact that you're a complete shit at home. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
