Exchange Database Physical Corruption: Ways To Detect, Prevent And Recover
Microsoft Exchange Server is an excellent and cost-effective collaboration and communication
application used by several organizations all over the world. The Exchange Server database (.edb) file serves as the repository to save mailboxes data. If this .edb file falls prey to physical corruption, you can experience serious data loss situation. To deal such cases, you must need to restore Exchange sever from a valid backup. However, if there is no backup available, you need to employ an Exchange Server recovery utility to recover lost or inaccessible data.
Detecting physical corruption
It is quite essential for a user to identify a physical corruption scenario at an early stage and resolve the issue with proper corrective measures quickly in order to avoid disastrous data loss cases.
Information store is a key component of MS Exchange Server, having two databases viz private information store and public information store. During an event of physical corruption in the information store, you may encounter the following error, thrown by Microsoft Exchange Server:
-1018 (JET_errReadVerifyFailure) The data read from disk is not the same as the data that was written to disk
-1022 (JET_errDiskIO) The hardware, device driver, or operating system is returning errors
510 JET_errLogWriteFail The log files are out of disk space or there is a hardware failure with the log file disk
Though, these errors indicate the physical corruption in the information store, there is yet another way to detect the physical corruption i.e. online backups. The online backup process thoroughly checks every single page in the database. When you spot an evidence of physical corruption, it is wise to opt for an appropriate and effective Exchange Recovery software.
Preventing physical corruption
1.Make sure you use quality hardware components and configure the system correctly
2.Make sure not to run file-level utilities, like anti-virus program on a computer which is acting as an Microsoft Exchange Server
3.Turn off write-back caching. If you do use write-back caching, ensure that the data is completely protected
Recovering after physical corruption
Use backup
As told before, the only best way to deal with a physical corruption instance is by using an updated backup, so that the log files can be rolled forward to bring the system to a consistent state.
Eseutil.exe utility
You can also consider running the Eseutil.exe utility in order to perform Exchange recovery. However, it is not very much recommended to use this utility as it deletes the damaged pages and make the broken or inconsistent database running again.
Third-party recovery software
Download a reliable third-party Exchange Recovery tool from the Internet and restore the corrupt database. This is the best and safest way to recover your .edb file.
Stellar Phoenix Mailbox Exchange Recovery repairs a corrupt Exchange Server database and restores all mailboxes as .pst files. Compatible with MS Exchange Server 2007, 2003, 2000 and 5.5, the easy-to-use tool also allows selective Exchange mailbox recovery and deleted mailbox recovery.
by: axel culver
Database: Your Perfect Guide To Juggle With Data Database: The Ideal Answer To Your Data Queries Detox Or Detoxification Is The Start Of Recovery How Virtualization Eases Disaster Recovery A Guide to Data Recovery and Restoration Extent Allocation Issues And Data Loss In Mac Os X Say No To Misuse Of Personal Data Through The Paper Shredders 98 Million announced by Secretary Napolitano in Recovery Act Funding Mexican Peso To Us Economy: Us Recovery And The Peso Opportunity Microsoft Access Database: Presenting The Most Preferred Desktop Database System All About Data Entry Projects Know Your Web Hosting - Difference between Bandwidth & Data Transfer Data Center Infrastructure of Indian Hosting Companies