> 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/whitepapers/re-evaluating-high-availability-options-for-modern-cybersecurity-threats/media-stack-high-availability/active-passive-media-stacks/service-clustering-+-media-sync.md).

# Service Clustering + Media Sync

Continuity + Keeps past media, but spreads corruption and gaps remain

## Executive Summary

Clustering with media synchronization provides an active-passive approach, where only one recorder service is active at a time, while the standby service takes over in the event of failure. Because media databases are mirrored between nodes, previously recorded content remains accessible after failover—an improvement over basic recorder failover. However, failover still requires tens of seconds to minutes, producing blind spots in both live monitoring and recorded streams. Automatic mirroring also creates a cybersecurity weakness: if one node is encrypted or corrupted, the issue propagates to the standby. Like other passive designs, efficiency is limited to a one-to-one ratio, demanding a dedicated standby for each active recorder.

## Failover

Service clustering turns on the standby service node when the primary node fails. The solution **does not provide stream-level failover**, where only failed primary streams are started on the standby.

<figure><img src="https://73860689-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK95oxUATgzuZZ2VhRoDw%2Fuploads%2FR2lm0swQ1cADtc9F3OyJ%2FProduct%20and%20Marketing%20Graphics%20-%202025-09-16T142613.849.png?alt=media&amp;token=80d76238-ddf0-4ac1-a534-b7244df26d86" alt="" width="250"><figcaption><p>Service Clustering during failover</p></figcaption></figure>

## Consistency

The media database is synchronized between the two stacks, improving consistency.

<figure><img src="https://73860689-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK95oxUATgzuZZ2VhRoDw%2Fuploads%2FRCn949muUQlgoVd38Ujk%2FProduct%20and%20Marketing%20Graphics%20(85).png?alt=media&amp;token=8f1fdae2-85ed-44df-8912-b5ad4433624c" alt="" width="563"><figcaption><p>Media Sync. improves consistency</p></figcaption></figure>

* Provides access to content recorded before the failover.
* But the non-zero failover time inevitably creates gaps in media availability. During this window, live monitoring is interrupted, and recorded streams are incomplete, resulting in blind spots in both real-time situational awareness and post-event investigations. These forensic gaps undermine the reliability of video evidence and can weaken compliance and liability defense when edge recording and restoration are unavailable.

<figure><img src="https://73860689-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK95oxUATgzuZZ2VhRoDw%2Fuploads%2FykFGirDWO3tFo68xsikp%2FProduct%20and%20Marketing%20Graphics%20-%202025-09-16T150903.899.png?alt=media&amp;token=ebab79a0-c95d-40d1-aa7a-d3b1571d2fe4" alt="" width="256"><figcaption><p>Content Gap</p></figcaption></figure>

## Cybersecurity

Unfortunately, automatic media database mirroring means that the media content on both nodes gets encrypted if either node is compromised.

<figure><img src="https://73860689-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK95oxUATgzuZZ2VhRoDw%2Fuploads%2FvSuTNp4z5t6LKp27cno4%2FProduct%20and%20Marketing%20Graphics%20(73).png?alt=media&amp;token=0bae8c47-6095-4fc8-9509-3480ae097174" alt="" width="250"><figcaption></figcaption></figure>

## Efficiency

Efficiency is 1:1, meaning one standby node can support one primary node failure. Two standbys are required to support two simultaneous primary node failures, and so on.
