Installation & Administration Guide Manual

93
Troubleshooting Chapter D
Logging
GAMLN uses the following types of logging:
The migration agents that run in the Feeders write summary and statistical information to
agent log documents in the Administration database and to each migration profile. Processing
information for each profile can be viewed by using the Migration Events action at the view
level or by selecting the Activity Log tab on the profile.
1. Processing errors, such as a failure to migrate because the migration agents cannot
access the original Notes mail file or database, are written to the migration profiles. Such
profiles are shown in the “Processing Failures” view.
2. Agents that run in the Administration database, such as the Directory Registration and
User Provisioning agents, write activity to a Notes Log database which can be found in the
same folder where the migration software is installed.
3. By enabling detailed logging at the site level, a Notes Log database is created for each
feeder, and the migration agents write details about all content migrated to these logs.
Migration exceptions are also captured on the migration profile when detailed logging is
enabled.
How GAMLN handles errors
In general, high-level errors (for example, errors associated with accessing resources on the
Domino server, or logging into Google Apps) are written to the logs and migration profile.
Low level errors (for example, failure to migrate a particular message) are:
• Shown as an increment to the error count for the user or database (see Migration
Profiles > With Errors view)
• Optionally captured in a separate Notes document and visible from the Exceptions tab on
the migration profile