Explore supported RMF architectures below. Each design is optimized for different redundancy needs, from single-site failover to active-active multi-site deployments. Click on any architecture to view deployment diagrams, setup steps, and configuration best practices.

1. Recommended for better cybersecurity -Federated

2. Recommended for better cybersecurity -Independent

3. Single Site

Attack

Replication needs a super-admin password and an open DB port.

With SQL Replication

The attacker steals the sysadmin-level replication account via an open port 5022 and pivots into other databases.

With RMF's Object Synchronization

The sync connector only makes an outbound secure call with a short-lived, narrow-scope token through the XProtect API/SDK (provided certificates are enabled on XProtect). Even if stolen, the damage is limited, and no DB port is open.

Attack

In this attack mode, a booby-trapped procedure slips into the primary database.

With SQL Replication

The hidden backdoor spreads everywhere.

With RMF's Object Synchronization

Application APIs expose no DDL, so the procedure can’t propagate.

Attack

In this attack mode, malware adds a rogue admin to the database.

With SQL Replication

All copies end up with the rogue admin. Every failover site is compromised.

With RMF's Object Synchronization

Per-object replication control enables administrators to establish a policy that mandates manual confirmation for replicating the Users/Roles category and quarantining rogue accounts.

The Vega Redundancy Management Framework (RMF) is software designed to enhance Milestone XProtect Video Management Software (VMS) by providing recording server redundancy in all architectures, as well as cybersecure management server and SQL redundancy in specific architectures, all within a single software package. Key components facilitate cybersecure data synchronization between data centers, ensure rapid video failover at each client, and enable high-availability alarms. RMF ensures that cybersecurity is central to the design of a redundant system.

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.

Pros

1. 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.

1. 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.

2. 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.

Cons

1. Increased levels of redundancy require higher infrastructure costs for multi-server deployments.

While the two data centers are independent, services and SQL can still be clustered within a single data center. RMF installation varies accordingly. Use the links below to navigate to the relevant RMF installation section.

• Non-Clustered Mode

• Clustered Mode

While the two data centers are federated, services and SQL can still be clustered within a single data center. RMF installation varies accordingly. Use the links below to navigate to the relevant section.

• Non-Clustered Mode

• Clustered Mode

Primary and Secondary recorders are part of a single Milestone deployment that utilizes one database. It is important to note that clustered SQL databases, clustered Management Servers, and the Milestone Management Server Failover are all classified as a 'Single Site' because they operate on a single unique database.

This setup ensures redundancy for the Recording Servers only. To achieve redundancy and failover for other Milestone components, solutions such as Milestone Management Server Failover, Windows Clustering with AlwaysOn SQL, or Evidian Clustering must be deployed in conjunction with RMF.

Pros

1. Lower cost: Usually, fewer servers result in lower infrastructure costs.

Cons

1. Weak Cybersecurity Design: Even with Always-On SQL clustering, there is only one effective database. A hack into one copy is a hack into all copies and will compromise all video security.

2. Potential Outages during Upgrades: Even if clustering is used for failover, during software upgrades, all nodes must be taken offline and upgraded. The system experiences a loss of functionality during the process, which worsens if there are issues during upgrades, potentially causing all video security to fail.

Attack

In this attack mode, ransomware encrypts the raw data pages of the database.

With SQL Replication

Encrypted pages stream to every replica; all copies are locked.

With RMF's Object Synchronization

Raw pages never move. API calls to the primary database fail. Standby stays clean and can be promoted.

Download and Unzip the RMF Installer File

Perform the following pre-installation steps to download and unzip the RMF Installer files:

1. Navigate to the download link provided and download the RMF zipped file.

2. Locate the RMF zipped file from the Downloads folder.

1. Right-click the zipped file and click Extract All.

1. Click Browse to select a destination where the zipped file contents will be extracted, then click Extract. Then, select the check box to show the extracted files when they are complete.

1. Unblock the installer after downloading it to ensure that the host system will run the installer. Often, because the installer was downloaded online, the host system automatically blocks it for security reasons.

Validate the RMF Installer File

Perform the following steps to ensure that the RMF installer is valid and not corrupted during download:

1. Right-click ValidateInstaller.bat file.

2. Click Run as Administrator.

Prerequisites

Before installing RMF components, ensure that each machine has the following software pre-installed:

• .NET Framework 4.8

Additionally, machines that will host the RMF service components must have:

• Internet Information Services (IIS) 7.0 or higher version

