Scope:ArchiveOne Enterprise, all versions
When migrating a mailbox from Exchange 2003 (or Exchange 2007) to Exchange 2010 SP1, the migration process can fail if the mailbox contains 'corrupt' mails. The process can be set with a maximum value for the number of corrupt mails that will be allowed in the migrated mailbox.
However it has been observed that, in some cases when migrating a mailbox that has been archived using ArchiveOne the operation fails because all of the message 'stubs' are flagged as being 'corrupt' mails.
The symptoms of this problem are as follows:
*The mailbox has been archived with version 5.6 (or earlier) of ArchiveOne Enterprise (Policy).
*The mailbox contains numerous message stubs.
*The mailbox is being migrated to Exchange 2010 SP1 (or later) using standard Microsoft approved procedures.
*The migration process is set to fail if more than a specified number of 'corrupt' messages exist in the mailbox.
*The number of message stubs in the mailbox greatly exceeds the number of allowed 'corrupt' messages.
Recent versions of Exchange (from Exchange 2010 SP1 onwards) have deprecated a number of previously valid MAPI properties. One of these deprecated properties was used by older versions of ArchiveOne Enterprise (Policy) and added into the MAPI properties of message stubs. As a mailbox may contain many thousands of archived message stubs then potentially there will be a great number of messages that Exchange 2010 will detect as being 'corrupt'.
There are a number of possible workarounds to this issue as follows:
*Increase the number of acceptable 'corrupt' mails that the migration process will accept to a very high number to accommodate all of the archived message stubs. This runs the risk of migrating actual corrupt (both archived and non-archived) mails and so should only be used with caution.
*Move all the archived message stubs out of Exchange into a PST, migrate the mailbox, and import the message stubs back into the moved mailbox. It is possible to write a policy in ArchiveOne Enterprise (Policy) to move message stubs (all of which have the message class of 'IPM.Note.arch2') to a PST, preserving the Exchange folder hierarchy. The downside of this operation is that PSTs need to be added back to user mailboxes post-migration which is usually a manual operation and so unsuitable for large numbers of mailboxes.
*Delete all the message stubs. Again it is possible to perform this action using a policy but this will mean that end users won't have immediate visibility of their archived items. This workaround is best used if an alternative method of users accessing their archived items is available, such as the "Search Archive" folder for users on ArchiveOne Enterprise (Policy) version 6.5 or later.
The resolution to this problem is to ensure that all current archived messages have the deprecated MAPI property removed. This is done as follows:
1. Confirm you have at least ArchiveOne version 188.8.131.528 or later installed. It is highly recommended you upgrade to the latest version if not already installed:
HOWTO: Perform a upgrade of ArchiveOne Policy by uninstalling/reinstalling
2. If you are not running at least version 6.3 or later and are not going to upgrade, then you will have to add the following registry keys on the Archive server:
1. Open the Registry Editor by running 'regedit'.
2. Browse to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AOnePolService\Parameters.
3. Right-click to create a new 'DWORD' named 'RemoveNonEx2010Props' with value '1'.
4. Close the Registry Editor.
5. Open the Microsoft Services console by running 'services.msc'.
6. Restart the 'Archive One Service' to bring the registry change into effect.Rename the 'Messages to be skipped' database file:
1. On the Archive Server, browse to the server data location which ArchiveOne uses for temporary data.
2. By default this is the installation directory: on v7 or later 'C:\Program Files (x86)\Barracuda\ArchiveOne_PoliciesCheckFiles', or v6.6 or earlier 'C:\Program Files (x86)\C2C Systems\ArchiveOne_PoliciesCheckFiles'
3. The server data location is given in the System Configuration Wizard. You can run this by right-clicking the Status node and selecting ‘Run System Configuration Wizard…’.Rename the file 'MessageToBeSkipped.mdb' to 'MessageToBeSkipped.mdb.OLD'.Create a new policy with the action 'Message Link Reconfiguration' to run against all messages in all mailboxes to be migrated:
HOWTO: Update the retrieval link address in archived messages
1. It is suggested to run the message link reconfiguration policy against one mailbox first and then testing the mailbox can be successfully migrated to Exchange 2010. If the migration succeeds, you can now proceed to run the message link reconfiguration policy against all remaining mailboxes.
If the migration process still fails then it is likely that the mailbox contains mails, or message stubs, that are genuinely corrupt in some way (and it should be remembered that a small percentage of corrupt mails in Exchange is to be expected). You should review the Exchange migration log for more information.
Link to This Page: