Exchange Server Forums

Corrupted store, difficulty fixing

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2003] >> Information Stores >> Corrupted store, difficulty fixing

Page: [1]

Message

<< Older Topic Newer Topic >>

Corrupted store, difficulty fixing - 31.May2005 8:45:00 AM

AmiraLF

Posts: 9
Joined: 6.Feb.2005
From: Virginia Beach
Status: offline

Hello, I have a Exchange 2003 server running a 6gb private mailbox store and a small (about 100mb) public store.
I am using NTbackup to back up the information store.
Reviewing my event log, I have received many errors of this type:

ESE 474
Information Store (2756) First Storage Group: The database page read from the file "C:\Program Files\Exchsrvr\mdbdata\pub1.edb" at offset 57397248 (0x00000000036bd000) for 4096 (0x00001000) bytes failed verification due to a page checksum mismatch. The expected checksum was 340394497 (0x144a0201) and the actual checksum was 2689204737 (0xa04a0201). 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.

ESE , error 705
Information Store (2756) First Storage Group: Online defragmentation of database 'C:\Program Files\Exchsrvr\mdbdata\pub1.edb' terminated prematurely after encountering unexpected error -1018. The next time online defragmentation is started on this database, it will resume from the point of interruption.

These errors have been going on for a few weeks now and restoring from backup is not an option.

Because the NTbackup has been unsuccessful, there are about 400 unmerged .log files in the MDBDATA directory, 5mb each.

I dismounted the stores this weekend to try and do an integrity repair on them unsuccessfully. I first tried to do a "eseutil /recovery e00" to merge the log files. This *completed successfully*, but only took a few seconds, and all the log files are still there.

I then re-mounted the stores and did an isinteg on both. The priv store went fine (two errors fixed), but the public store failed in the middle of the isinteg. I could not get it to complete. Sounds like major corruption.

---

So anyways, at this point I need help. From the errors, I would believe that the problem is corruption of the public folders only, but I find it hard to believe that I have 400 log files just for the public folders? Or will a problem with public folders also affect the private mail logs?

I can do a couple different things:
1. Remove the log files from the MDBDATA directory and run a eseutil /repair. I am concerned that I will loose data if I do this - can anyone confirm if I will or not?
2. If the problem is only with public folders, I can export them to a PST file, run a recovery on the pub1.edb, then re-import them.
3. If the situation is dire enough, I can bring up a second exchange 2003 server and move everything to it through ESM. I may have to do this anyways in the future because it seems I might have hardware issues?
4. Other options unknown to me.

Please advise.
Thank you!

Amira

Post #: 1

Featured Links*

RE: Corrupted store, difficulty fixing - 31.May2005 6:01:00 PM

a.grogan

Posts: 1917
Joined: 12.Apr.2005
From: London
Status: offline

I had almost the same problem 2 years ago.
What I did was create a PST and copy all of the required content from the Public Stores to the PST.

I then unmounted the Public store and deleted all of the Database and log files for the public store.
I then remounted the store which forced a re-creation of the database and logs, and I then copied the data from the PST back to the public store.

I then updated all of the store policies to reflect the Public Folders and I then followed the instructions for resetting the system folders.

That solved the problem.

(in reply to AmiraLF)

Post #: 2

RE: Corrupted store, difficulty fixing - 1.Jun.2005 1:14:00 PM

AmiraLF

Posts: 9
Joined: 6.Feb.2005
From: Virginia Beach
Status: offline

How can you tell the difference between log files for the public store and the private store? All my log files start with E00xxxxx.log that are in the MDBDATA directory.

(in reply to AmiraLF)

Post #: 3

RE: Corrupted store, difficulty fixing - 2.Jun.2005 3:00:00 PM

a.grogan

Posts: 1917
Joined: 12.Apr.2005
From: London
Status: offline

You could move the public databases to another folder using the exchange system manager - this will also move the logs automatically - this will help you know the difference.
Other than that - you could just delete the databases - and leave the logs.

A

(in reply to AmiraLF)

Post #: 4

RE: Corrupted store, difficulty fixing - 6.Jun.2005 6:55:00 PM