Federated
Active-Active Redundancy through Federation
Last updated
Redundancy Management Framework
Active-Active Redundancy through Federation
Last updated
Primary recorders are located at a parent milestone site, while secondary recorders are situated at a child site. There are two distinct databases: one at the parent site and another at the child site. Each camera streams to both sites simultaneously.
This setup ensures redundancy for all XProtect components, including the Management Server, Event Server, SQL Server, and Recording Servers.
Cybersecure Design: Separate data centers with no inter-site clustered components enable independent cybersecurity policies at each. A compromise in one does not automatically compromise the other.
Clean Software Update Workflows: Since there are no inter-site clustered components, one site can be taken offline completely while the other site continues to serve clients. If things go wrong during an upgrade, the blast radius is contained within a single site.
SQL Insulation: There is no cross-site SQL clustering; therefore, SQL corruption in one site does not automatically affect the other site. All SQL synchronization is achieved through the Milestone API, which fails when reading from a corrupt database.
Increased levels of redundancy require higher infrastructure costs for multi-server deployments.