• Milestone Management Client Software

Section Navigation

• If your Primary and Secondary recorders are part of a single Milestone deployment with a single database, go to the section.

• If your Primary recorders are part of a Parent Milestone site, and the Secondary recorders are part of a Child site, go to the section.

• If your Primary recorders are part of one Milestone deployment, and the Secondary recorders are part of a separate, independent Milestone deployment, go to the section.

• Cybersecurity-first: The API Object Transfer mechanism used by RMF provides a Malware-Filtered Alternative to byte-for-byte legacy SQL synchronization.

• Active-Active Redundancy: Cameras stream to both primary and secondary recorders, eliminating recording gaps caused by recorder failures.

Attack

Malicious user corrupts SQL tables.

With SQL Replication

Summary

SQL replication ensures availability but offers no protection against malware or corrupted data. Vega Systems' Object Intelligence framework adds a cybersecure layer to redundancy. By synchronizing only trusted objects through APIs, RMF, when deployed in , or architectures prevents harmful or unknown changes from propagating, keeping secondary systems clean and resilient.

The Vega RMF solution consists of three primary components: Services, Configuration UI, and Client. Each of these components plays a crucial role in ensuring high availability, synchronization, and seamless management within the RMF ecosystem.

1. ⚙️Services: The RMF solution comprises two key services designed to provide synchronization and high-availability features.

   1. RMF Smart Sync Service - This service ensures seamless synchronization of control data across data centers. It manages essential elements, including devices, streams, roles, views, and groups, thereby maintaining consistency and operational efficiency.

For deployments with less than 500 cameras

For a Federated architecture and clustered mode with less than 500 cameras, deploy the following components.

This section describes the Silent installation procedures of RMF Services and Client.

Attack

The standby server’s drive fills up (possibly because logs weren’t cleaned or an attacker dumped junk files), and it stops accepting the change data streamed from the primary.

Refer to the following sections for RMF Pre-installation, Installation, Post-Installation, and Uninstallation procedures.

Perform the following steps to install the RMF Smart Client component on the Smart Client machine:

1. Complete all the steps as described in the section.

2. Select the Smart Client option in the Package Type dialog box and click Install.

Perform this procedure to install the following components: RMF Smart Sync Service, RMF Configurator UI, and RMF Alarm Service. Note that the Client component is also installed by default.

1. Complete all the steps as explained in the section.

2. Right-click the RMF_Installer.exe file and select Run as Administrator.

3. Ensure that the RMF Setup path is pointed to the path where the Milestone is installed.

Primary recorders are part of one Milestone deployment, while the Secondary recorders belong to a separate, independent Milestone deployment. This architecture features two unique databases, one at each site. The sites are not Federated. 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.

Pros

This section describes the manual installation procedures for RMF Services and the RMF client.

With SQL Replication

A system that performs full-image replication sends every row and column in the database to the secondary site, regardless of whether that site is cleared to hold the information. If the primary contains PII, payroll data, export-controlled CAD files, or patient records, the replica now does, too—even if it sits in a lower-trust network, another country, or a public cloud.

Introduction

Unlike traditional high-availability architectures that replicate everything—including mistakes and malware—RMF provides cybersecurity by design. It combines selective object-level synchronization, which prevents malicious or unintended changes from spreading, with fully isolated data centers that eliminate shared attack surfaces and block lateral threats. Together, these two layers provide a resilient and secure foundation for mission-critical video infrastructure.

We explore these two pillars of RMF's architecture in the pages that follow.

For deployments with less than 500 cameras

For a Federated architecture and non-clustered mode with less than 500 cameras, deploy the following components:

RMF Service Components

The following Service components are installed on the Management Server M1:

• RMF SmartSync Service

• RMF Alarm Service

• RMF Configurator

• Milestone Management Client

For more information on the RMF Services Installation, go to the following sections:

For additional information on the Milestone XProtect Management Client, refer to the Milestone XProtect documentation.

RMF Smart Client Component

The RMF Smart Client Component is installed on the Smart Client Machine (SC1).

For more information on the RMF Smart Client installation, refer to the following sections:

For deployments with more than 500 cameras

For a Federated architecture and non-clustered mode with more than 500 cameras, the RMF services components must be deployed on a dedicated RMF server (DRMF). This server must have the exact machine specifications as the Milestone Management Server and can be clustered to ensure high availability.

RMF Service Components

The following Service components are installed on the Dedicated RMF Server (DRMF):

• RMF SmartSync Service

