You can deploy the Security Center Directory on the same machine as all the Genetec Mission Control™ components and have a failover configuration on a separate standalone machine.
What you should know
This deployment architecture is identical to the Basic deployment option for Mission Control with an additional failover configuration for the Security Center Directory on a separate standalone machine.
For more information on how to configure Security Center Directory failover, see Preparing Directory failover and load balancing.
This deployment architecture gives you the option of running your services in standard or failover mode.
Benefits: Directory on the same machine as other Mission Control services
- Low maintenance
- Only two machines to monitor and manage; one for the Security Center Directory and all other Mission Control components and one for the failover server.
- Low latency
- Services communicate directly with each other instead of going on the network.
- Low impact from environment problems
- Network latency and failures never affect your deployment unless they prevent Security Desk and Config Tool from accessing your machine. This does not affect services which will still operate normally.
- Fault resilience for the Security Center Directory
- If the machine running the Directory goes offline, the system launches another instance of the Directory on another machine, with a short delay. This ensures continued operations with minimal disruptions.
- Security Center Directory resources are not shared
- If the Directory is running on a standalone machine, other services do not use the same resources and therefore do not impact the Security Center Directory performance or availability unless failover is triggered.
Drawbacks: Directory on the same machine as other Mission Control services
- Complex deployment
- You must install the Security Center server on a separate machine and manually add the Security Center Directory failover to that server.
- No fault resilience or fault tolerance
- Having your machine with all the services fail or go offline means you lose Mission Control incident data. Directory remains available, unless both machines go offline.
- Resource starvation in failover mode
- In failover mode, Directory and Incident Manager would be competing for the same resources.