Skip to main content

Upgrade to Moogsoft Onprem v9.x

An upgrade from v8.x to v9.x is required to maintain support for your Moogsoft deployment. Because it involves an operating system change, you cannot perform the upgrade in place. Instead, the upgrade process involves deploying Moogsoft Onprem v9.x onto new RHEL8 servers, migrating the existing configuration and database from v8.x to v9.x, and then updating the database schema. Some downtime will be required, though no incoming events should be lost.


The v8.x to v9.x migration must be carried out by an experienced RHEL system administrator with root privileges. If you do not have the necessary experience or are unfamiliar with your Moogsoft components and deployment-specific customizations, contact your account manager to seek help from Moogsoft Professional Services.

For a v6.x or v7.x system, you will need to first upgrade to v8.x before performing the migration to v9.x. Consult Upgrade Moogsoft Enterprise for instructions on upgrading to v8.2.

The number and type of servers for your v8.x and v9.x deployments must match. Consult Server Roles for a review of Moogsoft server role terminology.

The following steps should be completed in advance of the migration. After the configuration is migrated to v9.x, no further changes should be made to the v8.x configuration.

  1. Archive old data

  2. Do a database health check

  3. Provision the new RHEL8 servers

  4. Install Moogsoft Onprem v9.x on the new servers

  5. Copy configuration information from your v8.x to v9.x deployments

The following steps should take place during a scheduled maintenance window. During the maintenance window, there will be a period of downtime when incoming events will be held in buffers on both systems. After services are restarted and data is being ingested on the v9.x system, the v8.x system can be fully turned off.

  1. Set up a RabbitMQ shovel

  2. Prepare the database (for v8.0 and v8.1 only)

  3. Copy the v8.x database to the v9.x system

  4. Upgrade the database schema

  5. Allow the v9.x database replicas to synchronize

  6. Restart services and transfer data ingestion

Guides with specific instructions for completing these steps are in the next two sections. File locations will vary depending on whether you are migrating an RPM or tarball deployment. Follow the appropriate guide to perform the migration.

Migrate an RPM deployment from v8.x to v9.x

Migrate a tarball deployment from v8.x to v9.x