• RMF Alarm Service

• RMF Configurator

• Milestone Management Client

For more information on the RMF Services installation, refer to the following sections:

For additional information on the Milestone XProtect Management Client, refer to the Milestone XProtect documentation.

RMF Smart Client Component

The RMF Smart Client Component is installed on the Smart Client Machine (SC1).

For more information on the RMF Smart Client installation, refer to the following sections:

Summary

A large percentage of deployed high-availability architectures rely on cross-site service clustering, which increases cyber risk by creating shared attack surfaces. RMF, when deployed in Federated or Independent architectures, takes a different approach: each data center operates independently, with no shared clustering or storage. This isolation blocks lateral movement during an attack and ensures a clean, uncompromised environment is always available for recovery.

Clustering Requires Broad and Persistent Trust

Traditional cross-site clustering relies on deep system-level integration between data centers, typically involving shared authentication domains, real-time database replication, and mutual access to control services and storage. For the cluster to function seamlessly, each site must implicitly trust the other across all layers of the stack. This broad trust model means that any compromise—whether through malware, misconfiguration, or insider threat—can rapidly propagate across the entire cluster. The exact mechanisms that deliver high availability also erase meaningful security boundaries between sites, violating zero-trust principles and increasing the blast radius of a breach.

RMF Service Architecture Enforces Narrow, Explicit Trust

The RMF solution (when deployed in or architectures) replaces clustering with a service-based model that treats each data center as an independent entity. There is no requirement for shared authentication, storage, or real-time database replication. Instead, RMF operates through a lightweight service that connects the two sites over a narrow, explicitly defined communication channel with limited privileges and no direct system-level access. This design dramatically reduces the trust surface and prevents lateral movement between sites. Even if one site is compromised, the other remains fully insulated. By eliminating the need for persistent cross-site trust, RMF aligns with zero-trust architecture and provides a far stronger foundation for cybersecurity and resilience.

Feature Video

For deployments with fewer than 500 cameras

For a single-site architecture and clustered mode with fewer than 500 cameras, deploy the following components:

RMF Service Components

The following Service components are installed on the Management Servers M1 and M2:

• RMF SmartSync Service

• RMF Alarm Service

• RMF Configurator

• Milestone Management Client

For more information on the RMF Services installation, refer to the following sections:

Add RMF Service Components to cluster management

Additionally, add the Smart Sync Service and the Alarm Service to the Cluster Manager. Including these services in the cluster ensures that the standby node activates them when it becomes active, and RMF services have HA. The information below illustrates the process for the RMF alarm service when using Windows Clustering. Repeat the steps for RMF Smart Sync Service. If using Milestone Management Server Failover, the steps may vary slightly, but the outcome should be the same.

For additional information on the Milestone XProtect Management Client, refer to the Milestone XProtect documentation.

RMF Smart Client Component

The RMF Smart Client Component is installed on the Smart Client Machine (SC1).

For more information on the RMF Smart Client installation, refer to the following sections:

For deployments with more than 500 cameras

For a single-site architecture and clustered mode with more than 500 cameras, one must deploy the RMF services components on a Dedicated RMF Server (DRMF). This server must have the exact machine specifications as the Milestone Management Server. For high availability, the DRMF server can be clustered.

RMF Service Components

The following Service components are installed on the Dedicated RMF Server (DRMF):

• RMF SmartSync Service

• RMF Alarm Service

• RMF Configurator

• Milestone Management Client

For more information on the installation procedures of these components, refer to the following sections:

For additional information on the Milestone XProtect Management Client, refer to the Milestone XProtect documentation.

RMF Smart Client Component

The RMF Smart Client Component is installed on the Smart Client Machine (SC1).

For deployments with less than 500 cameras

For an Independent architecture, clustered mode with less than 500 cameras, deploy the following components.

Note: All RMF components are installed only on Site 1.

RMF Service Components

The following Service components are installed on the Management Servers M1 and M2:

• RMF SmartSync Service

• RMF Alarm Service

• RMF Configurator

• Milestone Management Client

For more information on the RMF Services installation, refer to the following sections:

For additional information on the Milestone XProtect Management Client, refer to the Milestone XProtect documentation.

For deployments with more than 500 cameras

For an Independent architecture, clustered mode with more than 500 cameras, the RMF services components must be deployed on a dedicated RMF server (DRMF). This server must have the exact machine specifications as the Milestone Management Server. The DRMF server can be clustered to ensure high availability.

RMF Service Components

