Blogs >> Education & Books >>
What Causes Hard Recovery Failure in Exchange Server?
In Microsoft Exchange Server, you must replay the log file after restoring your EDB (Exchange Server database) from an online backup. This process is known as Hard Recovery. It helps you to recover your Exchange Server database in case of database corruption or database failure. However, in some situations, the Exchange Server hard recovery fails and the database remains in inaccessible and unusable state. At this point, you need to repair and restore the corrupt database using advanced Exchange Server Recovery tools.
As a practical example of this problem, the hard recovery of Exchange Server with Eseutil /cc may fail and you come across the below error message:
“Operation terminated with error -939523485 (Existing log file is not contiguous.) after 0.481 seconds.”
At the same time, you may see any of the following Events in the Application Event Log of Microsoft Exchange Server:
1.Event Type: Information
Event Source: ESE
Event Category: General
Event ID: 101
Date: 8/30/2002
Time: 11:32:31 PM
User: N/A
Computer: ServerName
Description: Information Store (1504) The database engine stopped.
For more information, click http://search.support.microsoft.com/search/?adv=1.
2.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.
For more information, click http://search.support.microsoft.com/search/?adv=1.
After this behavior, you may come across critical data loss situations. To retrieve data in such cases, you need to figure out the cause of this behavior and perform Microsoft Exchange recovery by fixing it.
Root of the problem:
You may come across this problem if the old log files are not in sequence with log, which is mentioned in the Restore.env file. You can file all the required log files using Eseutil /mh utility.
Resolution:
To fix this problem, follow the below steps:
1.View the content of Restore.env file using Eseutil /mh utility.
2.Record range of log files.
3.Remove the log files that are out of range.
If the above method does not work, you need to repair and restore the damaged Exchange Server database using third-party Exchange recovery software.
The Exchange Recovery tool are powerful enough to thoroughly scan entire database and extract all inaccessible data from it. They have rich and interactive graphical user interface to ensure easy recovery in all corruption scenarios.
Stellar Phoenix Mailbox Exchange Recovery is the most advanced and powerful exchange database recovery utility to offer assured recovery of damaged database. The exchange 2003 recovery software restores all EDB file objects, such as emails, notes, contacts, tasks, journal, attachments, and appointments. It works with Microsoft Exchange Server 2007, 2003, 2000, and 5.5.
As a practical example of this problem, the hard recovery of Exchange Server with Eseutil /cc may fail and you come across the below error message:
“Operation terminated with error -939523485 (Existing log file is not contiguous.) after 0.481 seconds.”
At the same time, you may see any of the following Events in the Application Event Log of Microsoft Exchange Server:
1.Event Type: Information
Event Source: ESE
Event Category: General
Event ID: 101
Date: 8/30/2002
Time: 11:32:31 PM
User: N/A
Computer: ServerName
Description: Information Store (1504) The database engine stopped.
For more information, click http://search.support.microsoft.com/search/?adv=1.
2.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.
For more information, click http://search.support.microsoft.com/search/?adv=1.
After this behavior, you may come across critical data loss situations. To retrieve data in such cases, you need to figure out the cause of this behavior and perform Microsoft Exchange recovery by fixing it.
Root of the problem:
You may come across this problem if the old log files are not in sequence with log, which is mentioned in the Restore.env file. You can file all the required log files using Eseutil /mh utility.
Resolution:
To fix this problem, follow the below steps:
1.View the content of Restore.env file using Eseutil /mh utility.
2.Record range of log files.
3.Remove the log files that are out of range.
If the above method does not work, you need to repair and restore the damaged Exchange Server database using third-party Exchange recovery software.
The Exchange Recovery tool are powerful enough to thoroughly scan entire database and extract all inaccessible data from it. They have rich and interactive graphical user interface to ensure easy recovery in all corruption scenarios.
Stellar Phoenix Mailbox Exchange Recovery is the most advanced and powerful exchange database recovery utility to offer assured recovery of damaged database. The exchange 2003 recovery software restores all EDB file objects, such as emails, notes, contacts, tasks, journal, attachments, and appointments. It works with Microsoft Exchange Server 2007, 2003, 2000, and 5.5.
|
|
