【文章內容簡介】 COV_SRVR only. b. On PROD_SRVR, on each drive that contains an EXCHSRVR\MDBDATA directory, create a new directory named EXCHSRVR\.c. On RECOV_SRVR, rename the EXCHSRVR\MDBDATA directory on each drive to .d. On RECOV_SRVR, create a new EXCHSRVR\MDBDATA directory on each drive.e. Copy the and files from the directory on RECOV_SRVR to the appropriate directory on PROD_SRVR. This is the directory on the drive that contains the currently used or . Therefore, if the location of the on PROD_SRVR is E:\EXCHSRVR\MDBDATA, copy the from RECOV_SRVR to E:\EXCHSRVR\ and do the same for the file.f. After you copy the and files to the directory on PROD_SRVR, stop the Exchange Information Store service on PROD_SRVR.g. On PROD_SRVR, rename the EXCHSRVR\MDBDATA directories on each drive to .h. On PROD_SRVR, create new EXCHSRVR\MDBDATA directories on each drive.i. On PROD_SRVR, move the and files from the directory to the MDBDATA directory.j. Copy the and files from the directory on PROD_SRVR to the EXCHSRVR\MDBDATA directory on RECOV_SRVR. Make sure that you are copying the files to the correct drive on RECOV_SRVR. If you are not sure, see the DB Path Registry value under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIS\ParametersPrivate and HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIS\ParametersPublic.k. Now you have exchanged the and files between PROD_SRVR and RECOV_SRVR. The MDBDATA directories on both servers should contain only the and files, and no other files should be in these directories. l. The and on PROD_SRVR are the information store as it existed at the time of the crash and contain all user data generated until the time of the failure. The and on RECOV_SRVR contain any data generated after you reset the Exchange Information Store service in Step1. The database files on RECOV_SRVR should be much smaller than those on PROD_SRVR.8. On both PROD_SRVR and RECOV_SRVR, at a mand prompt, change to the EXCHSRVR\BIN directory, and run the following mand:ISINTEG patch9. Start the Microsoft Exchange Information Store services on PROD_SRVR and RECOV_SRVR. To additionally reduce downtime, you can perform Step 8 on RECOV_SRVR after you plete Step 7(i) and then start the Exchange Information Store service on PROD_SRVR. In other words, you can start the Microsoft Exchange Information Store service on PROD_SRVR before the copy process in Step 7(j) is pleted.10. As soon as the Microsoft Exchange Information Store service has been started on RECOV_SRVR, you might need to run the DS/IS consistency adjuster to create directory entries for the mailboxes in the information store database files.11. Run against RECOV_SRVR, and merge all data from RECOV_SRVR into PROD_SRVR. You can use the onestep merge procedure or the twostep merge procedure. If you use the latter, you must first extract data on RECOV_SRVR to .pst files and then run again, against PROD_SRVR and merge the data from the .pst files into the mailboxes on PROD_SRVR. It is remended that you specify an interval for the program to extract data. This interval should be approximately the time the Information Store was reset on PROD_SRVR.12. At this point, after you reset the Microsoft Exchange Information Store service (Step1), all user messages and folders created on PROD_SRVR should be merged back into the mailboxes on PROD_SRVR and there should be no loss of data.13. Perform a full online backup of the information store on PROD_SRVR.Note:Resetting the information store on the production server invalidates all client offline stores (.ost) files. Users receive an error when they try to log on to the Exchange client or Microsoft Office Outlook174。 or when they synchronize with the Exchange server. Users will have to create a new .ost file to work with the new store. When the original store is restored on the production server, any .ost files users create for the temporary store bee invalid, and the users must create another .ost file.The above procedure will not recover all user data. Read the section on the limitations of in this document. The above procedure will only merge data in the private information store. To recover data from the public information store, you must manually log on to a client connected to a mailbox on RECOV_SRVR and copy public folder data to a .pst file. Then, you must log on to a mailbox on PROD_SRVR, add the same .pst file to the profile, and copy the data from the copied public folders in the .pst file to the serverbased public folders.For Exchange2000 or Exchange2003The process of using to minimize downtime differs slightly for Exchange2000 or Exchange2003 because of the requirements of Active Directory. NoteThere are references to the recovery storage group feature, which is available only in Exchange Server2003.The basic steps are as follows:1. Record all the logical names needed to recover the database.a. The Exchange2000 or 2003 organization name.b. The administrative group name to which the database belongs.c. The storage group name to which the database belongs.d. The logical database name.e. The legacyExchangeDN value of the administrative group to which the database belongs.NoteIf the legacyExchangeDN is the First Administrative Group, you do not need to change this value. However, if this value is not equal to the First Administrative Group, you will need to change the value.2. Perform one of the following two actions: Use the recovery storage group feature, which enables you to create a dedicated storage group to which you can restore a database on the same Exchange server. When you use this feature, you can use to log on to the restored database and extract the data. Recovery storage groups are available only in Exchange Server2003. For more information about Exchange Server 2003 Recovery Storage Groups, see Using Exchange Server 2003 Recovery Storage Groups