The following Service components are installed on the Dedicated RMF Server (DRMF):

• RMF SmartSync Service

• RMF Alarm Service

• RMF Configurator

• Milestone Management Client

For more information on the installation procedures of these components, refer to the following sections:

For additional information on the Milestone XProtect Management Client, refer to the Milestone XProtect documentation.

For deployments with less than 500 cameras

For independent architecture, in a non-clustered mode with less than 500 cameras, the following components are deployed:

For deployments with less than 500 cameras

For a Single Site architecture and non-clustered mode with less than 500 cameras, deploy in the following way:

RMF Service Components

The following Service components are installed on the Management Server M1:

The following RMF uninstallation procedures are explained in this section:

• Manual Uninstallation

• Silent Uninstallation

Perform the following steps in sequence for RMF offline license activation:

• Export License for Activation

• Import Activated License

Perform the following post-installation steps to verify that the RMF Client components are successfully installed.

1. Launch the Milestone XProtect Smart Client on the machine where the RMF Smart Client package is installed and sign in to the application.

1. Verify that the newly installed plugin appears under the MIP SDK Tools tree in the Smart Client application.

Perform the following steps to uninstall RMF:

1. Start the "Command Prompt" with administrator privileges.

1. Execute the following command:

RMF_Installer.exe /exenoui /qn /x 

RMF enables bi-directional synchronization based on the Direction setting, allowing users to automatically back up configurations to the redundant site or easily restore configurations from it.

This option starts the SmartSync Service.

Select Start from the SmartSync Service Settings.

For more information on how to enable the SmartSync Service, refer to the section: Enable the SmartSync Service

Perform the following post-installation steps to verify that the RMF Services and UI are successfully installed.

1. Launch the XProtect Management Client on the machine where the RMF Services are installed and sign in to the application.

1. After signing in, verify that the RMF is visible in the screen's bottom left corner under the MIP Plugins tree view.

1. Expand the RMF Expand button to view the Redundancy Configuration.

This option stops the execution of SmartSync Service.

Select Stop from the SmartSync Service Settings.

1. Open the Milestone XProtect Management Client.

2. Navigate to MIP Plug-ins > RMF > Redundancy Configuration.

Perform the following steps to export the license for activation:

1. Ensure the RMF is visible under the Installed Products section.

1. Select Activate License Manually → Offline.

• Open the Milestone XProtect Management Client.

• Navigate to MIP Plug-ins > RMF > Redundancy Configuration.

• We should see the Config dashboard on the right pane.

The RMF SmartSync Service is the workhorse that synchronizes control information in an active-active architecture.

Enable the SmartSync Service by moving the toggle button to show 'Enabled.'

SmartSync Service Settings

After enabling, wait a few seconds and verify that the SmartSync service System Tray icon shows a green dot. The following SmartSync settings are available from the System tray.

This option opens the log information for the present day.

Select Show Log from the SmartSync Service settings.

Introduction

When a camera reaches end-of-life, Milestone XProtect allows you to swap it out in place, ensuring all views, rules, and permissions remain intact. In an active-active environment, you would typically have to redo that swap on every redundant recorder. RMF’s Replace Camera feature does it for you automatically:

• Backup mode: Replacing a camera on the Primary recorder instantly triggers the same replacement on the linked Secondary

About

The Scheduling feature in the RMF SmartSync service, located within the Redundancy Configuration module, enables users to automate synchronization processes at predefined intervals. By enabling scheduling, administrators can ensure seamless data consistency across linked servers without manual intervention. This enhances system reliability and ensures redundancy is maintained efficiently.

To turn off scheduling in RMF SmartSync Service, follow these steps to prevent automated synchronization and scheduled executions.

1. Open the Milestone XProtect Management Client.

2. Navigate to MIP Plug-ins > RMF > Redundancy Configuration.

Perform the following steps to import the activated license:

1. Select Activate License Manually → Offline in the Management Client.

2. Select Import Activated License.

Prerequisite:

Please send your XProtect SLC (Software License Code) to [email protected] and wait for an email from Vega confirming the license activation.

Execute the following commands on the command prompt.

1. Complete all the steps as described in the Pre-Installation section.

2. Navigate to the location where the RMF_Installer.exe is available.

3. Start the "Command Prompt" with administrator privileges and navigate to the location where the setup is available.

1. Execute the following commands to install RMF:

a. Without RMF Bookmark Tab in the Smart Client:

b. With RMF Bookmark Tab in the Smart Client:

