Incident Manager deployment option: standalone machine - 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 (United States)
Product
Genetec Mission Control™
Version
3.0

You can deploy the Incident Manager role on a standalone machine, separate from the other components of Genetec Mission Control™ installation.

Benefits: Incident Manager on a standalone machine

Incident Manager resources are not shared
Other services do not use the same resources and therefore do not impact the Incident Manager's performance or availability.
Low maintenance
Only two machines to monitor and manage; one for the Incident Manager role and one for all other Genetec Mission Control™ components.
Data loss tolerance for the Incident Manager role
If the machine running the Incident Manager goes offline, Genetec Mission Control™ becomes unavailable. However, if RabbitMQ and the Security Center Directory are still online and running on other machines, no data is lost and the Incident Manager role triggers any missed incidents on becoming available.
NOTE: If your downtime is significant, you would begin to notice a loss of data pertaining to incident triggers. Furthermore, the system takes time to assimilate the data accumulated during downtime, incurring a time delay.

Drawbacks: Incident Manager on a standalone machine

Complex deployment
You must install the Security Center server or expansion server on a separate machine and manually move the Incident Manager role to that server.
Higher latency in communication between components
There might be a slight delay in communications between the Incident Manager role and the other services.
Greater impact from environment issues
Network environment issues between the Incident Manager role and other services would directly impact service up-time.
Single point of failure
If the machine with the Security Center Directory and RabbitMQ goes offline, you would lose access to the whole system including all information on incidents, devices and entities.
Updating your Windows machine might incur downtime
Every time you update your system, there is downtime incurred while the system reboots.

Quality of service

Using this deployment architecture implies that service quality relies more on your system infrastructure. The quality of service would be directly dependent on the quality and reliability of your network infrastructures.