> For the complete documentation index, see [llms.txt](https://docs.vega365.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vega365.com/redundancy-management-framework/solution-blueprints/multi-site-failover-without-doubling-servers.md).

# Multi-Site Failover Without Doubling Servers

Vega Systems Inc, Sept 2025

## Executive Summary

Resilience at Scale — Failover Without Server Sprawl.&#x20;

The Vega Systems solution stack — XPort + RMF — enables a shared failover model, providing multi-site redundancy without the need for proportional server expansion.

## The Challenge: One-to-One Failover

<figure><img src="https://73860689-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK95oxUATgzuZZ2VhRoDw%2Fuploads%2FNu1hE2WU4DUMfgbel1VV%2FProduct%20and%20Marketing%20Graphics.jpg?alt=media&amp;token=52b91e91-2d16-48b6-93d3-f56cf1fffe73" alt=""><figcaption><p>Legacy Distributed Deployments</p></figcaption></figure>

Industries such as **transportation, utilities, education, and retail** often run many distributed XProtect sites. Most rely on **all-in-one servers**, where recording, management, and client services run on a single machine. These remote sites are typically connected to a central location through **XProtect Interconnect**, which aggregates feeds for monitoring.

This architecture made sense at the time of deployment, when bandwidth was limited. However, with improved connectivity, continuous video availability has become increasingly critical for operations and compliance.

The simplest way to add failover is to place a second server at every site. However, this approach effectively doubles the infrastructure, thereby raising costs and maintenance overhead. Customers require a more innovative approach to achieving resilience without replicating hardware at each location.

## The Vega Approach

The Vega Systems solution stack provides a path to **resilience without server sprawl**, while also strengthening the cybersecurity profile of deployments.

{% stepper %}
{% step %}

### Step 1: Amalgamate Sites with XPort

<figure><img src="https://73860689-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK95oxUATgzuZZ2VhRoDw%2Fuploads%2FURGFTKExpSpPJtCtR3fA%2FXPort_Migration_popout_render.png?alt=media&amp;token=8afaa60c-8e28-4912-a0d3-d1ba7e94f2c7" alt="" width="563"><figcaption><p>XPort: Automated Migration</p></figcaption></figure>

[**XPort** ](https://docs.vega365.com/xport/xport.md#overview)automates the **amalgamation of distributed sites into a single SQL database**, while retaining remote recorders. Customers can choose the consolidation ratio — e.g., four sites into one (4:1) — or even centralize all sites when high-bandwidth connectivity is available.

Without automation, this process is labor-intensive. With XPort, database merges, role privileges, views, access rights, and archived media are preserved, while **time and effort are reduced by up to 60%**.

Site consolidation requires no additional servers and creates the foundation for a shared failover model. \
\
*(See testimonial: a U.S. school district cut weeks of work and significant costs using XPort.* [*Link*](https://youtu.be/ASYPiIxP6sg)*.)*

{% endstep %}

{% step %}

### Step 2: Add Resilience

**Option 1: Native XProtect Failover**

After consolidation, resilience can be added with **native XProtect failover mechanisms**:

* **Management Server failover** protects SQL and services.
* **Recorder failover** protects recorder functions.

For example, starting with four all-in-one servers, a 4:1 consolidation, plus two extra failover servers, results in a six-server architecture with redundancy — achieving resilience without doubling the infrastructure. Streams received at the central site via Interconnect also fail over automatically.

**Option 2: RMF Cyber-Secure Redundancy**

<figure><img src="https://73860689-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK95oxUATgzuZZ2VhRoDw%2Fuploads%2FfhmPXGk7W6weIuZOwplq%2FUI.png?alt=media&amp;token=91673f95-da5f-486c-a483-1885f55348ac" alt=""><figcaption><p>RMF Embedded inside the XProtect Management Client</p></figcaption></figure>

Native failover works but has limitations:

* **Management failover** uses byte-for-byte replication, which is not cyber-secure.
* **Recorder failover** is a service-level, not stream-level, feature, which leaves video gaps and requires one failover recorder per primary recorder. Archived content is also unavailable during recorder failure.

**RMF addresses these gaps**:

* Works at both the **Management Server** (XProtect Expert/Corporate) and **Recording Server** (XProtect Professional+ and above).
* Provides [**near-instantaneous stream-level failover**](https://docs.vega365.com/redundancy-management-framework/user-manual/high-availablity-in-the-smart-client/high-availability-live-views.md#overview) at clients, avoiding video gaps.
* Enables **dual recording** for [**uninterrupted playback**](https://docs.vega365.com/redundancy-management-framework/user-manual/workflows-dashboard/overlay.md#about).
* Allows **M→N coverage** — fewer redundant recorders can protect many primaries simultaneously. (See: <https://youtu.be/jaGwtBUrb4E>)
* Introduces [**cybersecurity benefits**](https://docs.vega365.com/redundancy-management-framework/whitepapers/cybersecure-redundancy-with-vega-systems-solutions.md#introduction) by using API-level synchronization instead of raw SQL replication.
* Extends to **Interconnect environments** — RMF at the central site's Smart Client can provide stream-level failover for remote feeds *(pending implementation)*.

In the 4:1 consolidation example, two additional servers can be added:

* One configured as **Management + SQL + core services**.
* One as an **active-active redundant recorder** streaming directly from all cameras.

This design reduces infrastructure, increases resilience, and strengthens the overall cybersecurity posture.
{% endstep %}
{% endstepper %}

## Conclusion

The Vega Systems solution stack — **XPort + RMF** — provides a clear path to resilient, cyber-secure multi-site XProtect deployments. By consolidating sites with XPort and adding redundancy with RMF, organizations can achieve **continuous video availability** without doubling server counts.

Compared to native failover alone, RMF delivers **stream-level protection, dual recording for uninterrupted playback, and M→N coverage** that scales more efficiently. At the same time, API-driven synchronization enhances the **cybersecurity posture** of the deployment.

In short, customers gain the availability and compliance assurance they need, while reducing infrastructure cost and complexity.