RMF offers a Restore Mode, in which the RMF SmartSync service copies changes from the secondary site to the primary site. The Restore Mode is a convenient feature that can save administrators time in various scenarios, such as:

• Administrators can restore deleted devices, roles, views, and groups on the primary site if accidentally deleted.

• Admin can quickly fix misconfigurations on the primary site.

• In cases where XProtect is Federated or Independent, and the primary site has been offline, users may have made changes directly on the secondary site. Restore Mode allows the administrator to restore those changes from the secondary site to the primary, ensuring flexibility in management.

To switch to Restore mode, perform the following steps:

1. Move the Direction toggle button at the bottom to display blue.

1. Click Yes when the following pop-up screen appears.

1. Click OK when the confirmatory pop-up screen appears.

1. Click Save in the Milestone toolbar to save the changes.

1. Click the Next arrow button on the screen that appears.

1. Click the Next arrow button on the screen that appears.

1. Click the Finish button to acknowledge.

About

Use this option to synchronize Microphone settings between Primary and Redundant sites.

Scope

The scope of action is limited to RMF-licensed devices selected in the section. The direction of synchronization depends on the direction setting. See . If no devices are selected in the Device Selection block, this option is disabled.

Enable

To enable microphone settings synchronization, perform the following steps:

1. Click Microphone.

1. Enable the Overall Microphone Settings Sync to enable all the individual microphone

   settings. Enable/Disable different sub-settings as needed.

1. To retain the settings, click the Check Mark button.

1. Click Save in the Milestone toolbar to save the changes.

Disable

To turn off the Microphone settings synchronization, perform the following steps:

1. Click Microphone.

1. To turn off the synchronization of the microphone settings, move the toggle button to display red and click the Save icon.

1. Click Save in the Milestone toolbar to save the changes.

About

Use this option to synchronize Speaker settings between the Primary and Redundant sites.

Scope

The scope is limited to RMF-licensed devices selected by the block and to the features listed under the "Settings here correspond to" section in the picture below. The direction of synchronization depends on the direction setting. See . If no devices are selected in the Device Selection block, this option is disabled.

Enable

To enable and synchronize the speaker settings, perform the following steps:

1. Click Speaker.

1. Enable the Overall Speaker Settings Sync to enable all the individual speaker

   settings. Enable/Disable different sub-settings as needed.

1. To retain the settings, click the Check Mark button.

1. Click Save in the Milestone toolbar to save the changes.

Disable

To turn off the Speaker settings synchronization, perform the following steps:

1. Click Speaker.

1. To turn off the synchronization of the microphone settings, move the toggle button to display red and click the Save icon.

1. Click Save in the Milestone toolbar to save the changes.

Introduction

Available in both Auto (Pair Servers) and Manual (Map Cameras) modes, the Delete Camera block ensures that device removals are mirrored across your redundant estate:

• Backup mode: Drop a camera from a Primary, and the same device is removed from its linked Secondary, releasing the RMF licence.

• Restore mode: Deleting the camera on the Secondary erases it from its one-to-one paired Primary as soon as the Primary reconnects.

No orphaned devices, no wasted licences, and no manual clean-up.

Scope

The feature is limited to RMF-licensed cameras.

Enable

1. Click the Delete block.

1. Move the toggle button to enable and click the Save icon.

1. Click Save in the Milestone toolbar to save the changes.

Introduction

The Add Cameras option saves you from double-entry work in active-active deployments. When it is enabled (and Mode = Auto):

Guide

1. Click on Add.

1. Click the Save icon.

1. Click Save in the Milestone toolbar to save your changes.

Introduction

When administrators redistribute cameras—say to load-balance traffic, decommission legacy hardware, or tidy up the estate—they typically drag each device from one primary recorder to another. In an active-active setup, if the same move must also occur on the redundant recorders, the Move Camera block automates that follow-up step:

• Backup mode: A camera moved between Primary recorders is moved in lock-step between their linked Secondary recorders.

• Restore mode: While the DR site is live, any changes made to a secondary are reflected to its one-to-one-linked Primary.

Scope

The feature is limited to RMF-licensed cameras.

Enable

1. Click Move.

1. Move the toggle button to enable and click the Save icon.

1. Click Save in the Milestone toolbar to save the changes.

This option removes the SmartSync Service from the system tray.

Click Exit from the SmartSync Service settings.

This option deletes the log files.

1. Select Clear Log from the SmartSync Service settings.

