How does Migrator for GroupWise (MFG) deal with moves, deletions, or changes made in items in GroupWise, on migrating the mailbox again?
What is the difference in the three remigration modes (default, update and change) with respect to the above scenarios?
The product documentation does not currently provide information on how it would deal with the above scenarios during remigration. A change request, ST70313, has been submitted to Development for consideration in a future release of GroupWise Migrator for Exchange.
Remigration can operate in either of three modes, determined by a Boolean program parameter in the [Exchange] section of gwmigapp.ini:
... where the parameter value is a single digit, 0, 1 or 2
RemigrateMode=1 (Default mode)
If the program detects a duplicate message in Exchange, the GroupWise source message will not be migrated, leaving the previously migrated copy in Exchange.
RemigrateMode=0 (Update mode)
If Migrator for GroupWise detects a duplicate message in Exchange, the message will be deleted in Exchange and then remigrated from the GroupWise source.
RemigrateMode=2 (on change)
If Migrator for GroupWise detects a duplicate message in Exchange, it verifies the last modified time to see if the source message has been modified. If the source message is newer than the copy in Exchange, it will delete it and remigrate the message from GroupWise. If the message in Exchange is newer, MFG will leave the previously migrated copy in Exchange.
The key word is "duplicate". An item has to exist in the same location (folder) in both GroupWise and Exchange and have the same messageId to be considered a duplicate.
All remigration modes behave similarly with respect to deletions and moves made in GroupWise after the previous migration. However, they behave differently for changes made in GroupWise.
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Nutzungsbedingungen Datenschutz