[IT认证]MailboxMergeWizardExMerge.doc

Exchange Mailbox Merge Program Published: September2003Updated: March2005Applies To: All versions of Exchange ServerCopyright The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. 20032004 Microsoft Corporation. All rights reserved.Microsoft, Active Directory, Outlook, Windows, Windows NT, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.The names of actual companies and products mentioned herein may be the trademarks of their respective owners.Table of ContentsiiiTable of ContentsIntroduction1Requirements and Setup3Using the Mailbox Merge Program to Reduce Downtime3For Exchange Server5.53For Exchange2000 or Exchange20036Using Mailbox Merge as a Brick-Level Backup Agent7Migrating User Data between Organizations and Sites8Extracting Data from the Dumpster9Extracting Folder Rules10Extracting Data from a Damaged Private Microsoft Exchange Information Store11What Occurs When the Merge Program Encounters a Corrupted Message11Overwriting All Existing Data in the Target Store11Overwriting Older Existing Data in the Target Store12Removing Particular Messages from the Source Store12Limitations of the Mailbox Merge Program15Modes of Operation17Differences between Interactive and Batch Mode19Command-line options21Logging23Running the Mailbox Merge Program25Interactive Mode25Selecting Merge Procedure25Data Selection Criteria27Selecting Databases36Selecting Mailboxes37Selecting the Default Mailbox Locale38Selecting the Target Directory39Saving Program Settings39Merge Process Status41Support for .Ini File in Interactive Mode42Batch Mode42Minimum Batch Mode Settings42Specifying Mailboxes to Be Processed42Specifying Different Target Mailboxes43Using ExMerge.exe to Migrate Data Between Sites or Organizations44Working Against Mailboxes Homed on Different Servers45Specifying Folders to Be Ignored45Specifying Folders to Be Processed46Selecting Messages by Date46Selecting Messages Using the Message Modification Time47Archiving Data from a Mailbox47Saving Folder Permissions47Saving Folder Rules47Extracting Data from the Dumpster47Removing Specific Messages48Redirecting Messages to Another Folder49Running the Program Against Multiple Servers Without Customizing the .Ini File49Specifying a Range of Mailboxes to Be Processed50Running the Mailbox Merge Program Using the Windows Scheduler51Using the Mailbox Merge Program in Non-US English Environments53Localized Provider Names53Localized Folder Names54Copying Data54Renaming Folders55Algorithm to Determine the Number of Threads Used by ExMerge.exe57.Ini File Settings59DomainControllerForSourceServer59SrcServerLDAP-Port60DestServerName60DomainControllerForDestServer60DestServerLDAP-Port61SelectMessageStartDate61SelectMessageEndDate61FileContainingListOfMessageSubjects62SubjectStringMatchCriteria62FileContainingListOfAttachmentNames62AttachmentNameStringMatchCriteria63FoldersProcessed63ListOfFolders63FileContainingListOfFolders63ApplyActionToSubFolders64LogFileName64LoggingLevel64DataDirectoryName65FileContainingListOfDatabases65RestoreDB65DelimiterUsedInMailboxFile65FileContainingListOfMailboxes66StartingIndex66EndingIndex67DateAttribute67DataImportMethod67ReplaceDataOnlyIfSourceItemIsMoreRecent68CopyUserData68CopyAssociatedFolderData68CopyFolderPermissions69CopyDeletedItemsFromDumpster69RemoveIntermediatePSTFiles69UseThisPSTFileForAllMailboxes69LocalisedPersonalFoldersServiceName70LocalisedExchangeServerServiceName70MapFolderNameToLocalisedName70RenameFoldersBasedOnFolderMappings71Folder Name Mappings72RenameSpecialFolders72International72DefaultLocaleID72UseLastLogonLocaleID73Tips for Running the Mailbox Merge Program75Common Problems77The Server SVR Specified in the .ini File Is Inaccessible or Is Not a Microsoft Exchange Server77Problems Getting Mailboxes on a Server77Error Configuring Message Service (MSEMS)78Error Opening Message Store (MSEMS)78Error Creating Message Service (MSPST MS)78Error Configuring Message Service (MSPST MS)78Error Opening Message Store (MSPST MS)79Store MSPST MS Was Not Opened80Store MSEMS Was Not Opened80Error Accessing Directory Object for DN80The Ordinal 6883 Could Not Be Located in the Dynamic Link Library MFC42.DLL81The Dynamic Link Library Could Not Be Found in the Specified Path81Error Running the Program on a Computer with Outlook2000 Installed81No Information Written to the Log File82MapFolderNameToLocalisedName and RenameFoldersBasedOnFolderMappings Do Not Work with Double Byte Character Set (DBCS) Languages82Introduction4IntroductionThe Microsoft Exchange Mailbox Merge Program (ExMerge.exe) enables a Microsoft Exchange administrator to extract data from mailboxes on an Exchange server and merge this data in mailboxes on another Exchange server. This is especially useful during disaster recovery. The program can also replace existing data instead of merging new data if specified by the administrator.The program copies data from the source server to personal folders (.pst) files and then merges the data in the .pst files into mailboxes on the destination server. Before using this program, read the section that follows about the limitations of ExMerge.exe.Note ExMerge.exe should be run only from Exchange2000 Server or Exchange Server2003 or from computers that have the Exchange2000 or Exchange 2003 administrative tools loaded. ExMerge.exe can be run against Exchange5.5, Exchange2000, and Exchange2003.In this document, unless otherwise noted, Windows refers to Windows2000 operating system or later versions. Earlier versions of Windows, such as Windows NT4.0, are specified as required.Requirements and Setup13Requirements and SetupYou must run ExMerge.exe on a computer that is using the Exchange2000 or Exchange 2003 administrative tools. It is recommended that you run ExMerge.exe on a dedicated management station that has Exchange administrative tools installed, instead of running ExMerge.exe on an Exchange server. You can run ExMerge.exe against Exchange5.5, Exchange2000, and Exchange2003 servers.For this program to work against an Exchange5.5 server, you must log on to Windows with the Microsoft Exchange Service Account or have Service Account administrative credentials at the organization, site, and configuration levels of the Microsoft Exchange Directory. If you run ExMerge.exe in a cross-forest scenario (where the user account and user mailbox are located in separate Windows forests), you must have a two-way trust between the forests.ImportantMake sure that you log on with an account, such as Backup Operators, that has Receive As and Send As permissions on all the Exchange mailboxes.Using the Mailbox Merge Program to Reduce Downtime When servers are experiencing problems starting the Microsoft Exchange Information Store service, ExMerge.exe can be used to significantly reduce downtime. In this case, downtime is defined as the time when users cannot send and receive mail (as opposed to being able to access old folders and messages).The following steps explain the procedures to follow for Exchange5.5, and Exchange2000 or Exchange2003:For the following procedures, assume that the production server is named PROD_SRVR and another recovery server is named RECOV_SRVR. Assume that RECOV_SRVR has the same version of Exchange Server installed on it as PROD_SRVR, including service packs, and has the same Exchange organization and site names. This server should not be added to the existing production site. Also assume that the location of the information store databases and transaction log files is the same on both servers.Additionally, we assume that the Exchange store on the production server, PROD_SRVR, is having trouble starting, and that all Exchange services on RECOV_SRVR are working correctly.For more information, see the Exchange Server 2003 Disaster Recovery Operations Guide (/fwlink/?LinkId=30250), or Disaster Recovery for Microsoft Exchange 2000 Server (/fwlink/?linkid=24619). For more information about Recovery Storage Groups, see Using Exchange Server2003 Recovery Storage Groups (/fwlink/?LinkId=23233).For Exchange Server5.51. Reset the Exchange store on PROD_SRVR:a. Rename the EXCHSRVRMDBDATA directory on each drive on PROD_SRVR to EXCHSRVRMDBDATA.BAK.b. Create a new EXCHSRVRMDBDATA directory on each drive on PROD_SRVR.c. Start the Exchange Information Store service on PROD_SRVRd. Users on PROD_SRVR are now able to send and receive mail but currently have no old mail.e. If you have to, back up the data in the EXCHSRVRMDBDATA.BAK directories.2. On RECOV_SRVR, stop the Exchange Information Store service.3. Move all files from the EXCHSRVRMDBDATA directories on every drive of the RECOV_SRVR server.4. If a valid online backup is available for the information store on PROD_SRVR:a. Verify that the MDBDATA directories on all drives of RECOV_SRVR are empty.b. Copy any transaction logs generated on PROD_SRVR from the EXCHSRVRMDBDATA.BAK directory that contains the logs to the EXCHSRVRMDBDATA directory on RECOV_SRVR. Verify that this is the directory that should contain the transaction logs. For information about where to put the transaction logs, see the DB Log Path Registry value under HKEY_LOCAL_MACHINESystemCurrentControlSetServicesMSExchangeISParametersSystem.c. Restore the online backup to RECOV_SRVR.d. Start the Microsoft Exchange Information Store service.5. If a valid online backup is not available, you may have to repair the existing Exchange store databases:a. Back up the original databases on PROD_SRVR in the EXCHSRVRMDBDATA.BAK directory.b. Copy the PRIV.EDB and PUB.EDB files to the RECOV_SRVR.c. Contact Microsoft Product Support Services before you proceed.6. Assume that the Microsoft Exchange Information Store service on RECOV_SRVR is restored from backup or has been repaired and is running correctly. This information store is typically large and contains all the user data, except for the data that was generated after the Microsoft Exchange Information Store service was reset on PROD_SRVR.7. Stop the Microsoft Exchange Information Store service on RECOV_SRVR and PROD_SRVR and swap the MDBDATA directories on both servers. If PROD_SRVR has sufficient disk space to hold the original PRIV.EDB and PUB.EDB, in addition to the databases created after the Information was reset, you can additionally reduce downtime by the following steps:a. Stop the Microsoft Exchange Information Store service on RECOV_SRVR only. b. On PROD_SRVR, on each drive that contains an EXCHSRVRMDBDATA directory, create a new directory named EXCHSRVRMDBDATA.NEW.c. On RECOV_SRVR, rename the EXCHSRVRMDBDATA directory on each drive to MDBDATA.NEW.d. On RECOV_SRVR, create a new EXCHSRVRMDBDATA directory on each drive.e. Copy the PRIV.EDB and PUB.EDB files from the MDBDATA.NEW directory on RECOV_SRVR to the appropriate MDBDATA.NEW directory on PROD_SRVR. This is the directory on the drive that contains the currently used PRIV.EDB or PUB.EDB. Therefore, if the location of the PRIV.EDB on PROD_SRVR is E:EXCHSRVRMDBDATA, copy the PRIV.EDB from RECOV_SRVR to E:EXCHSRVRMDBDATA.NEW and do the same for the PUB.EDB file.f. After you copy the PRIV.EDB and PUB.EDB files to the MDBDATA.NEW directory on PROD_SRVR, stop the Exchange Information Store service on PROD_SRVR.g. On PROD_SRVR, rename the EXCHSRVRMDBDATA directories on each drive to MDBDATA.RESET.h. On PROD_SRVR, create new EXCHSRVRMDBDATA directories on each drive.i. On PROD_SRVR, move the PRIV.EDB and PUB.EDB files from the MDBDATA.NEW directory to the MDBDATA directory.j. Copy the PRIV.EDB and PUB.EDB files from the MDBDATA.RESET directory on PROD_SRVR to the EXCHSRVRMDBDATA 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_MACHINESystemCurrentControlSetServicesMSExchangeISParametersPrivate and HKEY_LOCAL_MACHINESystemCurrentControlSetServicesMSExchangeISParametersPublic.k. Now you have exchanged the PRIV.EDB and PUB.EDB files between PROD_SRVR and RECOV_SRVR. The MDBDATA directories on both servers should contain only the PRIV.EDB and PUB.EDB files, and no other files should be in these directories. l. The PRIV.EDB and PUB.EDB 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 PRIV.EDB and PUB.EDB 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 command prompt, change to the EXCHSRVRBIN directory, and run the following command: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 complete 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 completed.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 ExMerge.exe against RECOV_SRVR, and merge all data from RECOV_SRVR into PROD_SRVR. You can use the one-step merge procedure or the two-step merge procedure. If you use the latter, you must first extract data on RECOV_SRVR to .pst files and then run ExMerge.exe again, against PROD_SRVR and merge the data from the .pst files into the mailboxes on PROD_SRVR. It is recommended 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 Outlook 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 become 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 ExMerge.exe 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 server-based public folders.For Exchange2000 or Exchange2003The process of using ExMerge.exe 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 t