Re: Information Store Corrupted
- From: "Mark Arnold [MVP]" <mark@xxxxxxxx>
- Date: Tue, 24 Apr 2007 08:36:47 -0700
You shouldn't have kept your users offline for that length of time.
All you had to do was to stop the store, pull all the files out of the
production directories and start a blank store to get the users up and
running with a "dial-tone" service. Then you could have created the
Recovery Storage Group and added your problem store into it and
started your repair operations on it.
1018 errors are often down to disk problems, especially following
Exchange 2003 SP1 (what are you on?) when the "bit flip" error was
largely resolved.
Can you see if you can get that store mounted in the RSG.
Another option depends on whether you are running Enterprise or
Standard. If you are on Enterprise the easiest thing to do is to move
all the mailboxes to another store on a different set of disks from
the ones the current store is on.
On Tue, 24 Apr 2007 08:08:05 -0700, Shanthi
<Shanthi@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I am using Exchange 2003 on Win2K3 server and backup application is Veritas.
My backup method is for
Daily - differential backup of Information Stores
Weekly - full backup of Information Stores
When I tried to run weekly backup an error has come as "Information Store -
is a corrupt file. This file cannot verify."
I checked the event log on Exchange server, it threw application error with
Source : ESE
Category : Database Page Cache
Event Id : 474
Description :
Information Store (2712) First Storage Group: The database page read from
the file "E:\Exchange\mdbdata\priv1.edb" at offset 409464832
(0x000000001867f000) (database page 99966 (0x1867E)) for 4096 (0x00001000)
bytes failed verification due to a page checksum mismatch. The expected
checksum was 3567500155055337822 (0x31824e7d5639715e) and the actual checksum
was 3711585678364162506 (0x338233827852b9ca). The read operation will fail
with error -1018 (0xfffffc06). If this condition persists then please
restore the database from a previous backup. This problem is likely due to
faulty hardware. Please contact your hardware vendor for further assistance
diagnosing the problem.
I tried some search on Microsoft online technical articles and found useful
informations. Below are the activities performed to resolve the issue;
Step 1: Taken a copy of all raw database.
Step 2: Run eseutil /p for repair database.
Step 3: Taken a backup of repaired database
Step 4: Run eseutil /d for defragment database.
Step 5: Taken a backup of defragmented database.
Step 6: Run Isinteg -fix -test alltests for checking integrity.
Step 7: Found no error in integrity checking.
Step 8: Run ntbackup on exchange server and completed with no issues.
Step 9: Tried full backup of information store by using veritas backup exec
and completed succesfully.
Please do let me know whether the way I performed is correct and also why
this kind of errors are coming. I kept my mail users on waiting for 26 hours
(such a huge down time)
Shanthi
.
- Prev by Date: Exchange 2007 forest prep
- Next by Date: Re: RUS Issue 2003?
- Previous by thread: Re: Information Store Corrupted
- Next by thread: Re: Information Store Corrupted
- Index(es):
Relevant Pages
|
