Novell Doc: GroupWise 7 Installation Guide - Finalizing the Post Office Migration

20.4 Finalizing the Post Office Migration

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.
On the Linux server, run DBCopy again to copy the post office:
```
./dbcopy -m -i mm-dd-yyyy -s /post_office_directory 
                             /destination_directory
```
When you run DBCopy the second time and include the -i switch with the date of the initial copy, it copies only files that have been modified since the initial copy, like an incremental backup. 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.
If you migrated a document storage area to the Linux server in Step 9 in Section 20.2, Performing the Post Office Migration, run DBCopy again to copy the document storage area with the files modified since the first copy:
```
./dbcopy -m -b -i /storage_area_directory /destination_directory
```
When the copy operation is finished, unmount the document storage area.
Run the standalone GroupWise Check utility (GWCheck), installed in Step 7 in Section 20.1, Preparing for the Post Office Migration, with the storelowercase support option to convert the filenames and directory names stored inside GroupWise databases in the post office to lowercase:
1. In the Database Type box, select Post Office.
2. Browse to and select the post office database in its new location, then specify the post office name.
3. In the Object Type box, select Post Office.
4. In the Support Options field on the Misc tab, specify storelowercase.
5. Click Run to run GWCheck.
  
  If you need to run GWCheck in a text-only environment, see Using Text-Based GWCheck (gwcheckt) in Databases in the GroupWise 7 Administration Guide for additional instructions.
If your GroupWise system includes an Internet Agent that is used for POP and IMAP e-mail clients, check the link between the Internet Agent and the post office:
1. In ConsoleOne, right-click the Internet 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.
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.
Start the Linux POA with or without a user interface, as described in Starting the Linux Agents with a User Interface or Starting the Linux GroupWise Agents as Daemons.
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, as described in Simplifying Client/Server Access with a GroupWise Name Server in Post Office Agent in the GroupWise 7 Administration Guide, users are automatically redirected to the new IP address when they start GroupWise.
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.
If you migrated a document storage area to the Linux server in Step 9 in Section 20.2, Performing the Post Office Migration, delete the old document storage are on the NetWare or Windows server.
Set up a backup procedure for the post office in its new location on Linux, as described in GroupWise Database Copy Utility or Target Service Agents in Databases in the GroupWise 7 Administration Guide.
If desired, uninstall the POA software to reclaim disk space on the NetWare or Windows server. See Uninstalling the NetWare GroupWise Agents or Uninstalling the Windows GroupWise Agents.