How do I Increase MNE migration throughput and performance? (4323160)

Below are some considerations to help improve migration performance with Migrator for Notes to Exchange (MNE).

1. Have the Domino server as close to the MNE migration server as possible. It is typically slower to get data out of Domino than it is to get data into Exchange.
2. Point 1, above, is presuming that an Exchange throttling policy has been created and assigned to the MNE Exchange migration admin account. By default, Exchange throttles all users, so the Exchange migration admin must be assigned to an unrestricted throttling policy for best performance.
3. If you have many servers globally and slow links, either use Domino replication to get the mail replica as close the MNE migration server as possible, or setup a migration machine near that remote office. It is typically faster to migrate mail files which are closer to the migration server.
4. When migrating data from slow, remote or global sites, MAPI over HTTP may provide up to 25% better performance. See solution SOL214759 on how to set this up.
5. Install more RAM on the MNE migration server.
6. Move the windows temp file to another disk on the MNE migration server. This will reduce Disk I/O.
7. Copy mail files to another server such as a file server and migrate from these file copies. You can then point the migration to use these files instead of looking at the Domino server. See solution SOL27457 on how to do this.
8. Try the migration off peak and out of office hours.
9. Because of the structure of calendar data, this migrates much slower than mail data.
10. Typically, customers report the best throughput when using 8 - 12 migration threads.
11. Ideally in large migrations have SQL on another disk/machine
12. Have multiple migration machines.
13. Note that re-migrating can cause a large amount of RAM to be used. It also uses many mapi requests against the exchange mailbox.
14. Verify that the MNE Exchange migration admin user's mailbox is located in the same site as the destination Exchange server for the users you are migrating.
15. Adjust the network load-balancers in the environment.
16. Check to see if logging is running in verbose mode. Noticed that throughput went from 500MB to 2GB because of the extra logging.
17. Verify Antivirus software is not installed and running on the migration console.