1. Click the Clear Log drop-down to view the following options:

   1. Today—Deletes log for the current day.

b. Past day—Deletes log from the previous day.

c. All—Deletes the entire log history.

About

Enables users to manually detect and correct configuration mismatches between primary and secondary data centers. It scans devices managed by RMF to identify and resolve inconsistencies.

Supported Modes

• When the synchronization service is in Backup Mode, this tool detects inconsistencies and synchronizes them from the primary data center to the secondary data center. Refer to to enable the backup mode.

• When the synchronization service is in Restore Mode, this tool detects inconsistencies and synchronizes them from the secondary data center to the primary data center. To enable the restore mode, refer to

Key Benefits

• Provides granular control to review and apply only selected changes.

Introduction

Once you have completed each configuration block—Mode Selection, Server Labeling, Server Linking (or Map Cameras in Manual mode), Storage Linking, Add Cameras (if in Auto Mode), and License Management—run Synchronize once to copy every device to its designated secondary recorder and allocate the required RMF licences.

Steps to Run

1. To run the service for the first time, go to the Run tab.

1. Click on the green 'Play' button to start a synchronization run.

2. Wait for the process to finish.

3. Once the initial synchronization is complete, the license count in the top bar will be updated to reflect the number of RMF licenses that have been consumed.

1. Return to the Settings tab and continue with the subsequent configuration.

The Run/Process () monitoring tab in RMF Configuration displays a Monitoring Dashboard with a step-by-step execution timeline of the synchronization process. The interface provides real-time status updates, including the next scheduled run, the duration of the most recent run, and licensing usage information. Administrators can manually trigger the sync process using the Run button. Execution logs categorize operations as successful, failed, or warning alerts.

The system supports manual and scheduled runs, dynamically updating the page in real-time during scheduled executions. Manual runs provide flexibility by allowing users to initiate the process immediately without waiting for a scheduled sync or to trigger an on-demand sync even when scheduling is enabled, but an immediate update is needed. This ensures users have control over execution, whether they prefer automated scheduling or require manual intervention.

Key Functions of the Run/Process Tab

The Run/Process tab provides essential status information, including:

• Scheduled and Manual Execution

  • Next Run ().

  • Last Run Duration ().

• Process Workflow Visualization ().

About

This tool enables the user to select video streams from each camera to transmit to each data center. While primary and secondary data centers must utilize identical camera stream definitions to support redundant recording, each can independently determine which stream to use for live view and playback. This tool streamlines the process of selecting streams.

Key Benefits

• Utilize this tool to achieve asymmetric redundancy by selecting different streams from the same camera in the primary and secondary data centers.

Illustrative Video

About

It enables users to manually select and replicate cameras between primary and secondary data centers. It also identifies devices present in one data center but absent from the other and provides a drag-and-drop interface for assigning and syncing them.

Key Benefit

• Enables selective replication of specific devices.

Perform the following steps for a Single Site architecture:

1. Select the Single Site architecture option.

• For First-time configuration, the following screen will appear.

Introduction

This block appears when Mode Selection () is set to Manual (Map Cameras) and allows you to decide, one device at a time, where each camera stream will be protected. Instead of pairing whole recorders, you drag and drop (or multi-select) cameras from the Primary Cameras list into one or more Secondary Recorders.

About

Use this option to synchronize Metadata settings between the Primary and Redundant sites.

Scope

The scope is limited to RMF-licensed devices selected by the

About

In both Single-Site and Federated architectures, Smart Client users benefit from stream-level failover when viewing video within RMF views. This block, View Synchronization, automatically creates and maintains these RMF views to mirror their corresponding native views. Additionally, this feature generates and maintains a set of Secondary camera views that mirror the primary views across all architectures—Single Site, Federation, and Independent. As a result, if a Smart Client user logs into the secondary management server, they will see the same views as they would if they logged into the primary management server.

This option saves admin users time in duplicate view maintenance.

Overview

Watch the video below for an overview of the capabilities of the SmartSync service. Then follow the steps in the next section to configure the service parameters.

Steps

Perform the following steps, starting with the top.

Introduction

Before RMF can do anything, it needs to identify which recorders are the primaries (the “live” capture points) and which are the secondaries (the backups). During the Server Labeling step, you tag each recorder as either Primary or Secondary. RMF then builds its device list exclusively from these labeled servers; anything left untagged is treated as out of scope, and its cameras never appear in the UI or participate in synchronization or failover. In short, no label, no redundancy—so be sure every recorder that should participate is labeled before you move on to pairing.

