Re: Exchange recovery questions...

From: Scott (mcdonsco_at_yahoo.com)
Date: 02/11/04 

Date: Wed, 11 Feb 2004 14:58:50 -0800

hey, one last quick question for you. Veritas never once reported any errors
with the exchange store when backing it up - now it's reporting an error
that the database is corrupted every time I try and restore it. IT restores,
but just reports that it's corrupted and thus the recovery exchange server
wont mount it.

I know I shouldn't do this, trust me I know, but the only system/drives I
have available to do this with had only a 40GB drive the store is 45GB so I
compressed the drive to get it to fit (which it does now). Is this the sole
reason it says it's corrupted, or should this still work? 

-- 
Scott McDonald
"Ken Ewert [MSFT]" <MS-kene@no.microsoft.spam.com> wrote in message
news:%232qzPGP8DHA.2472@TK2MSFTNGP10.phx.gbl...
> no problem.   I am going to over simplify things here so hopefully you
will
> pick up on what I'm saying.
>
> Exchange's database uses a transactional logging scheme (like other
> traditional database application).      Thus as changes / transactions
occur
> to the database , the changes are recorded in transaction logfiles as
well.
> If you restore from a backup, you have 2 choices.   1) restore the
database
> as it was at the time of the backup   2) restore the database and replay
the
> transactions that occurred *SINCE* the backup was done and therefore you
can
> mature the database back upto the point of failure.
>
> In answer to your question below,  Yes.. .without the use of ScanOST, the
> mail will remain in the local OST.
>
>
> Thx
> Ken
>
> "Scott" <mcdonsco@yahoo.com> wrote in message
> news:OZXwtPO8DHA.452@TK2MSFTNGP11.phx.gbl...
> > I'm not sure what you mean by "rolling logs forward"?
> >
> > Without using scanost.exe does that just mean that the emails would
remain
> > in the users ost on their system and not be copied back to the server
> store?
> > Then if scanost.exe is used once it's finished their outlook client will
> > copy the emails from the OST to the server?
> >
> > Sorry, I'm very very new to exchange and thsi is my first having to deal
> > with a recovery. Thanks for your help.
> >
> > -- 
> > Scott McDonald
> > "Ken Ewert [MSFT]" <MS-kene@no.microsoft.spam.com> wrote in message
> > news:eoGa2KO8DHA.360@TK2MSFTNGP12.phx.gbl...
> > > If you are saying that the exchange server as recovered to a previous
> > point
> > > in time (ie restored to the last backp without rolling logs forward)
> then
> > > those messages will be left in the local copy of the client.   There
is
> a
> > > tool in the Outlook binaries called ScanOST.exe I believe that if you
> run
> > it
> > > against that OST it will end up re-syncing the "local only" content
back
> > > upto the server.
> > >
> > > If you are saying that the database was not recoverd but instead a new
> > > database started, then Outlook (in cached mode) will not re-connect to
> the
> > > new database / mailbox .    Again, same way to recover the data  via
> > ScanOST
> > > tool  OR  you can move your OST content to a PST, then re-create your
> > > Outlook profile to point to the "new" mailbox and then mount the PST
to
> > the
> > > new mailbox and drag the content back into your new OST and push it
upto
> > the
> > > server.
> > >
> > > Thx
> > > Ken
> > > "Scott" <mcdonsco@yahoo.com> wrote in message
> > > news:uNhbG3N8DHA.2656@TK2MSFTNGP11.phx.gbl...
> > > If users are using outlook 2003 in cache mode and the exchange server
> goes
> > > down taking some data with it in store/database corruption, when it
> comes
> > > back online will exchange delete the emails from the users ost file
> > thinking
> > > "I don't have them so they shouldn't either" or will it copy those
> emails
> > > back into the exchange store thus recovering those emails from the
> client
> > > computers?
> > >
> > > I'm curious because we currently run outlook 2000 and our exchange
> server
> > > went down last week and there was some corruption in the store. Fixing
> > that
> > > lost a significant amount of data. I configured a recovery server only
> to
> > > find that the store had been corrupted for a few days before it went
> down
> > > (and nicely enough Veritas recognized and reported the store was
corrupt
> > on
> > > restore, but not when it had backed it up). So I was thinking outlook
> 2003
> > > could prevent this from being a problem if it ever happens again, but
> not
> > if
> > > exchange will just delete the emails from the users ost file once it's
> up
> > > and running again.
> > >
> > > Thanks!
> > >
> > > -- 
> > > Scott McDonald
> > >
> > >
> >
> >
>
>

Relevant Pages

  • Re: Exchange Disaster Recovery Server
    ... The backup server is setup also in the lab so I ... >>> The Microsoft Exchange Server computer is not available. ... >>> Microsoft Exchange Server Information Store ...
    (microsoft.public.exchange2000.admin)
  • Re: cant mount information store
    ... I then reinstalled exchange and then installed exchange 2003 ... Information Store First Storage Group: Database recovery failed ... Microsoft Exchange Information Store. ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange recovery questions...
    ... that the database is corrupted every time I try and restore it. ... but just reports that it's corrupted and thus the recovery exchange server ... have available to do this with had only a 40GB drive the store is 45GB so I ...
    (microsoft.public.exchange2000.admin)
  • RE: Exchange restore on SBS2003 from SBS2000 backup
    ... I agree with you that using ExMerge is a good ... How to recover or restore a single mailbox in Exchange 2000 Server ... >> the Exchange database from the SBS 2000 backup to the SBS 2003 Server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Help! Trouble restoring after file system corruption removed files on drive with Exchange datab
    ... this shows database was in dirty shutdown state. ... How to use Eseutil to test transaction log files for damage in Exchange ... <"Information Store First Storage Group: ... Create a Recovery Storage Group. ...
    (microsoft.public.exchange.admin)
Loading