7.10 Post-Migration Tasks for a Post Office

  1. Check the Server Migration Utility log file to verify the success of the migration.

    The log file is named gwsvrmig_mmddyyyy_nnnn.log and is found in the utility installation folder if the utility can write to that location. Otherwise, it is found in the /temp folder. It provides a migration summary and a listing of all actions taken by the Server Migration Utility.

  2. (Conditional) If you see problems in the utility log file, check the GroupWise Database Copy utility (DBCopy) log file to obtain additional detail. The DBCopy log file is named mmddgwbk.nnn and is found in the post office folder on the Linux server.

  3. (Conditional) If you have problems starting the migrated POA, see Section A.0, Troubleshooting Post-Migration Problems.

  4. (Conditional) If the post office migration is not successful using the Server Migration Utility, migrate the post office manually.

    See Section 11.0, Manually Migrating a Post Office and Its POA to Linux.

  5. Check the migrated POA startup file (post_office.poa in the /opt/novell/groupwise/agents/share folder on the Linux server) to see if any startup switches have been commented out during migration, and adjust them as needed, for the new Linux environment.

    The Server Migration Utility comments out any startup switches whose values contain NetWare or Windows paths or the IP address of the source server.

  6. Set up a GroupWise name server to help GroupWise clients connect to the new IP address, as described in the following section of the GroupWise Administration Guide for your version of GroupWise:

  7. (Conditional) If you copied remote document storage areas to the Linux server during the migration process, copy them again with a slightly different dbcopy command:

    ./dbcopy -m -i mm-dd-yyyy -b /storage_area_folder 
                                              /destination_folder

    This copies only the files that have been modified since you first copied the document storage area, like an incremental backup.

  8. Review your scheduled backups to ensure that they are set to run correctly with the new system changes.

  9. Ensure that your Restore Area is now available from the Linux POA.

  10. (Conditional) If you want to use the Monitor Agent to monitor the migrated POA on Linux, migrate the Monitor Agent manually.

    See Section 15.0, Manually Migrating Monitor to Linux.

  11. (Conditional) If you want to migrate domains now, see Section 8.0, Migrating a Domain and Its Agents to Linux.

  12. When you are completely finished with your migration to Linux, see Section 9.0, What’s Next for information about cleaning up the servers that you are no longer using for GroupWise.