> 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/milestone-recorder-failover.md).

# Milestone Recorder Failover

Ensures basic continuity

## Executive Summary

Milestone Recorder Failover, available in XProtect Expert and Corporate editions, provides an active-passive mechanism where a standby recorder takes over in the event of primary failure. Once the primary comes back up, content recorded in the failover is transferred back to the primary to restore consistency.&#x20;

While this ensures basic service continuity, failover activation can take tens of seconds to minutes, creating unavoidable gaps in both live monitoring and recorded content. The standby node does not hold prior media, leaving pre-failover footage inaccessible in the failed-over state. Automatic backups cannot protect against ransomware since encrypted data is replicated. Efficiency is limited to a one-to-one model, requiring a dedicated standby for each protected recorder. As a result, Milestone Recorder Failover offers coverage for hardware outages but leaves gaps in consistency and cyber resilience.

<figure><img src="https://73860689-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK95oxUATgzuZZ2VhRoDw%2Fuploads%2FVls0ZxV4lvILwq8igetI%2FProduct%20and%20Marketing%20Graphics%20(91).png?alt=media&amp;token=2ef803a7-5961-4f42-b199-dcdca60b7960" alt="" width="226"><figcaption><p>Milestone XProtect Recording Server Failover</p></figcaption></figure>

## Failover

If the active fails, the passive stack activates. Activation time varies from tens of seconds to minutes. 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%2FR38vzT9XxeunKJU2FPhw%2FProduct%20and%20Marketing%20Graphics%20(92).png?alt=media&amp;token=197c8e03-741d-4fef-ac30-01aeaeaad12d" alt="" width="250"><figcaption><p>Failover State</p></figcaption></figure>

## Consistency

Although the solution allows for stack-level failover with media backfill to the primary after failback, it lacks consistency in two key areas.

<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>Non-Zero Failover Time Creates Content Gaps</p></figcaption></figure>

1. 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.
2. The standby node lacks media database content from the primary stack. Therefore, when the standby is active, content recorded before the standby was activated is not accessible.

<figure><img src="https://73860689-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK95oxUATgzuZZ2VhRoDw%2Fuploads%2FgXc4tasMFU4xuAddvfah%2FProduct%20and%20Marketing%20Graphics%20(84).png?alt=media&amp;token=ff43ca16-fc8b-4575-8a84-677815e35187" alt="" width="563"><figcaption><p>Primary stack's media database is unavailable during failover</p></figcaption></figure>

## Cybersecurity

If an attack encrypts the primary server's media database, causing the recorder to stop functioning, the standby server takes over. However, the standby device never gains access to content recorded before it was turned on. Therefore, content recorded before the standby's activation is lost, possibly forever. Additionally, if an automatic media backup solution is used for the primary, it becomes ineffective because the backup is also encrypted.

<figure><img src="https://73860689-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK95oxUATgzuZZ2VhRoDw%2Fuploads%2FGCVMoEH4Hhu6Y0jByHuu%2FProduct%20and%20Marketing%20Graphics%20(70).png?alt=media&amp;token=f564d3db-2d27-4b66-bbed-7e890e9296fb" alt="" width="250"><figcaption><p>Cyberattack encrypting the primary's media</p></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.
