IdoNotes (and sleep)

Google Apps Migration for Lotus Notes (GAMLN) - part 6

As we have moved through the Google Apps Migration for Lotus Notes (GAMLN) tool, I have received excellent input form Marie Scott on their trials and knowledge gained as well.  Now that we have the basic architecture decided, the documentation suggests establishing the migration server as a trusted server in the mail server documents (shown below) and signing the templates from Google with a trusted id source such as the server id file.

Here was a key factor I gleaned from the documentation, mainly since we cluster mailfiles between two data centers for redundancy.  Each time a message is migrated it modifies the Last Modified date.  Doing this to large mailfiles can cause heavy network traffic according to the GAMLN documentation.  They suggest you disable replication for each mailfile as you configure that user for migration.

The last step today will be to create the actual administration database we discussed earlier.  Google provides a gmail.migration.ntf template with the Google Apps Migration for Lotus Notes tools.

History of postings on the Google Apps Migration for Lotus Notes (GAMLN) series:

• Intro
• Part 1
• Part 2
• Part 3
• Part 4
• Part 5
• Part 6
• Part 7
• Part 8
• Part 9
• Part 10

blog comments powered by Disqus



On Wednesday, June 2nd, 2010   by Chris Miller        

Next Document | Previous Document