Prerequisite

Complete

Label the Servers

Follow these steps to label the servers.

1. Select Label Servers.

a. For an Independent architecture, the following screen appears:

Click Connect at the bottom right corner of the screen to continue.

b. For Federated/Single Site, the following screen appears:

Click Connect at the bottom right of the screen to continue.

1. For more details, click the Help icon in the bottom left corner.

1. Label at least one server as Primary and another server as Secondary.

1. Click the tick mark at the bottom of the screen to save the changes.

5. Click Save in the Milestone toolbar to save the changes.

Perform the following steps for a Federated architecture:

1. Select the Federated architecture option.

• For First-time configuration, the following screen will appear.

• For subsequent architectural changes, click the Architecture button on the following screen.

For more information, click the Help icon.

1. Choose the architecture that represents the XProtect deployment at the site. In this scenario, select Federated.

1. Click the tick mark at the bottom of the screen to save the architecture.

1. Click Yes to confirm.

1. Click the Save icon in the top left corner of the Milestone toolbar to apply the changes.

Step 1: Navigate to System Tray -> Right-click SmartSyncService -> Set Service Logon Settings.

Step 2: Select Federated/Single Site.

Step 3: Provide the credentials. Click the Help icon for more information.

Step 4: Click Save to save the configuration.

1. Click OK.

1. Click OK.

1. Verify that the Federated architecture type is configured successfully. The selected architecture will be displayed on the bottom right.

Introduction

The Server Linking step is where you specify which Primary recording server will fail over to which Secondary recording server.

Prerequisite

Complete

Link the Servers

Perform the following steps to link the Primary and Secondary servers.

1. Select Link Servers.

a. For an Independent architecture, the following screen appears:

Click Connect at the bottom right corner of the screen to continue.

b. For Federated/Single Site, the following screen appears:

Click Connect at the bottom right of the screen to continue.

1. Click the drop-down under the Secondary Server section to view the list of Secondary servers.

1. Select the Secondary server to link to the relevant Primary server.

1. Click the tick mark at the bottom of the screen to save the changes.

1. Click Save in the Milestone toolbar to save the changes.

About

Each hardware device in Milestone can support multiple cameras. Each camera contains many parameters related to stream definitions, PTZ presets, Patrolling, Privacy Masking, and more. This block determines which camera properties will be synchronized by RMF.

The settings apply to all cameras within and across all hardware devices.

Scope

The scope is limited to RMF-licensed devices selected by the block and to the features listed under the "Settings here correspond to" section in the picture below. The direction of synchronization depends on the direction setting. See . If no devices are selected in the Device Selection block, this option is disabled.

Enable

To enable and synchronize camera settings, follow these steps:

1. Click Camera.

1. Turn on the Overall Camera Settings Sync switch to activate all individual camera settings. You can enable or disable different sub-settings as needed.

1. Click the Check Mark button to save and exit.

1. Click Save in the Milestone toolbar to save the changes.

Turning off the Settings Option

Asymmetric Streaming

Asymmetric streaming allows a camera to transmit varying resolutions and frame rates to the Primary and Secondary Data Centers. System integrators can leverage this feature to create a redundancy strategy that fits their budget. For example, while the Primary Data Center may have 10 recorders, the Secondary Data Center might only have 5. However, the Secondary Data Center can still offer complete redundancy by housing more cameras per recorder than the Primary Data Center.

1. To enable asymmetric streaming, turn off the stream synchronization option shown below. When off, the primary and secondary recorders can choose different streams from the list of stream definitions for the camera.

1. Different streams must be chosen in the primary and secondary recorders, either through the tool provided by RMF, under the workflows tab, or directly within Milestone.

Disable

To turn off the camera settings synchronization, perform the following steps:

1. Click Camera.

1. Move the toggle button to display red and click the Save icon.

1. Click Save in the Milestone toolbar to save the changes.

About

In an active-active redundancy setup, modifying user access to a group of primary cameras requires the same changes to the corresponding secondary cameras. Additionally, in multi-database deployments, such as federated or independent sites, any additions or removals of users or changes to roles at one site must be mirrored at the other. Performing these actions manually can be tedious. The role synchronization feature helps automatically synchronize roles between primary and redundant sites.

Scope

The scope is limited to RMF-licensed devices selected by the block and encompasses the features listed under the "Settings here correspond to" section in the picture below. If no devices are selected, this block remains disabled. The direction of synchronization depends on the direction setting. See .

