Re: Information store error

From: Andrei Marinescu [MSFT] (andreima_at_online.microsoft.com)
Date: 06/09/04


Date: Wed, 9 Jun 2004 00:18:29 -0700

It looks like you have a physical corruption on the drive, in the STM file.
You should check the System Event Log to see if there are hardware related
events, especially disk related, etc.. Most likely there is an attachment
affected but not more then that (it is hard to find which message/user at
this point though).

Separate from this, in order to get the database back you can try the
following options (you might want to replace the drive first but that's you
call):
- restore from the last good backup you have. Assuming you don't have
circular logging on (and you didn't delete them manually), you should have
all the logs since the last backup. Before restoring you can take the SG
offline and check them (check if the oldest is since the last backup, run
eseutil /ml e00 to check the logs themselves). I would recommend to make a
copy of the database files as well before the restore (take the database
offline, check for consistent state using eseutil /mh, then copy or move
them). This will be the only solution which will not have any data lost
including the corrupted attachment.
- run an offline defrag on the database. This will keep your attachment
corrupted but will recomputed the checksum and allow backup to keep going.
To do this, unmount the database, check it's consistency (eseutil /mh) and
the run an offline defrag (eseutil /d)
- exmerge all users to a different database, then, once empty, delete the
database (from ESM). This will have the same result as above most likely in
terms of data preservation.

Hope this helps,
--andrei
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"Steve Calnon" <steve@aceonline.com.au> wrote in message
news:u3E0YzeTEHA.3944@tk2msftngp13.phx.gbl...
> Thanks for your time
>
> I am also getting the following errors in my event log. They are -
>
> these first
>
> Information Store (3332) The streaming page read from the file "C:\Program
> Files\Exchsrvr\mdbdata\priv1.stm" at offset 2275921920
(0x0000000087a7d000)
> for 4096 (0x00001000) bytes failed verification due to a page checksum
> mismatch. The expected checksum was 2172834955 (0x8182d48b) and the actual
> checksum was 4036267172 (0xf0948ca4). The read operation will fail with
> error -613 (0xfffffd9b). If this condition persists then please restore
the
> database from a previous backup.
>
> then this
>
> Information Store (3332) 18728f59-b2e9-424e-9091-b8454dc6a331: Ending the
> backup of the file C:\Program
> Files\Exchsrvr\mdbdata\priv1.stm. Not all data in the file has been read
> (read 2275868672 bytes out of 3628081152 bytes).
>
> I have since exmerged all the users mailboxes and they all seem to be the
> same size and when Ihave opened the pst files they all appear to contain
the
> correct data.
>
> A restore is an option but I was hoping not to have to as last fridays
> backup failed with the same and I dont really want to have to go back
> another friday..... ?
>
> Steve.
>
>
>
> "Andrei Marinescu [MSFT]" <andreima@online.microsoft.com> wrote in message
> news:OZ%23u1ReTEHA.3476@tk2msftngp13.phx.gbl...
> >
> > Steve,
> > Can you check the Application EventLog for other errors? We might get a
> > better idea what went wrong during backup and go from there.
> >
> > --andrei
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > Use of included script samples are subject to the terms specified at
> > http://www.microsoft.com/info/cpyright.htm
> >
> >
> > "Steve Calnon" <steve@aceonline.com.au> wrote in message
> > news:eRIooScTEHA.1732@TK2MSFTNGP09.phx.gbl...
> > > Hi,
> > >
> > > I have an exchange 2000 sp3 server running which has been ok up until
a
> > few
> > > days ago. the disk the exchsrvr program lives on ran out of space. I
am
> in
> > > the process of cleaning up some space now but when I try and run a
back
> up
> > I
> > > get the error -
> > >
> > > Backup started on 9/06/2004 at 7:55 AM.
> > > WARNING: Portions of "\Mailbox Store (FILESERVER)" cannot be read.
The
> > > backed up data is corrupt or incomplete.
> > > This file will not restore correctly.
> > > Backup completed on 9/06/2004 at 8:16 AM.
> > >
> > > All the mailboxes seem to be ok when opened. is there some kind of
> > database
> > > check tool I should be running?
> > >
> > > Any help would be appreciated.
> > >
> > > steve
> > >
> > >
> >
> >
>
>



Relevant Pages

  • RE: Information Store Corrupted
    ... depend on the kind of storage you are using. ... If the corruption is a database structure page you will not ... The backup by definition doesn't include the corrupted items. ... Category: Database Page Cache ...
    (microsoft.public.exchange.admin)
  • Re: Copying Tables
    ... copy of my tables in another database on a different machine. ... Should I use transferdatabase to get the info into the backup ... "Corruption will only manifest itesl ... want a transaction by tranaction copy of my database so that I ...
    (microsoft.public.access.formscoding)
  • Re: Copying Tables
    ... copy of my tables in another database on a different machine. ... Should I use transferdatabase to get the info into the backup ... "Corruption will only manifest itesl ... want a transaction by tranaction copy of my database so that I ...
    (microsoft.public.access.formscoding)
  • Re: Copying Tables
    ... of my tables in another database on a different machine. ... Should I use transferdatabase to get the info into the backup ... "Corruption will only manifest itesl ... want a transaction by tranaction copy of my database so that I ...
    (microsoft.public.access.formscoding)
  • Re: Corrupt Mailbox Store
    ... Either of these steps will eliminate the corruption. ... If the database does not mount then you will have to resort to restoring the ... You will want to use the backup log as well as the application log to ... determine if this is a hardware problem. ...
    (microsoft.public.exchange2000.information.store)