Re: Priv1.edb and stm size cannot reduce after eseutil /d

From: Michael Barta [MSFT] (mbarta_at_online.microsoft.com)
Date: 03/09/04


Date: Tue, 9 Mar 2004 11:19:45 -0600

A defrag should not have deleted any messages. Did you run any other
switches?

Are the messages visible with any other clients?
POP3, OWA, etc?

-- 
Michael Barta [MSFT]
Microsoft Exchange Support
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Calvin" <kg_it_guy@yahoo.ca> wrote in message
news:OASvFhfBEHA.2600@TK2MSFTNGP09.phx.gbl...
> Question for Michael, after many hours of defragging the database and
> bringing it online, database shrunk from 13GB to 12GB but all messages
> except the directory structure are all gone.  Any idea Michael?
>
> Thanks
>
>
> "Horace" <aa@bb.com> wrote in message
> news:#J3qbwSBEHA.2600@TK2MSFTNGP09.phx.gbl...
> > Thank you.
> >
> > "Michael Barta [MSFT]" <mbarta@online.microsoft.com> ¦b¶l¥ó
> > news:%23zMkacSBEHA.3776@tk2msftngp13.phx.gbl ¤¤¼¶¼g...
> > > You should wait for online maintenance to complete after deleting
large
> > > amounts of messages. If you delete 3-4Gigs of mail and run the defrag
> > before
> > > online maintenance marks the free space, you will not recover that
> space.
> > >
> > > You will see 1221 events in the application log that will tell you how
> > much
> > > space the offline defrag will recover. Once you see the 3-4 gigs
listed
> in
> > > the 1221, the offline defrag will reduce in size.
> > >
> > > You can also adjust the online maintenance schedule on the properties
of
> > the
> > > mailbox store, database tab.
> > >
> > > --
> > > Michael Barta [MSFT]
> > > Microsoft Exchange Support
> > >
> > > Please do not send e-mail directly to this alias. This alias is for
> > > newsgroup purposes only.
> > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > >
> > > "Horace" <aa@bb.com> wrote in message
> > > news:O2BLR9RBEHA.2584@TK2MSFTNGP12.phx.gbl...
> > > > Dear ALL,
> > > >
> > > > My priv1.edb cannot reduce the size by using eseutil /d, I am using
> > > standard
> > > > edition, and now the priv1.edb is 12 GB already, before the
> defragment,
> > I
> > > > deleted nearly 3-4GB in mailboxes,
> > > > what is the potential problem ? Thank you.
> > > >
> > > > Regards,
> > > > Horace
> > > >
> > > >
> > >
> > >
> >
> >
>
>


Relevant Pages

  • Re: Priv1.edb and stm size cannot reduce after eseutil /d
    ... If you delete 3-4Gigs of mail and run the defrag ... > online maintenance marks the free space, you will not recover that space. ... the offline defrag will reduce in size. ... > Please do not send e-mail directly to this alias. ...
    (microsoft.public.exchange.admin)
  • Re: Priv1.edb and stm size cannot reduce after eseutil /d
    ... If you delete 3-4Gigs of mail and run the defrag before ... online maintenance marks the free space, you will not recover that space. ... Please do not send e-mail directly to this alias. ... "Horace" wrote in message ...
    (microsoft.public.exchange.admin)
  • Re: Priv1.edb and stm size cannot reduce after eseutil /d
    ... > A defrag should not have deleted any messages. ... > POP3, OWA, etc? ... > Please do not send e-mail directly to this alias. ... Any idea Michael? ...
    (microsoft.public.exchange.admin)
  • Re: Priv1.edb and stm size cannot reduce after eseutil /d
    ... I have never heard of a defrag causing this type of an issue. ... Please do not send e-mail directly to this alias. ... This posting is provided "AS IS" with no warranties, and confers no rights. ... >> Microsoft Exchange Support ...
    (microsoft.public.exchange.admin)
  • Re: Sudden growth to the Priv DB, unable to shrink using offline d
    ... then you have to wait for the in progress defrag to complete as ... mailboxes after DIR has expired. ... If items were deleted and retension time is zero then an offline defrag ... The next online maintenance after the deleted items retention period ...
    (microsoft.public.exchange.admin)