11.4 Finalizing the Post Office Migration

  1. On the NetWare or Windows server, stop the POA for the post office. If multiple POAs are currently running for the post office, stop all POAs.

    GroupWise users can no longer access their Online mailboxes.

  2. On the Linux server, run DBCopy again to copy the post office:

    ./dbcopy -m -s -p /post_office_directory /destination_directory
    

    The -s switch indicates that this is the second pass of the migration process, during which the post office queue directories (wpcsin and wpcsout) are copied. The second DBCopy process should be substantially shorter than the first one.

  3. (Conditional) If you migrated a document storage area to the Linux server in Step 11 in Section 11.2, Performing the Post Office Migration, run DBCopy again to copy the document storage area and include files modified since the first copy:

    ./dbcopy -m -i mm-dd-yyyy -b /storage_area_directory /destination_directory
    

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

  4. (Conditional) If your GroupWise system includes a GWIA that is used for POP and IMAP email clients, check the link between the GWIA and the post office:

    1. In ConsoleOne, right-click the GWIA object, then click Properties.

    2. Click Post Office Links.

    3. Make sure that the link shows the correct IP address where the Linux POA for the migrated post office is now running.

  5. (Conditional) If your GroupWise system includes the WebAccess Agent, check the link between the WebAccess Agent and the migrated post office:

    1. In ConsoleOne, right-click the WebAccess Agent object, then click Properties.

    2. Click Post Office Links.

    3. Make sure that the link shows the correct IP address where the Linux POA for the migrated post office is now running.

  6. Start the Linux POA with or without a user interface, as described in the following section of the GroupWise Installation Guide for your version of GroupWise:

  7. Enable user logins for the post office, as described in the following section of the GroupWise Administration Guide for your version of GroupWise.

  8. (Conditional) If necessary, provide GroupWise users with the new IP address where the Linux POA is now running, so that they can start GroupWise again and access their Online mailboxes on the Linux server.

    If you are running a GroupWise name server, users are automatically redirected to the new IP address when they start GroupWise, as described in the following section of the GroupWise Administration Guide for your version of GroupWise.

  9. When the Linux POA is running smoothly for the new post office location, delete the old post office directory structure from the NetWare or Windows server.

  10. (Conditional) If you migrated a document storage area to the Linux server in Step 11 in Section 11.2, Performing the Post Office Migration, delete the old document storage area on the NetWare or Windows server.

  11. Set up a backup procedure for the post office in its new location on Linux.

    If you want to use the GroupWise Database Copy utility (DBCopy), you create a copy of the post office and then back up the copy, which requires double the post office size in disk space. For instructions, see the following section in the GroupWise Administration Guide for your version of GroupWise:

    If you want to use the GroupWise Target Service Agent (TSAFSGW), this extra disk space is not required. However, having a recent complete online backup available can be helpful in a variety of circumstances. For instructions, see the following section in the GroupWise Administration Guide for your version of GroupWise:

  12. (Optional) Uninstall the old POA software to reclaim disk space on the NetWare or Windows server.

    See Section 9.0, What’s Next.