Upgrading a RabbitMQ failover cluster to version 3.8.3 - Genetec Mission Control™ 3.0.1.0

Genetec Mission Control™ Release Notes 3.0.1.0

series
Genetec Mission Control™ 3.0.1.0
revised_modified
2021-03-24

If RabbitMQ is deployed in a failover configuration with multiple nodes, you must use an adapted procedure to upgrade RabbitMQ to version 3.8.3. This version of RabbitMQ was introduced in Genetec Mission Control™ 2.13.3.0.

Before you begin

This procedure is specific to the deployment of RabbitMQ by the Genetec Mission Control™ installer. For external deployment of RabbitMQ with third party solutions, refer to the third party documentation as deployment process may differ.

To see how .erlang cookie paths are constructed, see the RabbitMQ Clustering Guide

Copy the Genetec Mission Control™ 3.0.1.0 installation package to both RabbitMQ servers.

Tip: It is recommended to use a 3 cluster node failover procedure. For details, see Configuring failover for RabbitMQ in the Genetec Mission Control™ Deployment Guide.

What you should know

RabbitMQ version 3.8.3 installs important security updates, an easier configuration file format and additional features.

This procedure refers to a 3 cluster failover node. Because these servers are interchangeable, the first node is always the first node to be brought down.

Before you upgrade your RabbitMQ, validate your existing RabbitMQ configuration.

Procedure

  1. On the first node, do the following:
    1. Stop the RabbitMQ service.
    2. Back up the .erlang.cookie file to a temporary storage location.
      File path for the .erlang.cookie is as follows:
      • C:\Windows\.erlang.cookie, if upgrading from RabbitMQ 3.7.10.
      • C:\Windows\System32\config\systemprofile, if upgrading from RabbitMQ 3.8.0.
      IMPORTANT: A new .erlang.cookie file is generated during the upgrade process and must be replaced with the backup.
    3. If using your own certificates in C:\Program Files (x86)\Genetec\RabbitMQ, you must create a back up for them as well.
  2. On the second and third node, do the following:
    1. Stop the RabbitMQ service.
    2. Back up the .erlang.cookie file to a temporary storage location.
      File path for the .erlang.cookie is as follows:
      • C:\Windows\.erlang.cookie, if upgrading from RabbitMQ 3.7.10.
      • C:\Windows\System32\config\systemprofile, if upgrading from RabbitMQ 3.8.0.
    3. If using your own certificates in C:\Program Files (x86)\Genetec\RabbitMQ, you must create a back up for them as well.
    4. Use the advanced setup in the Genetec Mission Control™ 3.0.1.0 installation wizard to only upgrade RabbitMQ.
    5. Restore your backup of the .erlang.cookie file to the following locations:
      • %HOMEDRIVE%%HOMEPATH%

        Usually C:\Users\<username>

      • %USERPROFILE%

        Usually C:\Windows\ServiceProfiles\LocalService\ for a service

    6. Restart the RabbitMQ service.
  3. On the first node, do the following:
    1. Restore your backup of the .erlang.cookie file to the following locations:
      • %HOMEDRIVE%%HOMEPATH%

        Usually C:\Users\<username>

      • %USERPROFILE%

        Usually C:\Windows\ServiceProfiles\LocalService\ for a service

    2. Use the advanced setup in the Genetec Mission Control™ 3.0.1.0 installation wizard to only upgrade RabbitMQ.
    3. Restart the RabbitMQ service.
    4. Validate the RabbitMQ upgrade.
  4. Enable queue mirroring.
    In the Admin tab, Policies section, ensure that the Genetec.MissionControl virtual host has the policy ha-all.

    If the Genetec.MissionControl virtual host policy is not set to ha-all:

    1. In the Name text box, enter ha-all.
    2. From the Apply to list, select Queues.
    3. From the Queues [Classic] tags list, click HA mode.
    4. Ensure the Definition > ha-mode is set to all.
    5. From the Queues [Classic] tags list, click HA sync mode.
    6. Ensure the Definition > ha-sync-mode is set to automatic.
    7. Click Add / Update policy.

Results

Your RabbitMQ failover cluster has been upgraded.