Event 619 is logged after an online restore operation of an Exchange Information Store database is performed

This article discusses some of the causes of Microsoft Exchange Server information store restoration issues that are indicated by event ID 619. This article also discusses some ways to resolve these issues.

This event is logged as follows in the application log of Event Viewer:

Event Type: Error
Event Source: ESE
Event Category: Logging/Recovery
Event ID: 619
Description: Information Store attempted to attach database D:\Exchsrvr\MyStorageGroup\MyDatabase.edb but it is a database restored from a backup set on which hard recovery was not started or did not complete successfully. For more information, click http://search.support.microsoft.com/search/?adv=1.

Event ID 619 is an Extensible Storage Engine (ESE) event that indicates that an online restore operation of an exchange information store database was performed. This event ID indicates that although the information store database was restored, the hard recovery operation was not run, or the hard recovery operation was not completed successfully.

Case 1: The Last Backup Set Check Box Is Not Selected

This issue may occur if you do not select the Last Backup Set check box during the restore operation. When you do not select the Last Backup Set check box, the hard recovery process does not run.

To resolve this issue, run the hard recovery process manually by using the following command: For additional information about how to resolve this issue, click the following article numbers to view the articles in the Microsoft Knowledge Base:

Case 2: Hard Recovery Runs but Does Not Complete

This issue may occur if the hard recovery is tried during the online restore process, but the hard recovery is not completed. This issue may also occur if you try to run the hard recovery manually by using the eseutil /cc command, but the hard recovery is not completed.

When hard recovery is run automatically or manually and it is not completed, an error is generated. The error code specifies why the hard recovery was not successful. The following list contains more information about these error codes:

• Error Code -939523485

  Cause

  You run the eseutil /cc command and it is unsuccessful. You receive the following error code: -939523485. This is the same as Error -556 or the JET_errGivenLogFileIsNotContiguous error. This error is caused by old log files that are out of sequence with the log that is specified in the Restore.env file.

  Resolution

  For additional information about how to resolve this problem, click the following article number to view the article in the Microsoft Knowledge Base:
  328639 XADM: Hard Recovery May End with Error -939523485
• Error Code -107

  Cause

  You run the eseutil /cc command and it is unsuccessful. You receive the following error message:
  The restore environment information isn't found. Operation terminated with Error -107.
  Error -107 is a generic error that corresponds to the JET_errInternalError error. This is a fatal internal error that can have many causes. One of the causes is that the administrative group name (and the legacyExchangeDN attribute for the administrative group) does not match the administrative group name of the production domain.

  Resolution

  For additional information about how to resolve this issue, click the following article number to view the article in the Microsoft Knowledge Base:
  324606 XADM: How to Use Legacydn.exe to Correct Exchange Organization or Administrative Group Names
  Microsoft recommends that you use the Legacydn tool only in a test environment. The Legacydn tool only works in a single domain controller environment.
• Error Code -566

  Cause

  You run the eseutil /cc command and it is unsuccessful. You receive the following decimal error code: Error -566. The error message that corresponds to this decimal error is JET_errDbTimeTooOld. The description from the Extensible Storage Engine 98 source code comments describes this error as follows:
  dbtime on page is smaller than dbtimeBefore in record

  Resolution

  To resolve this issue, follow these steps:
  1. Restore the Exchange databases on the production server from an earlier backup.
  2. Run the eseutil /p command against the database from the online restore operation on the recovery server.
  3. Run the esutil /d command against the database from the online restore operation on the recovery server.
  4. Run the isinteg -fix command against the database until you receive one of the following:
     • Zero warnings, zero errors, and zero fixes
     • The same result two times
  5. Use the Microsoft Exchange Mailbox Merge program (ExMerge) on the recovery server to move out only the messages that are newer than the messages that are contained in the earlier backup that you restored to the production server.
  6. Use the Microsoft Exchange Mailbox Merge program to move the newer messages from the recovery server to the production server.
  For additional information about how to use ExMerge to extract mail from a corrupted mailbox store, visit the following Microsoft Web site:
• Event ID 619

  Cause

  You restore a backup that is made from a Microsoft Exchange 2000 Server Service Pack 1 or a Microsoft Exchange 2000 Server (with no service pack installed) online backup to a Microsoft Exchange 2000 Server Service Pack 2 or later computer. The restore operation fails because a log format change is implemented in Exchange 2000 Service Pack 2 to support the elimination of the update file. If you try to mount the databases manually after the restoration, event ID 619 is logged in the application log of Event Viewer. For additional information about this issue, click the following article numbers to view the articles in the Microsoft Knowledge Base:
  316794 XADM: Exchange 2000 Service Pack 2 Does Not Allow You to Restore Exchange 2000 or Exchange 2000 Service Pack 1
  316796 XADM: A Patch File Is Not Created During Backup
  
  
  To remove an Exchange 2000 Service Pack 2 upgrade and replace it with an earlier version of Exchange 2000, you must restore the original system state, file system, transaction logs, and database files.