Multi-Server Upgrade (Version 5.6.1 to 6.0)

About this task

Important:

You must perform this upgrade as the root user.

If you are running PureMessage on multiple servers:

  • You must upgrade the assigned PureMessage server roles in the correct order (shown below).
  • You must ensure that you have enough hard disk space available if you are planning to migrate 5.6.1 data (quarantine, logs, reports, etc) after the upgrade. It is recommended that you run the following command as the root user on each PureMessage server to determine the amount of disk space required for installation on that server.

    du -sh /opt/pmx/
  • You must follow the single-server upgrade procedure for each server.
  • You must select the same migration options for each server, if you are using the migration script to import PureMessage 5.6.1 data. 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. For more information, see "Migrating from Version 5.6.1 to 6."
  • You must not change the hostname or IP address of any of the servers during the upgrade/migration. This can be done prior to or following the upgrade/migration. Making these changes during an upgrade/migration will result in failures and may leave your system in an unrecoverable state.
  • If you have more than one server that is running the Mail Filter role, it is only necessary to stop one mail filter at a time. The other(s) can continue processing messages. Your organization can send and receive mail throughout the upgrade, although access to certain resources (for example, the End User Web Interface and Groups Web Interface) will not be accessible until the entire upgrade process is complete.
  • If any of the upgrade steps fail, and you are unsure of how to proceed, contact Sophos Technical Support.

You must upgrade any assigned PureMessage server roles in the correct order:

  1. Database Server role and Centralized Server Manager (CSM) role
  2. Mail Transfer Agent role and Mail Filter role
  3. End User Web Interface Server role

To upgrade a multi-server deployment:

  1. Upgrade the server that is running the Database Server and Centralized Server Manager (CSM) roles.

    Note:

    Once you begin upgrading the Database server role:

    • Mail Filter servers will no longer be able to insert into or read data from the database, and you may see errors in the logs. This is expected and does not affect mail flow.
    • Groups Web Interface servers will no longer allow administrators to log in. Thus, administrators should be advised in advance that there will be a service interruption because of the upgrade.
    • End User Web Interface servers will no longer allow users to log in. Thus, users should be advised in advance that there will be a service interruption because of the upgrade.

    If required, run the migration script on the server running the Database Server and Centralized Server Manager (CSM) roles to import 5.6.1 data immediately following the succesful upgrade. For more information, see "Migrating from Version 5.6.1 to 6."

    The database server is now upgraded and migrated. However, the other servers in the deployment will not be able to communicate with the database until they have been upgraded (and, optionally, migrated) to version 6.

  2. Start PureMessage on the server that is running the CSM role.
  3. One at a time (if there is more than one), upgrade servers that are running the Mail Transfer Agent and Mail Filter roles. If required, run the migration script on each of these servers to import 5.6.1 data immediately following each upgrade.

    Note: After the upgrade and optional migrations steps are complete on each server, the individual servers will resume communication with the database and begin to process mail again. It is highly recommended that, on the first Mail Transfer Agent and Mail Filter server that is upgraded, you test for correct behavior before proceeding with the upgrade of other servers.

  4. One at a time (if there is more than one), upgrade the End User Web Interface servers. If required, run the migration script on each server to import 5.6.1 data immediately following each upgrade.

On each server, after you perform the steps described in the single-server upgrade procedure, you will be prompted to begin the installation on that particular server. For more about multi-server deployment, see the Custom Installation section.