Some roles in Security Center do not support failover, and others only support failover under certain conditions.
The following table lists which Security Center roles support failover, the failover approach they use, and any special requirements they might have.
| Role | Supports failover | Comments and exceptions |
|---|---|---|
| Access Manager | Yes | |
| Active Directory | Yes | |
| ALPR Manager | Yes | Extra resources must be shared between the servers assigned to the role. The Root folder of the role must follow the UNC convention and must be accessible to all servers. The paths to the hotlist and permit entities must also follow the UNC convention and be accessible to all servers. The WatermarkEncryptionParameters.xml file found in the installation folder of the primary server must be copied to all secondary servers. |
| Archiver | Yes | Up to two secondary servers can be assigned to an Archiver role. Each server
requires its own database, hosted locally or on a separate computer. NOTE: Failover
and redundant archiving are not supported on Archiver roles used for wearable (or
body-worn) cameras.
|
| Authentication Service | Yes | The Authentication Service role runs on the same server as the Directory role. If Directory failover is used, endpoint URIs for each Directory server on your system must be added to the identity provider configuration for Security Center. |
| Auxiliary Archiver | No | The function of the Auxiliary Archiver is to ensure that video archives remain available when the Archiver fails. |
| Camera Integrity Monitor | No (load distribution) | The Camera Integrity Monitor role can distribute its workload over multiple servers. This should not be confused with failover, where only one server always bears the full load of the role. |
| Cloud Playback | Yes | |
| Directory | Yes | Run on up to five servers simultaneously. Directory database failover is also supported. |
| Directory Manager | Not applicable | The function of the Directory Manager is to manage the Directory failover and load balancing. |
| Global Cardholder Synchronizer | Yes | |
| Health Monitor | Yes | |
| Intrusion Manager | Yes | Only when the intrusion panels are connected using IP. Failover is not supported if the intrusion panels are connected using serial ports. |
| KiwiVision™ Analyzer | Yes | |
| KiwiVision™ Manager | Yes | |
| Map Manager | Yes |
Best Practice: It is best to set the map cache to a location that can be
reached by all servers assigned to the role.
|
| Media Gateway | Yes | |
| Media Router | Yes | The primary and secondary servers can each have a separate database, hosted locally, or on another computer. |
| Mobile Credential Manager | Yes | |
| Mobile Server | Yes | |
| Plugin | Yes | Plugin (with an uppercase, in singular) is the role template that serves to create specific plugin roles. All roles created from this template support failover. |
| Privacy Protector™ | No (load distribution) | The Privacy Protector role can distribute its workload over multiple servers. This should not be confused with failover, where only one server always bears the full load of the role. If one of the assigned servers fails, and the remaining servers cannot handle their increased load, the resulting streams will have dropped frames. |
| Record Caching Service | Yes | |
| Record Fusion Service | Yes | |
| Report Manager | Yes | |
| Reverse Tunnel | Yes | |
| Reverse Tunnel Server | Yes | This is taken care by Genetec™ Cloud Operations. |
| Security Center Federation™ | Yes | |
| Unit Assistant | Yes | |
| Wearable Camera Manager | No | If the role fails, the body-worn camera stations (clients) cumulates the data until the role is up again. |
| Web-based SDK | Yes | |
| Web App Server | Yes | The Genetec™ Web App must reconnect to a different URL when the role fails over to a different server. |
| Web Client Server | Yes | The Security Center Web Client must reconnect to a different URL when the role fails over to a different server. |
| Zone Manager | Yes |