| Microsoft Exchange Server is an excellent and | | | | corruption in the information store, there is yet |
| cost-effective collaboration and communication | | | | another way to detect the physical corruption i.e. |
| application used by several organizations all over | | | | online backups. The online backup process |
| the world. The Exchange Server database (.edb) | | | | thoroughly checks every single page in the |
| file serves as the repository to save mailboxes | | | | database. When you spot an evidence of physical |
| data. If this .edb file falls prey to physical | | | | corruption, it is wise to opt for an appropriate and |
| corruption, you can experience serious data loss | | | | effective Exchange Recovery software. |
| situation. To deal such cases, you must need to | | | | Preventing physical corruption |
| restore Exchange sever from a valid backup. | | | | 1.Make sure you use quality hardware |
| However, if there is no backup available, you need | | | | components and configure the system correctly |
| to employ an Exchange Server Recovery utility | | | | 2.Make sure not to run file-level utilities, like |
| to recover lost or inaccessible data. | | | | anti-virus program on a computer which is acting |
| Detecting physical corruption | | | | as an Microsoft Exchange Server |
| It is quite essential for a user to identify a | | | | 3.Turn off write-back caching. If you do use |
| physical corruption scenario at an early stage and | | | | write-back caching, ensure that the data is |
| resolve the issue with proper corrective | | | | completely protected |
| measures quickly in order to avoid disastrous data | | | | Recovering after physical corruption |
| loss cases. | | | | Use backup |
| Information store is a key component of MS | | | | As told before, the only best way to deal with a |
| Exchange Server, having two databases viz | | | | physical corruption instance is by using an updated |
| private information store and public information | | | | backup, so that the log files can be rolled forward |
| store. During an event of physical corruption in the | | | | to bring the system to a consistent state. |
| information store, you may encounter the | | | | Eseutil.exe utility |
| following error, thrown by Microsoft Exchange | | | | You can also consider running the Eseutil.exe utility |
| Server: | | | | in order to perform Exchange Recovery. |
| "-1018 (JET_errReadVerifyFailure) The data read | | | | However, it is not very much recommended to |
| from disk is not the same as the data that was | | | | use this utility as it deletes the damaged pages |
| written to disk" | | | | and make the broken or inconsistent database |
| "-1022 (JET_errDiskIO) The hardware, device | | | | running again. |
| driver, or operating system is returning errors" | | | | Third-party recovery software |
| "510 JET_errLogWriteFail The log files are out of | | | | Download a reliable third-party Exchange |
| disk space or there is a hardware failure with the | | | | Recovery tool from the Internet and restore the |
| log file disk" | | | | corrupt database. This is the best and safest way |
| Though, these errors indicate the physical | | | | to recover your .edb file. |