Upgrade tips based on Genetec Mission Control™ deployment architecture - 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

Upgrade your Genetec Mission Control™ environment based on your deployment architecture.

Before you begin

Get the latest build of Genetec Mission Control™. For information on how to get the package, see Installing Genetec Mission Control™ 3.0.

Procedure

Upgrade tips for deployment model 1: Genetec Mission Control™ on expansion server

If your deployment architecture follows deployment model 1 described in the Genetec Mission Control™ Deployment Guide, follow the instructions below to upgrade your system.

  1. Upgrade the Directory server.
    The Genetec Mission Control™ Incident monitoring task remains online during the Directory server upgrade.
  2. Upgrade the Genetec Mission Control™ server.
    The Genetec Mission Control™ Incident monitoring task goes offline during Genetec Mission Control™ server upgrade.

    This process upgrades Genetec Mission Control™, RabbitMQ and the Incident Manager database.

  3. Restart the Genetec™ Server service on the Directory server.
    Security Desk remains offline until Genetec™ Server is back online.
  4. Restart the Genetec™ Server service on the Genetec Mission Control™ server.
    The Incident monitoring task remains offline until Genetec™ Server is online.
  5. Upgrade all Genetec Mission Control™ workstations.
    You have successfully upgraded your Genetec Mission Control™ environments.
    NOTE: Estimated downtime during this upgrade procedure is 5-10 minutes depending on the scale of your setup (number of active incidents, Security Center entities and so on).

Upgrade tips for deployment model 2: SQL on separate server

If your deployment architecture follows deployment model 2 described in the Genetec Mission Control™ Deployment Guide, follow the instructions below to upgrade your system.

  1. Upgrade the Directory server.
    The Genetec Mission Control™ Incident monitoring task remains online during the Directory server upgrade.
  2. Upgrade the Genetec Mission Control™ server.
    The Genetec Mission Control™ Incident monitoring task goes offline during Genetec Mission Control™ server upgrade.

    This process upgrades Genetec Mission Control™, RabbitMQ and the Incident Manager database. on the SQL server.

  3. Restart the Genetec™ Server service on the Directory server.
    Security Desk remains offline until Genetec™ Server is back online.
  4. Restart the Genetec™ Server service on the Genetec Mission Control™ server.
    The Incident monitoring task remains offline until Genetec™ Server is online.
  5. Upgrade all Genetec Mission Control™ workstations.
    You have successfully upgraded your Genetec Mission Control™ environments.
    NOTE: Estimated downtime during this upgrade procedure is 5-10 minutes depending on the scale of your setup (number of active incidents, Security Center entities and so on).

Upgrade tips for deployment model 3: RabbitMQ on dedicated server

If your deployment architecture follows deployment model 3 described in the Genetec Mission Control™ Deployment Guide, follow the instructions below to upgrade your system.

  1. Upgrade the Genetec Mission Control™ failover server.
    NOTE: The Genetec Mission Control™ Incident monitoring task remains online during the Genetec Mission Control™ server upgrade.
  2. Upgrade the Directory server.
    The Genetec Mission Control™ Incident monitoring task remains online during the Directory server upgrade.
  3. Upgrade the Genetec Mission Control™ main server.
  4. Restart the Genetec™ Server service on the Genetec Mission Control™ main server, Genetec Mission Control™ failover server and Directory server.
    Security Desk and the Genetec Mission Control™ Incident monitoring task remains offline until Genetec™ Server is back online on all servers.
  5. Validate the existing RabbitMQ configuration setup.
  6. Upgrade the RabbitMQ nodes:
    Security Desk and the Genetec Mission Control™ Incident monitoring task remain online during the RabbitMQ upgrade. The RabbitMQ cluster configuration is not disturbed during this upgrade.
    1. Deactivate the Incident Manager role:
      1. Select System > Roles > Incident Manager.
      2. Right click the Incident Manager role to select Maintenance > Deactivate role.

      The Genetec Mission Control™ Incident monitoring task remains offline when the Incident Manager role is deactivated and is only available when the Incident Manager role goes active.

    2. Upgrade RabbitMQ on node 1.
    3. After the RabbitMQ setup is finished on node 1, copy the following certificate files from the paste them in the same locations in the Genetec Mission Control™ main and failover servers:
      • CACert.pem
      • Cert.pem
      • Key.pem

      By default, these files are found in C:\Program Files (x86)\Genetec\RabbitMQ\.

    4. Restart the RabbitMQ service:
      1. On the RabbitMQ node 1, open Microsoft Management Console Services (services.msc).
      2. Select the RabbitMQ from the list of services and click Restart.
    5. Upgrade RabbitMQ on nodes 2 and 3.
    6. After the RabbitMQ setup is finished on RabbitMQ nodes 2 and 3, copy the following certificate files from RabbitMQ node 1 and paste them in the same locations in RabbitMQ nodes 2 and 3:
      • CACert.pem
      • Cert.pem
      • Key.pem

      By default, these files are found in C:\Program Files (x86)\Genetec\RabbitMQ\.

    7. Activate the Incident Manager role:
      • Select System > Roles > Incident Manager.
      • Right click the Incident Manager role to select Maintenance > Activate role.
    8. Upgrade all Genetec Mission Control™ workstations.
    9. Validate the RabbitMQ upgrades.
    You have successfully upgraded your Genetec Mission Control™ environments.
    NOTE: Estimated downtime during this upgrade procedure is 30 minutes or more depending on the your setup (number of active incidents, Security Center entities and so on).