Enable

To enable Roles for synchronization, perform the following steps:

1. Click Roles.

1. Select the roles from the available list to enable automatic synchronization of the selected roles.

1. Click the 'Save' button to confirm and continue.

1. Click Save in the Milestone toolbar to save the changes.

Disable

1. Toggle the button to red to turn off overall role synchronization.

1. Click Save in the Milestone toolbar to save the changes.

About

Use this option to synchronize Speaker settings between the Primary and Redundant sites.

Scope

The scope is limited to RMF-licensed devices selected by the block and to the features listed under the "Settings here correspond to" section in the picture below. The direction of synchronization depends on the direction setting. See . If no devices are selected in the Device Selection block, this option is disabled.

Enable

To enable and synchronize the device output settings, perform the following steps:

1. Click Output.

1. Enable the Overall Output Settings Sync to enable all the individual device output settings. Enable/Disable different sub-settings as needed.

1. To retain the settings, click the Check Mark button.

1. Click Save in the Milestone toolbar to save the changes.

Disable

To disable and synchronize the device output settings, perform the following steps:

1. Click Output.

1. Enable the Overall Output Settings Sync to enable all the individual device output

   settings. Enable/Disable different sub-settings as needed.

1. Click Save in the Milestone toolbar to save the changes.

Next Run

Next Run shows the scheduled time for the system to execute the synchronization process automatically.

Last Run Duration

Last Run Duration displays the total time to complete the most recent synchronization operation.

License

The License utilization section displays the total number of RMF licenses purchased versus those currently in use. It also monitors license usage across multiple sites, ensuring optimal allocation of licenses. Additionally, the License Count indicates the total number of licenses used or available within the system, ensuring proper monitoring and compliance with licensing limits.

Process Workflow Visualization

The process workflow visualization displays the stagewise status of the sync process.

When a synchronization run is not in progress, the color of the LED indicates whether a stage is enabled or not.

• Enabled (green): Indicates that the process is running or scheduled to run as expected. Once the stage is successfully processed, the indicator will turn solid green.

• Disabled (red): Indicates that the stage is disabled, preventing both scheduled and manual executions.

When a synchronization run is in progress, the color of the LED indicates the status of the execution of a particular stage.

• Running/Completed:

  • When a stage is in progress, its indicator blinks green.

  • When a stage has been completed, its status indicator is solid green.

• Yet to run: Yellow indicators signify stages that are enabled but have not yet started or completed processing.

Manual Run Button

The manual run button enables users to initiate a synchronization run on demand, bypassing the need to wait for the next scheduled run. This is useful when users prefer to launch a run manually rather than scheduling a sync, or when they have a planned sync but need to execute a run before the next scheduled time.

Illustrative Run Operation

Open Log Folder

The Open Log Folder feature allows users to access the directory where execution logs are stored. This feature provides direct access to log files, allowing you to review detailed records of run activities, troubleshoot errors, and analyze system behavior. It helps in debugging issues by offering a comprehensive view of past executions.

Logs Section

Displays status logs for each process step, categorized into:

• ✅ Successful Operations (Green Checkmark): Clicking on the number next to this icon will open a notepad-style log displaying details of all completed operations.

• ❌ Failed Operations (Red X): Clicking next to this icon will open a notepad-style log with error messages and reasons for failure, helping users troubleshoot issues.

• ⚠️ Warnings (Yellow Exclamation Mark): Clicking next to this icon will open a notepad-style log highlighting potential issues or warnings that may not have caused failure but need attention.

Execute the following commands on the Silent Installation of All-in-one Package type command prompt.

1. Complete all the steps as described in the Pre-Installation section.

2. Navigate to the location where the RMF_Installer.exe is available.

3. Start the "Command Prompt" with administrator privileges and navigate to the location where the setup is available.

1. Execute the following command:

Introduction

Tick ✓ only the cameras you want RMF to keep identical across sites; any camera you leave unchecked is ignored by every downstream block. After this coarse filter, later blocks—Device Properties, Roles, Views, Device Groups—provide fine-grained switches for each individual property, allowing you to build an exact, policy-driven sync recipe.

Think of Selective Sync as the “big gate” that decides which devices enter the sync pipeline; the blocks that follow let you fine-tune what about those devices stays mirrored, giving you layered, policy-level control over redundancy.

To verify that the RMF components are successfully installed, perform the following post-installation steps.

This option restarts the SmartSync Service.

Select Restart from the SmartSync Settings.