General discussion

Locked

Corrupted page in Exchange Private datab

By menendez ·
I administer an Exchange Server 5.5 400 users. My daily backup has stopped working with this events among others:

EventID:118 Source:ESE97
Direct Read found corrupted page - error 1018

EventID:105 Source:ESE97
The db engine has stopped the backup - error 1018

In spite of this the services seem to be Healthy and are running ok.
There are no hardware errors reported.
What is the best recovery path I should follow???

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Corrupted page in Exchange Private datab

by McKayTech In reply to Corrupted page in Exchang ...

The best recovery approach depends on whether you have circular logging disabled (hopefully it is). If so, you can do an on-line restore from the last good backup and all the transaction logs will play forward from that point and bring the databaseup to date. If that completes successfully, you will have no data loss.

The backup failure is to be expected when there is a corrupt page because the program is smart enough to know (usually) not to back up bad data. Because the backup doesn't complete successfully, the logs do not get truncated (if you have circular logging disabled) and life is pretty good.

If you do have circular logging enabled, it's a whole 'nother problem because some of your logs may have been overwritten since the last good backup. In that case, there is going to be some data loss.

One other note, after you do the on-line restore, it will take a LONG time for the Information Store to start but if you look at Event Viewer, you'll see that it is rolling the logs forward and will not start until that is complete.

best wishes!

paul

Collapse -

Corrupted page in Exchange Private datab

by menendez In reply to Corrupted page in Exchang ...

Thank you
Finally I moved the mailboxes to a new server cause all of my recent backups were bad!
Circular logging was on! I disabled it.
The hard repair of Priv.edb produced a loss of 40000 attachments in the store!
eventhought Esefile.exe reported only two bad Pages (8Kb. in 10 Gb. of data)
Thanks, I appreciatte any comments to
menendez@lmaasa.com

Collapse -

Corrupted page in Exchange Private datab

by Stephen Mynhier In reply to Corrupted page in Exchang ...

First, I would recommend that you stop the services and get an offline backup if your daily backups have stopped working.
Second, restoring your last backup would not rectify the problem. I would bet that the problems would pop right back up. Error 1018 is caused (almsot exclusively) by a hardware problem somewhere (or with software positioning itself between Exchange and the hardware).

When the online backup process runs, it performs a page level file check. This can be performed manually using the esefile.exe utility that is found on the Exchange SP3 CD. This will scan at about 1 GB/min and tell you how many bad pages that you have (i.e. the extent of your problem).

Some of the most common causes of 1018 errors:
Write-back caching enabled on your drive -- this should be disabled!
SCSI drive going bad
SCSI controller failing
Bad cable to SCSI controller
Device driver bugs
RAM going bad
Anti-virus software interfering with the write to disk

Some of these will also pop up events in the System log (but not necessarily). I would check the WB caching first, and contact your server vendor for a utility disk to give a diagnosis of your server. Most (if not all) hardware vendors like Dell or Compaq are familiar with Exchange's Error 1018 and will send you the utility if you tell them that you are having this problem.

After you have diagnosed the problem and fixed it, then you get to fix the damage within the database. What I would recommend:
1) Move the priv.edb and pub.edb to a recovery server
2) Restore your last good backup on your production server
3) Hard repair the databases on the recovery servers
4) On the recovery server, ExMerge out the data between your last backup and now. ExMergethis data into the production server.
5) Using a client on your recovery server export the public folders (if any) to PSTs and import them back into the production server

Collapse -

Corrupted page in Exchange Private datab

by menendez In reply to Corrupted page in Exchang ...

Thank you
Finally I moved the mailboxes to a new server cause all of my recent backups were bad!
Circular logging was on! I disabled it.
The hard repair of Priv.edb produced a loss of 40000 attachments in the store!
eventhought Esefile.exe reported only two bad Pages (8Kb. in 10 Gb. of data)
Thanks, I appreciatte any comments to
menendez@lmaasa.com

Collapse -

Corrupted page in Exchange Private datab

by menendez In reply to Corrupted page in Exchang ...

This question was closed by the author

Back to Software Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums