Recover Data From EDB File After Erroneous Online Defragmentation
Online defragmentation of Exchange Server database is done automatically on regular basis for database maintenance.
Online defragmentation helps removing those objects that are not in use thus, improves the database performance.
Though, online database defragmentation is a part of database maintenance, it sometimes lead into generation of errors that show some sort of corruption in database, existence of uncommitted logs, and other issues.
Appearance of the errors after online defragmentation may prompt you to perform Exchange recovery.
Mentioned below is an error that appears after online defragmentation: "1067 The Information Store terminated abnormally" The aforementioned error message occurs during online defragmentation when some sort of issue has forced the Information Store to stop abruptly.
However to know why the Information Store is terminated abruptly, you have to check the Event Log.
When you check the Event log, you get the following information: "Date: date Source: ESE Time: time Category: Database Corruption Type: Error Event ID: 447 User: N/A Computer: Servername Description: Information Store (nnnn) A bad page link (error -338) has been detected in a B-Tree (ObjectId: 70950, PgnoRoot: 157120) of database C:\Program Files\exchsrvr\mdbdata\priv1.
edb (157120 => 296404, 296403).
" After reading the aforementioned error message, you can easily identify the real cause for the termination of Information store.
Mentioned below are the reasons due to which the Information Store gets terminated abruptly: 1.
During online defragmentation some of the uncommitted logs are deleted.
2.
Hard disk controller is defected.
3.
Exchange database is damaged.
Based on the cause of error message, you can resolve the issue.
Let's assume that the cause of the issue is database corruption, as mentioned in the event log specified in this article.
Considering database corruption as the main cause for issue, let's see how to perform EDB repair.
One can repair Exchange database either by using Eseutil.
exe or third party Exchange Recovery tool.
Let's elaborate eseutil.
exe and third party Exchange Recovery tools: 1.
Eseutil.
exe: It is a Microsoft product, which is provided with MS Exchange Server to perform functions like database offline defragmentation, database repair, database compaction, etc.
Eseutil is a command line tool; therefore, Exchange administrator must have apt knowledge about its commands, their executions, and their effect of the database.
2.
Exchange Recovery tool: Third party Exchange Recovery tool is a graphical EDB repair tool, which is very much easy to use.
While using this tool, you do not need to remember typical commands for Exchange Recovery.
Just select the database and proceed ahead to repair the database.
Kernel for Exchange Server recovery is one of the renowned tools for Exchange database repair and recovery.
Comprising the well-organized and attractive graphical user interface, using Kernel for Exchange Server tool is not only easy but attractive too.
One of the best features of the tool is, it uses the corrupt EDB file as read only copy; therefore, does not alter the data stored in the file.
The software uses the data stored in the file and based on the fetched information new and error-free EDB file is created at destined location, which can be mounted on Exchange Server.
Online defragmentation helps removing those objects that are not in use thus, improves the database performance.
Though, online database defragmentation is a part of database maintenance, it sometimes lead into generation of errors that show some sort of corruption in database, existence of uncommitted logs, and other issues.
Appearance of the errors after online defragmentation may prompt you to perform Exchange recovery.
Mentioned below is an error that appears after online defragmentation: "1067 The Information Store terminated abnormally" The aforementioned error message occurs during online defragmentation when some sort of issue has forced the Information Store to stop abruptly.
However to know why the Information Store is terminated abruptly, you have to check the Event Log.
When you check the Event log, you get the following information: "Date: date Source: ESE Time: time Category: Database Corruption Type: Error Event ID: 447 User: N/A Computer: Servername Description: Information Store (nnnn) A bad page link (error -338) has been detected in a B-Tree (ObjectId: 70950, PgnoRoot: 157120) of database C:\Program Files\exchsrvr\mdbdata\priv1.
edb (157120 => 296404, 296403).
" After reading the aforementioned error message, you can easily identify the real cause for the termination of Information store.
Mentioned below are the reasons due to which the Information Store gets terminated abruptly: 1.
During online defragmentation some of the uncommitted logs are deleted.
2.
Hard disk controller is defected.
3.
Exchange database is damaged.
Based on the cause of error message, you can resolve the issue.
Let's assume that the cause of the issue is database corruption, as mentioned in the event log specified in this article.
Considering database corruption as the main cause for issue, let's see how to perform EDB repair.
One can repair Exchange database either by using Eseutil.
exe or third party Exchange Recovery tool.
Let's elaborate eseutil.
exe and third party Exchange Recovery tools: 1.
Eseutil.
exe: It is a Microsoft product, which is provided with MS Exchange Server to perform functions like database offline defragmentation, database repair, database compaction, etc.
Eseutil is a command line tool; therefore, Exchange administrator must have apt knowledge about its commands, their executions, and their effect of the database.
2.
Exchange Recovery tool: Third party Exchange Recovery tool is a graphical EDB repair tool, which is very much easy to use.
While using this tool, you do not need to remember typical commands for Exchange Recovery.
Just select the database and proceed ahead to repair the database.
Kernel for Exchange Server recovery is one of the renowned tools for Exchange database repair and recovery.
Comprising the well-organized and attractive graphical user interface, using Kernel for Exchange Server tool is not only easy but attractive too.
One of the best features of the tool is, it uses the corrupt EDB file as read only copy; therefore, does not alter the data stored in the file.
The software uses the data stored in the file and based on the fetched information new and error-free EDB file is created at destined location, which can be mounted on Exchange Server.
Source...