In-Place Migration

After the migration requirements have been met, proceed as follows to migrate CMS Fiona:

  1. Stop the old CMS server (CM, SES, TE) as well as the Trifork Application Server.

  2. Start the migration from the directory of the target instance by calling the CM with the -migrate option, passing it the source directory (e.g. CMS-Fiona-6.0.4/instance/intranet/) as an argument:

    $ CMS-Fiona-current/instance/intranet/bin/CM -migrate /opt/Infopark/CMS-Fiona-6.0.4/instance/intranet
    [2010-02-27 09:36:22] (32764) [cm master info] migrate: START
    Have you made a backup of the database, in case the migration fails? [Y/n] > y
    Does the database user have the permission to alter the database schema? [Y/n] > y
  3. Since the migration directly modifies the contents of the database, you need to confirm the existence of a backup. Furthermore, it is required that the CMS database user has the permission to modify the database schema. This includes, among other things, the permission to execute ALTER TABLE.

    After the questions have been confirmed with y, the migration is continued. From the old instance, the directories config, script, and data are copied. This might take some time, depending on the amount of data in the data directory. The license file is not copied since the new installation is assumed to have an individual license file.

  4. Then several migration steps follow in which the database schema, the data itself, and the system configuration are modified:

    [2010-02-27 09:36:26] (32764) [cm master info] migrate: Please wait. The migration may take a while...
    [2010-02-27 09:36:26] (32764) [cm master info] migrate: Copying config, script and data directories from old instance
    [2010-02-27 10:11:11] (32764) [cm master info] migrate: DB's destination schema version = 121
    [2010-02-27 10:11:11] (32764) [cm master info] migrate: DB's current schema version = 89
    [2010-02-27 10:11:11] (32764) [cm master info] migrate: Performing migration step 99: CopyOldBinConfAndConvertItToTcl
    [2010-02-27 10:11:11] (32764) [cm master info] migrate: Performing migration step 100: SupportMultipleInstances
    [2010-02-27 10:13:46] (32764) [cm master info] migrate: Performing migration step 101: AddContentService
    ...
    [2010-02-27 10:15:19] (32764) [cm master info] migrate: END
    [2010-02-27 10:15:19] (32764) [cm master info] CM master process terminating

    The output above indicates that the CM has successfully migrated the database.

  5. If you are exporting your content incrementally using the Template Engine, you can now migrate the TE data:

    $ CMS-Fiona-current/instance/intranet/bin/TE -migrate /opt/Infopark/CMS-Fiona-6.0.4/instance/intranet
    [2010-02-27 13:48:16] (20695) [te master info] migrate: START
    Have you made a backup of the database, in case the migration fails? [Y/n] > y
    Does the database user have the permission to alter the database schema? [Y/n] > y
    
    [2010-02-27 13:48:21] (20695) [te master info] migrate: Please wait. The migration may take a while...
    [2010-02-27 13:48:22] (20695) [te master info] migrate: DB's destination schema version = 121
    [2010-02-27 13:48:22] (20695) [te master info] migrate: DB's current schema version = 89
    [2010-02-27 13:48:22] (20695) [te master info] migrate: Performing migration step 100: SupportMultipleInstances
    ...
    [2010-02-27 13:49:04] (20695) [te master info] migrate: END
    [2010-02-27 13:49:04] (20695) [te master info] TE master process terminating
  6. Run the CM -migrate command the same way for all your CMS instances.

Migrating a Distributed Installation

For updating a Template Engine operated separately, a complete migration is required, including both the CM and the TE. The reason is that some components common to both TE and CM can only be migrated by performing a CM migration.

Please proceed as follows to migrate the Fiona installation on TE machine:

  1. If the CM has not been in operation on the TE system until now, and therefore has no database, please create the database. Afterwards run the CM once to generate the database tables:

    $ instance/intranet/bin/CM -single
    % exit
  2. Now, perform the migration as described here.

Migrating and Changing the Database Product

If the database product is changed, e.g. from Oracle to MySQL, the the dump/restore method must be used to transfer the content from the old to the new database. This can be done before or after the in-place migration described above. Please proceed as follows:

  1. Dump the contents of the instance to be migrated.
  2. Configure the target instance to use the target database system.
  3. Restore the content on the target system.