You can migrate directly from any of the NetWare platforms that support GroupWise as listed in the GroupWise documentation.
Although other supported platforms are listed in the GroupWise documentation, this guide focuses on migrating to OES 11 SP3.
For specific planning instructions, see the following information:
GroupWise 7:
Planning Your Basic GroupWise System
in the GroupWise 7 Installation Guide.
GroupWise 8:
Planning a Basic GroupWise System
in the GroupWise 8 Installation Guide.
GroupWise 2012:
Planning Your GroupWise Server Migration
in the GroupWise Server Migration Guide.
Probably the most important tip to a successful migration is to make sure, before starting the migration, that the source NetWare server has the latest GroupWise support pack installed, and that GroupWise is running without problems.
The GroupWise documentation includes thorough migration planning instructions in Planning Your GroupWise Server Migration
in the GroupWise Server Migration Utility Installation and Migration Guide.
Earlier Version of GroupWise: If you are running an earlier version of GroupWise on NetWare, you must upgrade to GroupWise 7 or GroupWise 8 with the latest support pack before migration to OES 11.
Migrating vs. installing GWIA and WebAccess: Novell Support recommends deleting the NetWare-based GWIA and WebAccess objects and then installing new GWIA and WebAccess services on OES, even though there are instructions for migrating the GWIA and WebAccess services from NetWare to OES in the documentation.
You have two options for migrating GroupWise from NetWare to OES 11 SP3:
GroupWise Server Migration Utility: This lets you identify the components (Post Office agents, etc.) to be migrated from NetWare to OES and then installs GroupWise, configures the agents, and migrates the data—all in real time. The process is flexible, allowing you to choose which components to migrate when.
During the initial transfer, the original server is maintained, letting you continue to run GroupWise on NetWare until the migration is complete and you are satisfied with the results.
After the initial transfer, the utility guides you through testing the system on the new OES server, and then when you are ready to switch, it migrates any data that was altered since the initial transfer and activates GroupWise on the OES server. This is the only point in the process when post office agents are taken down.
Manual Process: Although it is much more involved and labor-intensive, some prefer to migrate GroupWise manually. The results are the same as the automated process, if all of the instructions are followed carefully.
Some administrators have incorrectly assumed that they must install GroupWise on the target server prior to the migration. Actually, GroupWise is installed on the OES 11 SP3 server as part of the migration.
You cannot upgrade GroupWise as part of the migration to OES.
Table 11-1 Instructions for Manual GroupWise Migrations
|
GroupWise Version |
See |
|---|---|
|
GroupWise 7 |
|
|
GroupWise 8 |
|
|
GroupWise 2012 |
|
Table 11-2 Instructions for an Automatic GroupWise Migration
|
GroupWise Version |
See |
|---|---|
|
GroupWise 7 and GroupWise 8 |
Migrating GroupWise as part of a Transfer ID migration is essentially a three-phase process.
If your NetWare server is currently running GroupWise, you must run the GroupWise Server Migration Utility before performing the Transfer ID migration.
The GroupWise Server Migration Utility does the following:
It moves all GroupWise data and agents from a NetWare source server to an OES target server.
It sets up the GroupWise Agents to run on the IP address and DNS name of the target OES server.
For instruction on running the GroupWise Server Migration Utility, see the GroupWise Server Migration Guide.
You should verify that GroupWise has migrated correctly and is running successfully for several weeks in the OES environment before completing the Identity Swap.
After the GroupWise migration, a copy of the GroupWise data is still located on the NetWare server. After you perform the Transfer ID migration, the GroupWise data is no longer accessible on the NetWare server.
In ConsoleOne, change the IP address or DNS names for the POA, WebAccess, and GWIA to reflect the NetWare server IP address or DNS information. This is only required for the agents that were transferred using the GroupWise Server Migration Utility.
Ensure that the changes have replicated through the system.
If a domain was transferred during the GroupWise Server migration, change the IP address or DNS name for the MTA.
Shut down the GroupWise agents running on the OES server.
Perform the Identity Swap.
After the Identity Swap has completed, bring up the GroupWise agents on the Linux server.
Product Documentation: