Here are the steps to let you analyze your database for repair:

1.Download and complete the installation process. You can find DRAT at Start -> All Programs -> Microsoft Exchange menu.
2.Click to start it and now you can either let the software to automatically detect your Exchange databases or manually specify the database locations. Unless your server is running an unusual configuration, Auto Detect is the best way.
3.Enter the Exchange server’s name and the name of one of your domain controllers.
4.Click Next and the tool starts collecting server’s configuration. It isn’t actually analyzing the database yet; it’s just detecting the various storage groups set up on your server and the databases within them.
5.On completion of the detection process, choose the storage group containing the problematic database. A screen will appear listing the name of the databases within the store that you chose.
6.Now you can select: Analyze a single database or all databases within the storage group. It’s better to analyze all databases even if the issue is with a single database as all databases in a storage group share a common set of transaction logs, which can sometimes be the root of the problem. If you want quick results, then probably better select the specific database as it takes a while to completely analyze the databases. Select to let the analysis begin.

Once, the process is complete; you get valuable information about the database status and it instructs if any issues were found with the database. It also points to Knowledge Base articles which can be used to revive the server if you can’t mount the database. This utility can be run against Exchange 2000 Service Pack 3 or higher and Exchange 2003. This can get you rid of various errors but what if the EDB files are corrupt. It’s tough to repair them and rebuild the database. In such cases, convert the EDB files to PST files to view them with MS Outlook and recover your data.

Use Restore Exchange Server Database tool to convert EDB to PST files. It repairs Dirty Shutdown error and lets you to mount the databases even when DRAT can’t provide sufficient help. It repairs Priv1.edb database and public folders (pub.edb). It has three recovery modes for complete Exchange recovery; Automatic Analyze and Recover, Advance Scan and Rebuild Corrupted Database. It recovers every mailbox from the EDB database and allows you to save them PST format. It supports MS Exchange Server 5.0, 5.5, 2000, 2003, 2007, 2010 and the PST file created is compatible with MS Outlook 2010, 2007, 2003, 2000, 98 and 97. Use the free evaluation version to restore Exchange and preview the recovered files in PST format but requires the full version to save them in your drive.

Open the Microsoft Exchange Information Store and register the error first. Assure that the Information Store has been stopped before running the Eseutil.exe program. If the information store is not responding then disable it by restarting the server. Now check the consistency of databases with these commands:

C:\Program Files\exchsrvr\BIN>eseutil /mh
“drive:\Program Files\exchsrvr\MDBDATA\priv1.edb”

C:\Program Files\exchsrvr\BIN>eseutil /mh
“drive:\Program Files\exchsrvr\MDBDATA\pub1.edb”

In case you have executed an upgrade then the files would reside at C:\Exchsrvr\Mdbdata folder. Check whether the EDB files are inconsistent or not with these commands:

C:\Program Files\exchsrvr\BIN>eseutil /mh
C:\Program Files\exchsrvr\MDBDATA\priv1.edb > mypriv.txt

C:\Program Files\exchsrvr\BIN>eseutil /mh
C:\Program Files\exchsrvr\MDBDATA\pub1.edb > mypub.txt

If the Public or Private EDB folders are not residing in Program Files folder on the same drive then replace the “C:\program files\mdbdata\priv1.edb” with the full path of the Private and Public EDB files.

Note: If the files are not consistent then perform a soft recovery on the log files with C:\Program Files\exchsrvr\MDBDATA>”C:\Program Files\exchsrvr\BIN\eseutil” /r E00 on the prompt and press yes. If this has not worked then bring the Private & Public EDB files to consistent state:

C:\Program Files\exchsrvr\MDBDATA>”C:\Program Files\exchsrvr\BIN\eseutil” /p priv1.edb
C:\Program Files\exchsrvr\MDBDATA>”C:\Program Files\exchsrvr\BIN\eseutil” /p pub1.edb

Now eradicate all .log files in the Mdbdata folder, .chk filed, and Temp.edb files. Quickly mount and dismount the databases so that other users cannot access them. Defragment the Public and Private EDB files:
C:\Program Files\exchsrvr\BIN>eseutil /d
C:\Program Files\exchsrvr\MDBDATA\priv1.edb

C:\Program Files\exchsrvr\BIN>eseutil /d
C:\Program Files\exchsrvr\MDBDATA\pub1.edb

Now run the Isinteg.exe tool for fixing the private & public EDB databases and restart the information store: C:\Program Files\exchsrvr\BIN>isinteg -s (servername) -fix -test alltests.

