You can deploy the Security Center Directory on a standalone machine and configure Directory failover on another standalone machine.
You can isolate machine resources, even in failover mode, by using two machines with the Security Center Directory and its corresponding failover.
For more information on how to configure Security Center Directory failover, see Preparing Directory failover and load balancing.
Benefits: Directory and failover on separate standalone machines
- Resource availability
- Resources are not shared even in failover mode.
- 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.
- Minimal downtime for rolling updates
- Updates for your Windows system are available with minimal downtime for the Security Center Directory.
Drawbacks: Directory and failover on separate standalone machines
- Medium maintenance
- With this deployment architecture, there are three machines to monitor and maintain.
- Complex deployment
- You must install Security Center server on two machines, manually move the Security Center Directory to one machine and the Directory failover to the other machine.
- Higher latency in communications
- There would be some delay in communications between the Security Center Directory and other components Genetec Mission Control™.
- 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.
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.