GWMHN FAQ

If you’re migrating from a production database, you might notice the Notes’ user databases are inaccessible during a migration. Migrating data is resource-intensive and can cause your users to lose accessibility to their mailboxes while the migration runs. This is usually temporary.

We recommend you don’t migrate directly from a production mail database. Instead, you should replicate or copy the production mail databases to the migration server. Then, use GWMHN to migrate its local copies or replicas.

You might find another task on the server has locked a mail database. If this occurs, GWMHN tries to access the database each time the feeder agent cycles. If the database remains inaccessible to GWMHN, it’s likely to be inaccessible to other services as well. Contact your Notes administrator to troubleshoot.

An assigned feeder database processes an active user’s database. We recommend you don’t switch a user from one feeder to another. Doing so could potentially migrate the same database content and duplicate data.

If you have to manually assign a feeder database to a profile, make sure you’re not missing or duplicating content in Google Workspace.

A single instance of GWMHN can migrate users from any mail server. However, we recommend you copy the production mail databases to the migration server. Then, set up GWMHN to migrate the local copies. Doing so ensures the migration server processes don’t impact the production servers.

Multiple connections increase the load on the server. Eventually the server resources might run low, causing performance issues. We don’t recommend you point multiple GWMHN servers to the production mail server. Instead, copy the production mail databases to the migration servers. Then, have each GWMHN server migrate the copied databases.

Each migration profile in GWMHN has a Server field, which specifies the server where the mail file is located. The migration agents in the feeder databases use this field and open the mail database on the designated server. How the server field is set depends on how you create the migration profiles. When you register a database, you can choose from the following registry options:

• From directory
• Import from file
• By server

If you choose the From directory or Import from file option, GWMHN accesses the user's home mail server. This is the same server as the mail server listed in the user's Person document in the Domino directory (usually the production server or servers).

If you choose the By server option:

• You can specify the server you want GWMHN to search for mail files. Use this option if you’ve copied data from the production server to the migration servers. In this case, select the migration server to search.
• Make sure you don’t activate the same profile on more than one GWMHN server. Doing so can cause data duplication. We recommend each migration server hosts only the profiles of users it intends to migrate.

You can put an active profile on hold. Doing so ensures the profile is skipped when the migration agent is run. It doesn’t pause or stop the migration if the active profile is being processed.

While trying to get an authorization code during access token setup, you might receive one of the following warning messages in the Chrome Browser:

• "This app is blocked. This app tried to access sensitive info in your Google Account. To keep your account safe, Google blocked this access."
• "Sign in with Google temporarily disabled for this app. This app has not been verified yet by Google in order to use Google sign in."

The cause of the issue is that GWMHN is not on the Google Admin console allowlist as a third-party app. To add GWMHN under App Access Control:

1. Sign in to your Google Admin console.

   Sign in using your administrator account (does not end in @gmail.com).

2. In the Admin console, go to Menu  SecurityAccess and data controlAPI controls.
3. Click Manage third-party app access.
4. Under the Apps tab, click Configure new appOAuth App Name Or Client ID.
5. Enter 815156995542.apps.googleusercontent.com in the search field and click Search.
6. Select GWMHNSelect.
7. Check the OAuth Client ID box and click Select.
8. Select Trusted: Can access all Google services and click Configure.

The GWMHN app appears as a connected app on the App Access Control page.

When users migrate Group archived mail, they should make sure the database template is based on the mail-in database. Otherwise, for example, if messages were accidentally stored in a discussion database, GWMHN replaces the message's "To" field with the group address during the migration.