Roles supporting failover - Security Center 5.9

Security Center Administrator Guide 5.9

Applies to
Security Center 5.9
Last updated
2022-09-12
Content type
Guides > Administrator guides
Language
English (United States)
Product
Security Center
Version
5.9

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  
Archiver Yes Can have up to two secondary servers 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 wearabe (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 bears the full load of the role at all times.
Directory Yes Can run simultaneously on up to five servers. Also supports Directory database failover.
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  
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.
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 Server Yes  
Omnicast™ Federation™ 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 bears the full load of the role at all times. If one of the assigned servers fails, and the remaining servers cannot handle their increased load, the resulting streams will have dropped frames.
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 Server Yes The Web Client must reconnect to a different URL when the role fails over to a different server.
Zone Manager Yes