Resolving Exchange Database Restore Problems


If the restore process fails, troubleshoot the problem as soon as possible. Sometimes, performing the restore process again corrects the problem. Other times, you might have to repair one or more Exchange databases. For information about how to repair Exchange databases, see "Repairing Exchange Databases."

For general information about how to search and troubleshoot restore errors, see "Checking the Success of a Completed Restore Job" in Using Backup to Restore Your Data.

If you experience problems with the databases that you tried to restore, check the application log for errors, and then search the Microsoft Knowledge Base for specific solutions to those errors.

Troubleshooting Failed Restore Processes

If the restore process is not completed successfully, search for errors in the Backup status window, the Backup restore log, and the logs in Event Viewer. These errors might help you determine the cause of the failure.

Because Exchange relies heavily on your Windows Server 2003 operating system, look for both Exchange-specific errors in the event logs and errors for non-Exchange components that Exchange relies on. Also consider hardware errors. For example, a bad page file on a hard disk drive can prevent Exchange from moving forward writing to the database.

After you have identified errors in the event log that you suspect might be the cause of the failed restore, search the Microsoft Knowledge Base for those specific errors.


If one or more Exchange database or log files are damaged or missing, the application log might include the following error: Error -1216 (JET_errAttachedDatabaseMismatch)


For information about how to troubleshoot database restore issues that include the 1216 error, see Microsoft Knowledge Base article 296843, "XADM: Error -1216 Recovering an Exchange 2000 Database."

If you cannot resolve the problems that are preventing you from restoring your Exchange databases, contact Microsoft Help and Support.