In Microsoft Exchange Server, you are required to to perform hard recovery after restoring your database from an online backup. Hard recovery is a log replay process, which is similar to the soft recovery, however there are a few critical differences. If you do not complete the hard recovery process after restoring the database from backup, the restore process is not successful. In some situations, the hard recovery process fails and your database remains inaccessible even after restoring from an online backup. This behavior causes severe data loss and requires
Exchange Recovery to be sorted out.
As a practical instance of this behavior, the hard recovery process may not complete successfully with eseutil /ff command after restoring Exchange Server database (EDB file) from online backup. Additionally, you receive underwritten error message:
"Operation terminated with error -939523485 (Existing log file is not contiguous.) after 0.481 seconds."
After the above error, you see the below events in the Application Event Log of Microsoft Exchange Server:
Event Type: Warning
Event Source: ESE
Event Category: Logging/Recovery
Event ID: 458
Date: 8/30/2002
Time: 11:32:31 PM
User: N/A
Computer: ServerName
Description: Information Store (1504) Restore0003: The logfiles E0000003.log and E00.log are not in a valid sequence. Logfile replay cannot succeed if there are gaps in the sequence of available logfiles.
Event Type: Error
Event Source: ESE BACKUP
Event Category: Callback
Event ID: 904
Date: 8/30/2002
Time: 11:32:31 PM
User: N/A
Computer: ServerName
Description: Information Store (1504) Callback function call ErrESECBRestoreComplete ended with error 0xC8000263 Existing log file is not contiguous.
After this behavior of Microsoft Exchange Server, the database remains inaccessible. In order to access your EDB file in such situations, you need to find out the cause of this problem and then perform Exchange Server recovery by resolving it.
Cause
The above problem occurs if old log files are not in sequence with log, which is described in the Restore.env file. You can list out the required log files using eseutil /mh utility.
Resolution
To sort out this behavior, you need to repair and restore damaged EDB file using Exchange recovery software. These software use high-end scanning techniques to scan entire database and extract all mailboxes from it. With graphical user interface and non-destructive conduct, the Exchange recovery tools are totally easy and safe to use.
Stellar Phoenix Mailbox Exchange Recovery software repairs and restores damaged Exchange Server database in all possible corruption scenarios. The software works well with Microsoft Exchange Server 2007, 2003, 2000, and 5.5. It restores all inaccessible EDB file objects, such as emails, contacts, notes, tasks, journal, calendar entries, attachments, appointments, and more.
Article Source:
http://www.buzzle.com/articles/hard-recovery-fails-after-restoring-exchange-server-database-from-online-backup.html
