There is no precise way to estimate how long it will take to migrate a particular post office or domain to Linux. The major determining factors are:
Amount of data to migrate
Connection speed between the source and target servers
Fortunately, the Server Migration Utility makes it easy to perform any number of practice runs. You can safely run the Server Migration Utility on a live post office or domain as long as you do not make any of the configuration changes in ConsoleOne that would be made during a real migration.
You can expect to see the Migration Utility move about 6 GB of data per hour. If performance is substantially slower than this, check your network configuration for slow links and make sure that none of the following processes are running while you are migrating data:
GroupWise maintenance activities such as Mailbox/Library Maintenance or Nightly User Upkeep
Indexing of messages and documents
Backups of GroupWise databases
These activities can hold files open and cause the Migration Utility to wait, thus slowing the migration process.
One type of data that you might want to move out of post office directories and domain directories to speed migration is agent log files, especially if any of the following situations apply:
You have been using the verbose log level.
You retain log files for a long period of time.
You have been generating MTA message log files.
Agent log files are stored in the following locations:
Table 4-1 GroupWise Agent Log File Locations
|
Agent |
Log File Location |
|---|---|
|
POA |
|
|
MTA |
|
|
Internet Agent |
|
|
WebAccess |
GroupWise 8: domain\wpgate\webac80a\000.prc GroupWise 7: domain\wpgate\webac70a\000.prc |