If the repair encounters a page that is damaged (for example, an invalid checksum caused by a modification to the page that was not preformed by Jet) it deletes the page (-1018). When this happens, critical data may be lost after the repair finishes. This data may be part of an e-mail message, a calendar appointment, a note, an attachment, or in the worst-case scenario, part of a system table.
If that system table is the attachment table, every user on the server may lose the attachments to their messages. This is only one possible scenario, but if there are damaged pages in the database, data will be lost following a hard repair.
Important It is always best to restore from a backup whenever possible.
If you restore from a backup, you ensure that you have a good, clean, stable, database that will start and run on your server. In almost every circumstance, it is faster and more reliable to restore from a backup than to perform a hard repair on the database. This is because the repair runs at approximately 4 to 6 gigabytes (GB) per hour, and you must run the Isinteg process after the repair, which runs at approximately 3 to 6 GB per hour. (These rates are average; performance may vary depending on how many passes the repair has to make on your database and the speed of the hardware.)
For example, if you use the fastest possible hardware setup, a 50-GB database requires approximately 8 hours for repair and approximately 8 hours for the Isinteg process, for a total of 16 hours. If you use a typical Wide SCSI-connected digital linear tape (DLT) 35/70, which averages around 3 megabytes (MB) per second for restoration, the same database needs approximately 5 hours for restoration. That is a time savings of 11 hours. Extremely high speed "snapshot" type backup systems, such as the system from EMC Corporation, can restore a database of this size in a matter of minutes.
If you have no backup, and no other option but to run a hard repair on your database, follow these steps:
- Run a hard repair on the database by using Eseutil /p or Eseutil /d /r.
- Defragment the database by using Eseutil /d. Offline defragmentation creates a new physical database structure and moves the existing data to that structure.
- Check the consistency of the database by using Isinteg -fix. You may need to run Isinteg several times until the summary report returns no errors.
The Isinteg utility fixes the logical problems that may arise when you run a hard repair:
- For the Exchange Server 4.0 and 5.0 private information store, run the following command:isinteg -fix -pri
- For the Exchange Server 4.0 and 5.0 public information store, run the following command:isinteg -fix -pub
- For the Exchange Server 5.5 private information store, run the following command:isinteg -pri -fix -test alltests
- For the Exchange Server 5.5 public information store, run the following command:isinteg -pub -fix -test alltests
For more information about Exchange disaster recovery, click the following article number to view the article in the Microsoft Knowledge Base:
- The information store either will not stop or stops responding.
- The information store stops accepting mail from the message transfer agent (MTA).
- E-mail remains in the Outboxes of the users.
- The Store.exe program runs with very high CPU use with no load on the server.
- The Store.exe program generates an access violation if there is a heavy load.
- Users cannot open e-mail attachments or e-mail messages.
If Isinteg is run multiple times and does not correct the database corruption, you must use the Exmerge utility to extract data from one database and place it in another database:
eseutil /mh x:\exchsrvr\mdbdata\pub.edb |more
Copyright (C) Microsoft Corporation 1991-1999. All Rights Reserved.
Initiating FILE DUMP mode...
Format ulMagic: 0x89abcdef
Engine ulMagic: 0x89abcdef
Format ulVersion: 0x620,2
Engine ulVersion: 0x620,2
DB Signature: Create time:4/5/2000 17:48:52 Rand:769046 Computer:
Last Objid: 184
Scrub Dbtime: 0
Scrub Date: 00/00/1900 00:00:00
Repair Count: 1
Repair Date: 2/20/2000 10:48:50