Migrating from Version 5.6.1 to 6

Important
  • Migrating data overwrites core configuration settings in PureMessage 6 with settings from PureMessage 5.6.1. It is therefore not recommended that you modify the PureMessage 6 installation until the migration is complete.
  • When upgrading servers in a multi-server deployment, you must migrate servers in the correct order, and then run the migration script on each server, immediately after each one is upgraded. See "Migrating a Multi-Server Deployment" below.

If have finished installing PureMessage 6 alongside an existing 5.6.1 installation, you have the option of migrating policy settings and other data from your 5.6.1 installation to the new installation directory. Immediately following installation of Version 6, you are prompted to run the migration script.

Note
You can only migrate data from the most recent version of PureMessage (5.6.1). If you are running an older version of PureMessage, upgrade to Version 5.6.1 before migrating.

The migration is done by way of a command-line tool (pmx-v6-migrate), which leads you through the steps in the required order.

Sophos Professional Services modules and settings are not imported as part of the migration. Contact Professional Services if you require any assistance. Although core configuration files are migrated, there are some configuration files that are not imported to version 6. For detailed results of the migration, see /opt/pmx6/var/log/migrate_pmxv5.log.

If you prefer to migrate data manually, or you choose not to migrate any data, do not perform these steps.

To migrate your data on a single-server configuration.

  1. As the PureMessage user (by default, 'pmx6'), run the PureMessage migration script located in /opt/pmx6/bin:
    pmx-v6-migrate

    You are presented with three migration options, which must be run in order shown.

    Note
    The optional Step 3 (Database & Quarantine) may take a very long time, depending on the size of the quarantine and your data.
  2. At the Enter selection prompt, type 1, and press Enter . When prompted to overwrite your current PureMessage 6 configuration settings, type y.
    The results are displayed at the command line as the configuration files are migrated.
  3. Press Enter to return to the migration menu.
  4. At the Enter selection prompt, type 2, and press Enter . When prompted to overwrite your current PureMessage 6 log search files and data, type y.
  5. Press Enter to return to the migration menu.
  6. [Optional] At the Enter selection prompt, type 3, and press Enter . Carefully read the message displayed at the command prompt. If you are ready to proceed, type y.
    The results of the migration are displayed.
  7. At the Enter selection prompt, type 4, and press Enter to exit the migration script.
Note
Migrating a Multi-Server Deployment
  • Migrate data for each server separately.
  • Upgrade each server individually, running the migration script on each server before proceeding to the next server.
  • Select the same migration options for each server. For example, if you choose to perform the Database & Quarantine step for the server that is running the Database Server role, you must also perform this migration step for all servers in the deployment.
  • Before migrating data, start the server that is running the Database Server and Centralized Server Manager (CSM) roles.
  • When migrating on multihomed servers, the IP address selected during the version 6 upgrade must match the IP address that is specified in etc/location for version 5.6.1.

For more information, see "Multi-Server Upgrade (Version 6)."