If the Information has not been restored then a user can derive the data with restore EDB tool. This is a majestic Restore Exchange tool which retrieves the EDB and STM files from any kind of corruption.

Restore Exchange by using the Eseutil & Isinteg utilities:

Note: Here we have taken the example of Jet Engine Error i.e. Error 4294966746.
The Eseutil utility can be accessed by running the C:\Program Files\Exchsrvr\Bin command. But before using this utility ensure to have at least 20% of spared disk space in exchange database. With Eseutil a user can generate various commands like Defragmentation: /D, Repair: /P, Restore: /C, Recovery: /R, Integrity: / G, File Dump: /M, Checksum: /K, Copy File: /Y, etc. These are the steps for trying it:

Open the information store and register the error or ID messages. Run the Eseutil.exe utility for checking the consistency of Private and Public EDB files. For Private EDB files Run c:\exchsrvr\bin>eseutil /mh…\mdbdata\priv.edb command. For public EDB files run c:\exchsrvr\bin>eseutil /mh..\mdbdata\pub.edb command. After that provide the output in a text file:

• For Private EDB files c:\exchsrvr\bin>eseutil /mh ..\mdbdata\priv.edb > mypriv.txt.
• For Public EDB files c:\exchsrvr\bin>eseutil /mh ..\mdbdata\pub.edb > mypub.txt.

Note: Kindly enter the full path of EDB files.
In case if the files are residing in MBD folders then try the Swift Recovery process.

• c:\exchsrvr\bin>eseutil /r /ispriv
• c:\exchsrvr\bin>eseutil /r /ispub

Now conduct full recovery with the eseutil /mh command then try hard repair for any discrepancy.

• c:\exchsrvr\bin>eseutil /p /ispriv for private EDB files.
• c:\exchsrvr\bin>eseutil /p /ispub for public EDB files.

Also, remove the Temp.edb files in ExchSrvr\Mdbdata. Now check the Microsoft Exchange Information Store service and close the program if they are working normally. Simultaneously run the Defragment (eseutil/d) and repair (Isinteg) command on the private and public EDB files. Repeat this process unless zero error errors are reported.

For avoiding this cumbersome process and saving time use the reliable Exchange Server Recovery software. This restore EDB tool can quickly restore the corrupt and damaged EDB files into accessible PST files.

By making the proper usage of restore exchange software one can easily deal with every situation very easily. However, you can also get ride of such situations or corruption even by using in-built data recovery tools. In fact, MS Exchange Server provides user with two different repair tools- Eseutil and Isinteg. Both these utilities are effective and facilitate you perform Exchange Server Recovery operation in an easiest manner. These in-built programs repair and restore the
Database that has got corrupted, but you may surprise to know that there are conditions when these utilities fail completely to deliver the desired result. In fact, in situation of severe database damage the programs fail to perform its operation. To deal with such unfavorable conditions the most effective approach that you can opt is MS Exchange recovery software like Exchange Server Recovery tool. The tool is very efficient and can be very useful for repairing the deleted Exchange mailboxes as well as the permanently deleted emails from the mailbox folders.

There are many who also recommends opting the manual data recovery process to restore Exchange database. But, it’s just not that easy as it appears initially. Adding to this, a manual MS Exchange database recovery process is a very expensive and time-consuming method. The probability to retrieve the required information with full accuracy is very less. Therefore, it’s important that you take help of this third party Exchange Serer Recovery tool. It is very easy and safe to use.

All that a user needs to do is just provide the file path. And, once you provide the complete path the software will do rest of the work. In fact, the most important highlight of this tool is its interactive graphical user interface that assists user in having quick data recovery.

Microsoft Exchange Server saves all the received, sent emails in an EDB database file which faces corruption due to physical hard drive errors, jet errors and file size errors. Also, exchange server failure occurs at times due to improper shutdown, virus attacks and human errors. Recovery for Exchange Server restore Exchange Server email database i.e., .EDB and .STM files. It efficiently converts .EDB files to working .PST files through which emails of MS Exchange Server can be viewed with Microsoft Outlook email client. It also recovers inaccessible and deleted emails from MS Exchange Server database files.

Key features:

Let’s have a brief look at its elaborate features.

• Use it to restore exchange server data and save user mailbox to .PST or .EDB file
• Restores various items of mailbox including emails, attachments, images, contacts, appointments, tasks, etc
• Also recovers inaccessible and deleted emails from MS Exchange Server database files.
• Repairs Dirty Shutdown error where eseutil and other ms utilities fail
• Efficiently repairs large databases.

