Migrating Garoon from Linux Environment

This section describes how to migrate Garoon from Linux environment to other servers.

Points to Check before Migration

  • Server migrations should be performed by the following users.
    • On Windows:
      Users who have local Administrator rights on the server machine
    • On Linux:
      Users with root privilege
  • The following must be identical on the source and destination servers to migrate:
    • Garoon versions:
      The revisions must be identical in revision level. You can check the version of your product in the footer on the screen. Image in which the version in the footer is 5.0.0 Example for Garoon version 5.0.1:
      5: Major Version
      0: Minor Version
      1: Revision
    • Installation identifier:
      You can check the installation identifier from the Garoon access URL.
      For the following URLs, the installation identifier is "cbgrn".
      http://192.0.2.0/cgi-bin/cbgrn/grn.cgi
    • database user password
  • If the server OS type or host name are changed during server migration, the migrated Garoon access URL will be changed.
    For details, refer to the article What are the necessary tasks to be performed when IP address/host name of Garoon server is changed? in the FAQ.
  • When you use a full-text search server, the full-text search server and the Garoon server must be the same OS. If you continue to use the full-text search server after you have migrated Garoon to a different OS, the full-text search server must also be built in the same OS as the Garoon after the migration of Garoon.

For Migrations to Windows Environment

The following example shows that migrating your Garoon on Linux to a Windows environment:

  • On Linux:
    • Installation identifier: cbgrn
    • CGI Directory: /var/www/cgi-bin
    • MySQL installation directory: /usr/local/cybozu
  • On Windows:
    • Installation identifier: cbgrn
    • CGI directory: C:\inetpub\scripts
    • MySQL installed directory: C:\Program Files\Cybozu
Steps:
  1. On Linux, disable notifications that the MySQL service sends to the full-text search server only when full-text search is used.

    If you are not using the full-text search server, proceed to step 2.

    1. Start the console and move to the following directory:
      cd /var/www/cgi-bin/cbgrn
    2. Execute the following command:
      Type the command in one line.
      ./grn.cgi -C -q code/command/fts/disable_udf_notifier.csp db_admin_password= (database administrator password)
      Confirm that the message "UDF Notifier is out of service" appears.
      If you receive an error message, see "Appendix B Error Messages" in the full-text search server guide.

  2. Back up all the Garoon data on Linux.

    For details, refer to the following page:

  3. Installs and initializes Garoon on the Windows environment.

    You must match the source and destination Garoon versions, installation identifiers, and database user passwords.
    The passwords for database administrative user and Administrator are optional. At the end of this procedure, the password will be the one you have set before the migration.

  4. Copy the backed up data in step 2 to the Windows environment and restore it.

    For details, see the following page:

  5. Install a full-text search server in the Windows environment only if you are using full-text search.

    If you are not using a full-text search server, proceed to step 6.
    The full-text search server can be installed on the same server as Garoon, or on a different server. If you want to install the full-text search server on a server other than the server Garoon resides, the operating systems must be Windows.
    For instructions on how to install the full-text search server, see "Installing" in the full-text search server guide.

  6. Ensure that you can access Garoon in the Windows environment.

For Migrations to Linux Environment

Migrate your Garoon on Linux to another Linux environment.

Steps:
  1. On the source server, back up the data in Garoon.

  2. Installs and initializes Garoon on the destination server.

    You must match the source and destination Garoon versions, installation identifiers, and database user passwords.
    The passwords for database administrative user and Administrator are optional. At the end of this procedure, the password will be the one you have set before the migration.

  3. Copy the backed up data in step 1 to the destination server environment and restore it.

  4. Ensure that you can access Garoon in the destination environment.