Incident Manager deployment option: on standalone machine with separate failover configuration - Genetec Mission Control™ 3.0.5.0

Genetec Mission Control™ Deployment Guide 3.0.5.0

Applies to
Genetec Mission Control™ 3.0.5.0
Last updated
2022-05-02
Content type
Guides > Deployment guides
Language
English
Product
Genetec Mission Control™
Version
3.0

You can deploy the Incident Manager on a standalone machine and configure failover for it on the machine with all other services.

The procedure to set up failover clusters for the Incident Manager role follows the same process as configuring role failover in Security Center. For more information, see Role failover and Setting up role failover.

Benefits: Incident Manager on a standalone machine with failover configuration on a separate machine

Low maintenance
Only two machines to monitor and manage; one for the Incident Manager role and one for all other Genetec Mission Control™ components.
Advantages of failover configuration
If the machine with the Incident Manager role goes offline, failover kicks in and you derive the same benefits of having the Incident Manager role running on the same machine as all other services.
Fault resilience for the Incident Manager role
If the machine running the Incident Manager goes offline, the system launches another instance of the Incident Manager on the machine with the other services after a slight delay thereby resuming operations.
NOTE: If however, any of the other services are down this option becomes useless as the Incident Manager requires all components to be up and running.
Incident Manager resources are not shared
Other services do not use the same resources and therefore do not impact the Incident Manager performance or availability unless failover is triggered.
Minimal downtime for rolling updates
Updates for your Windows system are available with minimal downtime for Incident Manager role.

Drawbacks: Incident Manager on a standalone machine with failover configuration on a separate machine

All drawbacks of deploying the Incident Manager role on a standalone machine
  • Complex deployment
  • Higher latency in communication between services
  • Greater impact from environment issues
  • Single point of failure
  • Downtime delay during Windows updates
No fault resilience or fault tolerance for other components
Having your machine with all the services fail or go offline means you lose incident data. The Incident Manager role also becomes unavailable when any of the components go offline.
NOTE: For the Incident Manager deployment, you cannot have the failover on a standalone machine because all the other services are required for the Incident Manager to run smoothly. However, if all the other components required for the Incident Manager to run support fault resilience or fault tolerance, you could try having a failover Incident Manager role on the same machine.