Welcome to the world of MS Exchange Server mailing system. If you are already a user of this messaging system, you must be familiar with its attractive features like e-mail access, calendar, contacts, and voice mail. Exchange Server supports a wide variety of devices that can be mobile, remote or attached to a network. The software is reliable and provides protection against spam and viruses. Users can store mails for long time as archives and access them again using Outlook integration or Web Access tools. Organizations that rely on Exchange Server are set to achieve excellent business results. Bosses have a better control on deployment, administration and compliance, customized to environment.
As the dependency of the organizations on Exchange Server has grown, any problem can prove to be catastrophic. The impact of a corrupt Exchange Server can be so much that it can daunt the productivity, reputation and economy of a company. In today’s competitive atmosphere, if companies do not adhere to repair and recovery policy, for a smooth and uninterrupted availability of mail system, they become unfit to stand in the market. For better, quick and effective recovery of exchange server users should keep the following points in their mind while repair of Exchange Server.
1. Take a backup before recovery. Before repairing, it is best to take a backup of the exchange database, logs and other supporting files and applications. This will protect you against any further damage of the EDB file. After backup creation restore the database using online backup, followed by deletion of MDBDATA folders.
2. Mind the order of restore from Incremental Backup. Once you restore the database, go ahead with incremental backup. Note all the files that were erased from the MDBDATA folder. Use incremental backups to restore the files. Restore from the incremental backups should be done in the same order in which it was taken. After restoring, add the name of the new files in the list of file names created earlier.
3. EDB.log files. Copy all the Edbxxxxx.log files created after the last incremental backup. You can find the logs in the MDBDATA folder. Note that EDB.log file must be copied only if the system was properly shutdown last time. If the last shutdown was abnormal, the edb.log file may be damaged.
4. Priv.edb and pub.edb. No need to use eseutil /mh or edbutil /mh tools to check Priv.edb and pub.edb files for inconsistency. It is already understood that Priv.edb and Pub.edb files are inconsistent.
5. Check Event.log. Check the EVENT.log file to find the last executed event. To check it, open Services in Control Panel. See the Application event log for new events. If new events are present then the Exchange recovery is successful.
6. Check Mailbox. Once the information store is running, check the mailboxes for messages and folders. Send some ‘test mails’ to users. Verify the accuracy of subject, senders address, etc of the mail.
7. Take a backup after recovery. Take a backup of the recovered and repaired exchange database for future purpose.
If you follow these 7 guidelines, recovery of Exchange Server is done effectively and precisely. Confused! No need to get concerned. To ease the process many companies provide some commercial applications to recover Exchange Server.
About the Guest Post Author:
Ricky Watson is an Exchange server administrator and doing research on some commercial data recovery programs. He has personally used an Exchange server recovery program that is incredibly easy-to-use, flexible, well supported and priced reasonably. More information of this program can be found here: http://www.repair-file.com/exchange-server-recovery.htm