Most of them support email recovery from all the versions of MS Exchange Server 5.0, 5.5, 2000, 2003, 2007 and 2010. Also normally support Microsoft Outlook 97, 98, 2000, XP, 2003, 2007 and 2010. Generally they come with a free trial version for scanning and viewing the recoverable data and the full version is used to actually retrieve them.

Exchange Server Recovery:

Nucleus technologies also provide Restore Exchange database software but with added features. It has three recovery modes; Automatic Analyze and Recover, Advance Scan and Rebuild Corrupted Database. Use them accordingly to recover data with the most appropriate way. Software is available in two different licenses, corporate and technician license depending on how many files you need to repair.

Microsoft Exchange Server does not provide any inbuilt tool to diagnose the logical corruption of EDB database.

Moreover, there are no specific symptoms to identify the logical corruption of database. In case the EDB database is affected by logical corruption, the EDB database becomes inaccessible and you face acute data loss situation.

Let’s consider a real life scenario wherein when you attempt to access the data from the Exchange Server, you come across the following entries in the Application Event log:

Event ID: 42
Source: EDB
Type: Warning
Category: General
Description: MSExchangeIS ((###)) The database engine found a bad page.

The aforementioned entries in the Application Event log symbolize logical corruption of Exchange Server database files.

After restoring the database, just in case you replay the wrong transaction log files, logical corruption of Exchange Server database takes place.

As a matter of fact, the “bad page link” or JET_errBadPageLink errors symbolize or indicate the logical corruption of Exchange Server database.

In order to overcome this situation, you need to perform Exchange recovery.

Now let’s see what all you can do to resolve the aforementioned issue. A lot can be done to resolve the aforementioned issue.

First and foremost, try to restore Exchange Server database from the last, valid, and clean backup. However, in case of unavailability of a valid backup or just in case you are unable to restore Exchange Server database from a valid backup, use the exmerge.exe tool to export the data.

If the above-mentioned does not work, then use the “Move Mailbox” feature in Exchange Administrator program for moving users from damaged Exchange Server to another one. Now, recreate priv.edb file on the original Exchange Server and then move users back to the original Exchange Server.

However, if nothing works then use a professional and proficient restore Exchange tool to repair the damaged and corrupt Exchange database.

Exchange Server recovery is a professional, comprehensive, and result-oriented restore Exchange tool that is specifically devised to repair Exchange Server database (EDB) files.

First of all, if you come across such a situation where your priv1.edb is damaged and you have a recently updated backup of your EDB database, then we suggest you to recover EDB using your backup. Check for a recently updated backup so that you don’t have to look out for an alternative to repair the corrupt file. And if you don’t have a backup, then you need to try recovering your data using a number of EDB repair utilities that Microsoft has to offer. However, if in case the backup of your data is missing, the only way left to get your important data back is by getting your file repaired. Let’s start the repair process with some useful tools Microsoft has to offer (although most of the times, these don’t work):

If priv1.edb is damaged and pub.edb files some error messages start appearing.  Make a note of the error messages and event ID that occurred while mounting the EDB file.

To resolve them, use of DS/IS Consistency Adjuster is suggested; DS/IS Consistency Adjuster is devised to run on both public as well as private information stores. Using this tool you can perform this recovery operation on another server, or if you removed or reinstalled Exchange Server on this server and do not have a working copy of the Dir.edb. In order to perform recovery operation using this utility, you need to re-create any distribution lists and memberships to those lists that were lost.

After performing this operation, you can expect Server to work and users will start receiving emails. However, you are able to retrieve your emails but there are other issues that you need to troubleshoot, and then we suggest you to use the Exmerge.exe tool to export all the user mailboxes to PST file. This will help you merge the PST files to user mailboxes in a new Priv1.edb file. 

But again, we were looking for something that could help us retrieve the emails that were lost. In order to retrieve the previous data and restore Exchange when priv1.edb is damaged, rely on third party Exchange Server repair software. Why? Let us understand this in detail; the best part of this third party software is that these tools offer you the flexibility of free evaluation that saves you from the horror of wasting money on useless crap.

You may try about 20 of the Restore Exchange tools available online, but choose the one that may help you to restore Exchange when priv1.edb is damaged. Try the evaluation version of Exchange Repair to recover your previous emails and check the accuracy of the tool. But before you select any third restore Exchange tool, let me remind you a few points to ponder:

Before you try repairing the corrupt file, make a copy of your file at a different location 

Always try its free evaluation version first and check its accuracy

Check its reviews and customer satisfaction

 Look out for discount offers available (most of the companies claim guaranteed results or offer the money back) So don’t panic when your data is lost, stay alert, look for possible rescue procedures online and select the one that suits you