21.2 Performing the Domain Migration

  1. On the NetWare or Windows server, stop the MTA for the domain.

  2. If the domain has gateways, stop the gateways.

  3. In the /opt/novell/groupwise/agents/bin directory, use DBCopy to copy the domain directory from the NetWare or Windows server to the new directory on the Linux server.

    ./dbcopy -m /domain_directory /destination_directory

    The -m switch indicates that DBCopy is being used for migration to Linux. The domain_directory variable includes the Linux mount location (for example, /mnt), the mount point directory, and the full path to the domain directory on the NetWare or Windows server. The destination_directory variable is the directory you created on the Linux server in Step 5 in the previous section.

    DBCopy creates a log file named mmddgwbk.nnn. The first 4 characters represent the date. A three-digit extension allows for multiple log files created on the same day. The log file is created at the root of the destination domain directory. Include the -v switch in the dbcopy command to enable verbose logging for the domain migration.

    DBCopy is typically used for backing up your GroupWise system, but when you use the -m switch to migrate a domain, it changes directory names to lowercase as required on Linux and copies the message queue directories as well as well as the GroupWise databases in the domain. For more information about DBCopy, see GroupWise Database Copy Utility in Databases in the GroupWise 7 Administration Guide.

  4. If you are using the /work startup switch to place the MTA working directory (mslocal) outside the domain directory structure:

    1. Copy the mslocal directory to the Linux server so that no messages en route between users are lost.

    2. In the mslocal directory structure, rename files and directories that contain uppercase letters to all lowercase.

  5. If your Linux environment includes the X Window System, run the GroupWise Installation program to install the Linux MTA for the domain, as described in Installing the GroupWise Agents on Linux.

    or

    If the X Window System is not available, run the text-based GroupWise Installation program, as described in Installing the GroupWise Agents Using the Text-Based Installation Program.

    If you need to perform the installation from a remote location, you can use ssh to access the remote Linux server. Copy the GroupWise 7 Administrator for Linux CD to the server where you have migrated the domain, then run the text-based Installation program to install the MTA on the Linux server.

  6. Change to the /opt/novell/groupwise/agents/bin directory.

  7. If the X Window System is available, enter the following command to start the Linux MTA to verify that it runs for the domain in the new location:

    ./gwmta --show --home /domain_directory

    The --show switch starts the MTA with a user interface. The --home switch provides the location of the domain.

    You should see the MTA server console described in Starting the Linux Agents with a User Interface. If the MTA server console does not appear, review the preceding steps to verify that all steps have been followed. For additional assistance, see Message Transfer Agent Problems in Strategies for Agent Problems in the GroupWise 7 Troubleshooting 2: Solutions to Common Problems.

    or

    If the X Window system is not available:

    1. Enter the following command to start the Linux MTA to verify that it runs for the domain in the new location:

      ./gwmta --home /domain_directory --noconfig 
        --ip mta_server_ip_address --httpport 7180

      The --home switch provides the location of the domain. The --noconfig switch prevents the MTA from reading configuration information from eDirectory; the current eDirectory information is obsolete because the domain has been migrated. The --ip switch provides the IP address of the server where the MTA is running. The -httpport switch enables the MTA Web console and provides the port number.

      To simplify this test, do not use an SSL connection.

    2. In an appropriate environment, open a Web browser and display the following URL:

      http://mta_server_ip_address:7180

      You should see the MTA Web console described in Monitoring the Linux GroupWise Agents from Your Web Browser. If the MTA Web console does not appear, review the preceding steps to verify that all steps have been followed. For additional assistance, see Message Transfer Agent Problems in Strategies for Agent Problems in the GroupWise 7 Troubleshooting 2: Solutions to Common Problems.

  8. After verifying that the MTA starts successfully for the domain in the new location on Linux, stop the MTA, as described in Stopping the Linux GroupWise Agents.

  9. If you plan to use SSL on Linux, create new certificate and key files for the Linux server and place them in the /opt/novell/groupwise/agents/bin directory, the default location where the MTA looks for certificate and key files.

    For instructions on creating certificate and key files, see Server Certificates and SSL Encryption in Security Administration in the GroupWise 7 Administration Guide

  10. Continue with Reconfiguring the Domain in ConsoleOne.