The document discusses Microsoft Exchange databases, highlighting common causes and errors of data loss, such as inappropriate data writing and disk I/O errors. It details recovery methods using inbuilt tools like eseutil.exe and isinteg.exe, while also noting their limitations and complexities. Additionally, it presents an alternative solution for recovering deleted emails from damaged databases, emphasizing its user-friendly interface and system requirements.

1. MICROSOFT EXCHANGE DATABASE
DATA LOSS & THEIR RECOVERY METHODS

2. EXCHANGE DATABASE – INTRODUCTION
Exchange Database or an EDB File is the main repository that stores all the data for a defined mailbox. It stores all
the in-process massages as well as the stored non-SMTP messages.
EDB
Public Folder
Or
Pub.edb
Private Folder
Or
Priv.edb
Private Folder
Or
Priv.edb
Public Folder
Or
Pub.edb
CORRESPONDING
STM file stores the streamed
data for the Public as well as
private folders
CAN BE CLASSIFIED AS

3. EXCHANGE DATABASE – ERRORS
Fundamental causes of data damage:
• Inappropriate data written for the storage media.
• Data written in the wrong place of storage media.
• Data altered after being stored.
Data damage results in the following errors:
• 1018 JET_errReadVerifyFailure
• 1019 JET_errPageNotInitialized
• 1022 JET_errDiskIO
The database errors can be categorized as:
• Page or file system level errors
• Database or JET level errors
• Application or the exchange info store errors

4. How resolve
these
problems?

5. ESEUTIL.EXE AND ISINTEG.EXE
These Problems can be resolved using inbuilt tools that microsoft provides – Eseutil.exe and Isinteg.exe
Eseutil.exe Effective on
Page level errors
Database level errors
Isinteg.exe Effective on Application level errors
Solution

6. DO THESE INBUILT TOOLS HAVE ANY LIMITATIONS?
• Incomplete data: As the ESEUTIL /p command is run it removes the corrupt pages and the data content in it is also removed.
• New Folder Hierarchy formed: As Isinteg is used an all new hierarchy is formed as the pages a re-indexed.
• 110% disk space required: The Isinteg tool requires 10% extra space of the original database size
• Complicated: Most frustrating this is the complexity of the tool, it has so many commands that for a beginner it’s just like mission
to repair his/her EDB using the tools.
• Time Consuming: And lastly it’s a very lengthy process.

7. So is there any other
solution available?

8. EXCHANGE DELETED
EMAIL RECOVERY
Yes! Here’s a reliable solution

9. EXCHANGE DELETED EMAIL RECOVERY
WHAT IT OFFERS?
Now easily recover your Exchange mailbox deleted data from a damaged or a
dismounted Exchange database (EDB) File.
• Effective recovery of Permanently Hard Deleted Exchange Mailbox.
• Dual Scan mode that includes advance mode in case of heavy corruption.
• Recovery of data from an Inactive Exchange Server.
• Data recovery Beyond Retention Period Expiry
• A user friendly interface.
Read more at: http://www.emaildoctor.org/deleted-emails/exchange-server.html
• Outlook should be installed configured properly
• Migration machine and Exchange Server should be working
under the same domain.
• Exchange Mailboxes should have complete administrative
rights for Exchange (2000-2003,2007-2013) Versions.
Application Pre-Requisites
• Windows OS: Windows 8.1 and below versions(32-bit or 64-bit)
• Processor: 1 GHz Processor (2.4 recommended)
• RAM: 512 MB (1GB Recommended)
• Disc Space: 50 MB free space
System Requirements

10. Thank You