Steps to restore exchange server 2003
1. Replace any damaged hardware. If possible, ensure that all replacement hardware in the server you are rebuilding is identical to the hardware that existed in the server that experienced the disaster.
2. Install windows 2003 on the server that you are rebuilding.
3. Restore the windows backup set that was performed on the damaged server to the
server you are rebuilding. Restoring the windows backup set restores the windows 2003
system files, including the registry database and internet information services metabase files. This process also provides the server that you are rebuilding with its original NetBIOS name and returns it to the correct domain. If you do not perform this step, you cannot properly run setup in disaster recovery mode.
4. Install any windows 2003 service packs and software updates that were running on the damaged server to the server you are rebuilding.
5. Install any application (other than exchange server 2003) that run on the server.
6. Restore any additional data backups that were performed on the damaged server.
7. Run exchange server 2003 setup in disaster recovery mode. This process installs
exchange applications and any necessary exchange files to the server you are rebuilding. This process also uses the configuration information that is stored on the exchange server object in Active directory to reclaim the configuration of the original server. The configuration information that is reclaimed includes the exchange storage group names, mailbox store names, public folder store names, and virtual server configuration settings. When you run exchange in disaster recovery mode, ensure that all the components that existed on the damaged server are selected.
8. If not already selected, select disaster recovery for each component that was installed on the damaged server.
9. Install Exchange server 2003 to the same drive and directory that it was installed to on the damaged server. At a minimum, you should ensure that all the drive letters on which databases and log files were kept are available.
10. Install any exchange server 2003 hotfixes that were running on the damaged server.
11. Install in disaster recovery mode any exchange server 2003 service packs that were running previously on the damaged server to the server. Installing exchange server 2003 service packs in disaster recovery mode prevents the exchange databases from being mounted at the end of the service pack installation process, which enables you to proceed to restoring the exchange databases from backup.
12. After exchange database restore, check the state of the database by using eseutil. If they are in dirty shutdown state, use eseutil to covert them to clean shutdown state. Once exchange databases are in clean shutdown, you can mount them.
13. Restore exchange database files and log files to the correct locations from the backup.
14. If you do not have the latest log files then you will lose changes that were made to exchange databases up to the time the disaster occurred.
Subscribe to:
Post Comments (Atom)
1 comment:
To solve such type of problems, Microsoft has designed the Exchange Server Disaster Recovery Analyzer tool for Exchange 2003 Server. If you are an Exchange server administrator, you can use this application to troubleshoot issues that occur when you attempt to mount an Exchange database database file. This tool collects configuration settings and header information from damaged Exchange databases and transaction log files programmatically.
Although the tool is enough to handle disaster problem, it takes much time to complete the process. There are some easy to use and advanced tools available in the market to perform the quick Exchange 2003 recovery process. One such tool is Stellar Phoenix Exchange server recovery that is capable to handle all corruption situations effectivey in any version of Exchange server i.e. 5.5, 2000, 2003, 2007, and 2010.
Post a Comment