The way to Recover Data from EDB Files
On the internet defragmentation of Exchange Server database is completed automatically on normal basis for database maintenance. Online defragmentation helps removing those objects that are not in use thus, improves the database performance. Though, on the net database defragmentation is really a component 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 on the net defragmentation may well prompt you to perform Exchange recovery. Mentioned below is an error that appears after on the web defragmentation:
“1067 The Facts Store terminated abnormally”
The aforementioned error message occurs throughout online defragmentation when some sort of problem has forced the Data Store to stop abruptly. Even so to know why the Details Store is terminated abruptly, you’ve got to check the Event Log. Whenever 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
Pc: Servername
Description: Information and facts Store (nnnn) A bad page link (error -338) has been detected in a B-Tree (ObjectId: 70950, PgnoRoot: 157120) of database C:Files.edb (157120 => 296404, 296403).”
After reading the aforementioned error message, you can simply identify the real trigger for the termination of Details store. Mentioned below are the reasons because of which the Information and facts Store gets terminated abruptly:
1.During online defragmentation a few of the uncommitted logs are deleted.
2.Tough disk controller is defected.
3.Exchange database is damaged.
Based on the trigger of error message, you’ll be able to resolve the problem. Let’s assume that the trigger of the problem is database corruption, as mentioned within the event log specified in this article. Thinking about database corruption as the main cause for problem, let’s see tips on how to perform EDB repair. One can repair Exchange database either by utilizing Eseutil.exe or third party Exchange Recovery tool. Let’s elaborate eseutil.exe and third party Exchange Recovery tools:
1. Eseutil.exe: It’s a Microsoft product, which is supplied with MS Exchange Server to perform functions like database offline defragmentation, database repair, database compaction, etc. Eseutil is a command line tool; as a result, Exchange administrator ought to 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 quite a lot quick to use. Although making use of this tool, you don’t must bear in mind typical commands for Exchange Recovery. Just choose 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, utilizing Kernel for Exchange Server tool isn’t only quick but attractive too. 1 of the best features of the tool is, it uses the corrupt EDB file as read only copy; consequently, does not alter the data stored in the file. The software uses the data stored in the file and based on the fetched facts new and error-free EDB file is developed at destined location, which can be mounted on Exchange Server.
Author of this article is well versed in providing info related to Exchange Server, EDB repair, eseutil, eseutil Exchange 2003 , etc. His articles provide excellent details about resolving problems related to MS Exchange Server.
Come back for these sites gt bike parts
Processing your request, Please wait....
