How to get rid of Exchange Dirty Shutdown Problem?

This is a very common problem that every Exchange user has to face.

Symptoms: - Following are the main factors that need to be determined in case of an Exchange System in a Dirty shutdown state.

• Collect the database and the required logs

User must find a copy of the .edb file and needed logs. These logs are required from database perspective and this can be completed by suspending the older database copy, and then copying the needed files to a separate location or creating a snapshot of the volume which can be reverted to at a later time.

Resolving Exchange Sever Error -338 (JET_errBadParentPageLink, Database corrupted)

Microsoft Exchange Server, no doubt, is one of the best email server applications. It is a transaction based messaging tool and provides better security system against important data loss. Despite of powerful data security, Exchange database files still become damaged and corrupted due to various reasons. The most common causes of corruption are Dirty shutdown, hardware failure, database file oversize issues, virus attack, human errors and due to application bugs. Such paradigms directly affect the Information Store databases ( Priv.edb and Pub.edb). Well, such kind of problematic situations can be tackled easily through the use of an updated backup or some advance third party Exchange recovery software if the built-in utilities fail. Let us do a general talk on a problematic situation which is faced by Exchange server administrator at an attempt to check the database integrity by executing the inbuilt eseutil commands. Error messages appear to be like this: