Google Apps Migration for Lotus Notes Installation & Administration Guide - Manual (Page 50)

50 Google Apps Migration for Lotus Notes Installation & Administration Guide
When this feature is enabled, failures encountered during migration to the Google servers are
also captured and stored as exception documents on the migration profiles.
Enable this option only to assist with the resolution of a problem, because it has a detrimental
effect on performance.
Set to Disabled to prevent the system from logging document-level events.
Router delay
Enter the number of seconds to have the system wait between successive messages when
moving mail from the users’ mail files to the Feeder databases.
Increase this delay if you experience router errors or flooding during the migration process.
You can also increase the number of MAIL.BOX files to load balance the system and avoid
flooding. Having multiple MAIL.BOX files allows the server to multi-thread mail delivery and
thereby optimize performance.
Create Gmail labels for all Notes folders
By default, a label is created in Gmail as a property of migrated mail. This means that if you
have empty Notes folders, then these will not appear as labels in Gmail following migration.
Set this field to ‘Enabled’ if you want the system to create a label in Gmail for all Notes folders
found, including empty folders.
Out of Office agent checks
The system stamps each mail message that is migrated with a migration status value. In some
rare instances, this update could trigger an out of office notification to the original sender of the
message if the Out of Office agent was enabled. Because of this, the system does not process
a user if the agent is enabled.
You can override this behavior by setting this field to “Disabled”. This can be useful if you are
migrating only calendars and/or contacts. If you are migrating mail, you must determine for
yourself that overriding the default behavior does not cause out of office notifications to be
generated in your environment for any user that has the agent enabled.
Check and remove mail quotas before migration
Set to Enabled to have the system remove quotas as part of its preprocessing checks.
Where mail quotas are used and a user's quota is nearly reached or has been exceeded, the
system is not able to write the migration-status values back to the database. This will cause
the system to repeat the migration multiple times for affected users.
By default, the system attempts to remove the quota on mail files as it processes them. For
this to work, you should ensure that the ID you use to sign the GAMLN templates is also listed
as an Administrator on each of your mail servers.
Set to Disabled if you do not use quotas or you want to use Domino Administrator to remove
quotas on all mail databases prior to migration.