Skip to main content

Upgrade Moogsoft Onprem to v9.2.0

This topic describes how to upgrade Moogsoft Onprem to v9.2.0 from v9.0.0 or 9.0.0.x or 9.0.1.x, 9.1.0.x, or 9.1.1.x

Warning

Moogsoft Onprem v9.2.0 requires RabbitMQ v4 to be installed, which uses Quorum Queues (https://www.rabbitmq.com/docs/quorum-queues) and this feature requires at least three RabbitMQ nodes for full HA support

If the third/redundancy server does not exist in your deployment, it must be provisioned, and v9.2.0 installed on it, before the upgrade is started, with only RabbitMQ and OpenSearch running

Important

Enabling the "latency performance" RHEL profile is strongly recommended. This profile allows RabbitMQ to operate much more efficiently so that throughput is increased and smoothed out.

For more information on performance profiles, see https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/monitoring_and_managing_system_status_and_performance/getting-started-with-tuned_monitoring-and-managing-system-status-and-performance

Enable the profile by running the following command as root:

tuned-adm profile latency-performance

This setting will survive machine restarts and only needs to be set once.

Important

This process requires the presence of a third Moogsoft Onprem server to act a redundancy server as per : [→Fully Distributed HA Installation]

If this server is not already provisioned and running, it must be provisioned before starting this process, and a clean installation of Moogsoft Onprem v9.2.0 performed on it, with just the RabbitMQ and OpenSearch processes left running

In the process below, Server 1 and Server 2 are existing servers running MoogFarmD, Apache-Tomcat, RabbitMQ etc

In the process below, Server 3 is the Redundancy Server running just RabbitMQ and possibly OpenSearch too

Detailed step-by-step upgrade processes
High level v9.x.x.x to v9.2.0 upgrade process

The high level process is to upgrade the Redundancy Server first, send RabbitMQ messages to this server during the upgrade using a RabbitMQ Shovel, then upgrade the existing application Servers one by one.

  • Server 1 below is one of two existing application server running MoogFarmD, Apache-Tomcat, RabbitMQ, OpenSearch etc

  • Server 2 below is one of two existing application server running MoogFarmD, Apache-Tomcat, RabbitMQ, OpenSearch etc

  • Server 3 below is the Redundancy Server just running RabbitMQ and possibly OpenSearch too

  1. Upgrade Server 3

  2. Create a RabbitMQ Shovel to backup Events from Server 2 to Server 3 during the upgrade

  3. Upgrade Server 1

  4. Upgrade Server 2

  5. On Server 1

  6. On Server 2

‌

‌

In this section: