SafeKit quick installation guide with Milestone XProtect Management Server (milestone.safe mirror module)

Overview of the SafeKit / Milestone XProtect solution

Installation of the SafeKit / Milestone XProtect solution on Windows (milestone.safe)

Prerequisites

You need Milestone XProtect Management and SQL installed on 2 nodes (virtual machines or physical servers). SQL Server and Event Srver can be external, see the notes below.

Note: SQL Server can be external. In this case, at step 4 during the step by step configuration of milestone.safe:

remove the replication of SQL Data and Log folders,
remove the process checker on sqlservr.exe,
remove MSSQLServer from the macro SERVICES.

You can implement redundancy of the external SQL Server with SafeKit and the sqlserver.safe module.

In this case on both management nodes, configure the connection of Milestone Management to SQL with the virtual IP address of the sqlserver.safe module (registry key HKEY_LOCAL_MACHINESOFTWAREVideoOSServerConnectionString).

Note: The Event server can be external to the Management server.

In this case, you have 2 clusters with 2 installations of milestone.safe: one for the Management cluster, the other one for the Event cluster.

For the Management cluster, at step 4 during the step by step configuration of milestone.safe:

remove MilestoneEventServerService from the SERVICES macro.

And for the Event cluster, at step 4 during the step by step configuration of milestone.safe:

remove from the SERVICES macro: MSSQLServer, Milestone XProtect Management Server, Milestone XProtect Log Server,
remove the replication of SQL Data and Log folders,
remove the process checker on sqlservr.exe,
during the step-by-step configuration, register the Event server with the virtual IP address of the Management cluster (or install the Event server from the Download Manager and set the virtual IP address of the Management cluster during the installation),
in the Milestone management client, set the Event Server with the virtual IP address of the Event cluster in the Registered Services.

Recorder redundancy

Replication of recorders is not suitable for SafeKit due to the volume of data.
The solution integrated into Milestone can be used (failover recording server without real-time replication).
Two recorders can also run in an active/active configuration and the cameras are distributed so as not to lose all the cameras in the same area in the event of a failure.
The stream from each camera can also be sent to two recorders with the Vega / RMF solution.

In case of migration of Milestone from version N to version N+1 in a SafeKit cluster, read this article: Milestone Management Migration with SafeKit

Package installation on Windows

Download and install the free version of SafeKit on 2 Windows nodes.

Note: the free version includes all SafeKit features. At the end of the trial, you can activate permanent license keys without uninstalling the package.
Upon completing the package installation, select Set console credentials and firewall rules now and configure a password for the admin user of the SafeKit console.

Set the same password on all nodes.
Exclude from antivirus scans C:/safekit/ (the default installation directory) and all replicated folders that you are going to define.

Antiviruses may face detection challenges with SafeKit due to its close integration with the OS, virtual IP mechanisms, real-time replication and restart of critical services.

Step by step configuration of the SafeKit / Milestone XProtect solution

2. Configure node addresses

Enter the node IP addresses, press the Tab key to check connectivity and fill node names.
Then, click on Save and apply to save the configuration.

If either node1 or node2 has a red color, check connectivity of the browser to both nodes and check firewall on both nodes for troubleshooting.

If you want, you can add a new LAN for a second heartbeat and for a dedicated replication network.

This operation will place the IP addresses in the cluster.xml file on both nodes (more information in the training with the command line).

4. Configure the module

In Module startup at boot, choose an automatic start of the module at boot without delay.
In Macros / SERVICES, enter the service names of your application, in the startup order, separated by commas. See this screenshot for a visual example of Milestone XProtect services.
In Heartbeat networks, you should have a single heartbeat network on which the replication is made. If you have added a private LAN at step 2, then you can configure two heartbeats with the replication flow on the private LAN.
In Virtual IP addresses, enter a virtual IP address. A virtual IP address is a standard IP address in the same IP network (same subnet) as the IP addresses of both nodes.
Application clients must be configured with the virtual IP address (or the DNS name associated with the virtual IP address).
The virtual IP address is automatically switched in the event of a failure.
In Replicated directories, set the paths of directories to replicate. Check that they exist on both nodes and contain the application data.
Data and log replication are essential for a database.
You can create additional replicated directories as required.
See this screenshot for a visual example of Milestone XProtect SQL replication.
In Checkers, you will be able to configure checkers if needed, such as process monitoring, custom checkers, TCP, ping, or split-brain checkers.
For example, if a process name is displayed in Monitored processes/services, it will be monitored with a restart action in case of failure. Configuring a wrong process name will cause the module to stop right after its start.

If SQL is on the management server:

The SQL system databases (like master.mdf and mastlog.ldf) must be located in the same directories on both nodes. The directories must be configured as replicated.
SQL must be also installed at the same location in the file system on both nodes because the read-only SQL resource database is located in the binary and is required for the failover. This database does not need to be replicated.
The SQL Milestone databases (.mdf and .ldf) must be located in the same directories on both nodes. The directories must be configured as replicated. Milestone databases are as follows according this article.

If you click on Advanced configuration, the userconfig.xml file is displayed. This file, automatically populated by the console, is the one that will be deployed on the nodes along with the restart scripts.

5. Edit scripts (optional)

This step is optional and can be skipped in most cases, as the restart scripts are already pre-configured to restart services defined in the previous step.
So, click directly on Next step.
start_prim.ps1 starts all services in the order specified in the SERVICES list, while stop_prim.ps1 stops all services in the reverse order.
Additionally, start_prim.ps1 checks the startup of each service and stops the module if any service fails to start correctly.
During module configuration, the boot startup of services will automatically be set to ‘Manual’. This ensures that services do not start automatically upon system boot, but instead, they will be initiated only when the module itself is started.

9. Start the node with up-to-date data

If node 1 has the up-to-date replicated directories, select it and start it As primary.

When node 2 will be started, all data will be copied from node 1 to node 2.

If you make the wrong choice, you run the risk of synchronizing outdated data on both nodes.

It is also assumed that the Milestone XProtect and SQL application is stopped on node 1 so that SafeKit installs the replication mechanisms and then starts the application in the start_prim script.

Use Start for subsequent starts: SafeKit retains the most up-to-date server. Starting As primary is a special start-up the first time or during exceptional operations.

10. Wait for the transition to ALONE (green)

Node 1 should reach the ALONE (green) state, which means that the virtual IP is set and that the start_prim script has been executed on node 1.

If ALONE (green) is not reached or if the application is not started, analyze why with the module log of node 1.

click the "log" icon of node1 to open the module log and look for error messages such as a checker detecting an error and stopping the module.
click on start_prim in the log: output messages of the script are displayed on the right and errors can be detected such as a service incorrectly started.

If the cluster is in WAIT (red) not uptodate, STOP (red) not uptodate state, stop the WAIT node and force its start as primary.

11. In the desktop of node 1, stop, then register on the vitual IP address and restart the Milestone Management Server

Execute the following bullets on node 1 according the menu in the image:

Right-click on the Milestone Management Server icon in the taskbar.
Stop Management Server Service
Then choose Server Configurator... and register the virtual IP address.
Start Management Server Service

This procedure registers the node 1 management server in the SQL database (running on node 1) through a connection to the virtual address.

12. Solve Windows authentication issue on failover

When you start the Milestone XProtect Management Client, you have to authenticate using one of the following methods. Depending on your choice, specific steps are required to ensure the login works after a SafeKit failover. Reference: View Login Screenshot.

Windows authentication with Active Directory (AD)

Configuration: No special configuration is required.

If Milestone "Windows authentication" is configured with an Active Directory, the user and password information is retrieved from the external AD. After a failover, the secondary node connects to the same AD, so authentication works automatically.

Windows authentication in Workgroup

Configuration: You must add the BUILTIN\Administrators group in "Security / Roles".

Warning: In a Workgroup, local users have different Security Identifiers (SIDs) on each node, even if the names are identical. Only the BUILTIN\Administrators group has the same SID on both nodes.

By adding this group, you can authenticate on the secondary node with any local administrator account after a failover.
Without this, local Windows authentication will fail on the secondary node because the SIDs will not match.

Basic authentication with SQL database

Configuration: Create a user with "Basic authentication" (e.g., "Admin").

For "Basic authentication", the user credentials are stored directly in the SQL database. Because SafeKit replicates the SQL database to the secondary node in real-time, these users are always available immediately after a failover.

13. In the desktop of node 2, register the management server on the vitual IP address

Choose Server Configurator in the taskbar of node 2 and register it on the virtual IP address (see image).
Then Stop Management Server Service.

The account of the user executing the registration on node 2 must have the administrator role in Milestone on node 1.

If it is the local administrator on node 2 who makes the registration, the built-in Windows group BUILTINAdministrators must have been set in Management Client / Security / Roles at Step 12. Else the registration will not work.

This procedure registers the node 2 management server in the SQL database (running on node 1) through a connection to the virtual address.

15. Verify that the cluster is operational

Check that the cluster is green/green with Milestone XProtect and SQL services running on the PRIM node and not running on the SECOND node.
Only changes inside files are replicated in real time in this state.

Register the recording servers with the virtual IP address.
Connect the Milestone Management Client and the Milestone Smart Client on the virtual IP address.

Components that are clients of Milestone XProtect and SQL services must be configured with the virtual IP address. The configuration can be done with a DNS name (if a DNS name has been created and associated with the virtual IP address).

16. Testing

Stop the PRIM node by scrolling down its contextual menu and clicking Stop.
Verify that there is a failover on the SECOND node which should become ALONE (green).
And with Microsoft Management Console (MMC) on Windows or with command lines on Linux, check the failover of Milestone XProtect and SQL services (stopped on node 1 in the stop_prim script and started on node 2 in the start_prim script).

If ALONE (green) is not reached on node2 or if the application is not started, analyze why with the module log of node 2.

click the "log" icon of node2 to open the module log and look for error messages such as a checker detecting an error and stopping the module.
click on start_prim in the log: output messages of the script are displayed on the right and errors can be detected such as a service incorrectly started.

If everything is okay, initiate a start on node1, which will resynchronize the replicated directories from node2.

If things go wrong, stop node2 and force the start as primary of node1, which will restart with its locally healthy data at the time of the stop.

Find more details, along with videos, in the SafeKit Online Training.

🔍 SafeKit High Availability Navigation Hub

Explore SafeKit: Features, technical videos, documentation, and free trial
Resource Type	Description	Direct Link
Key Features	Why Choose SafeKit for Simple and Cost-Effective High Availability?	See Why Choose SafeKit for High Availability
Deployment Model	All-in-One SANless HA: Shared-Nothing Software Clustering	See SafeKit All-in-One SANless HA
Partners	SafeKit: The Benchmark in High Availability for Partners	See Why SafeKit Is the HA Benchmark for Partners
HA Strategies	SafeKit: Infrastructure (VM) vs. Application-Level High Availability	See SafeKit HA & Redundancy: VM vs. Application Level
Technical Specifications	Technical Limitations for SafeKit Clustering	See SafeKit High Availability Limitations
Proof of Concept	SafeKit: High Availability Configuration & Failover Demos	See SafeKit Failover Tutorials
Architecture	How the SafeKit Mirror Cluster works (Real-Time Replication & Failover)	See SafeKit Mirror Cluster: Real-Time Replication & Failover
Architecture	How the SafeKit Farm Cluster works (Network Load Balancing & Failover)	See SafeKit Farm Cluster: Network Load Balancing & Failover
Competitive Advantages	Comparison: SafeKit vs. Traditional High Availability (HA) Clusters	See SafeKit vs. Traditional HA Cluster Comparison
Technical Resources	SafeKit High Availability: Documentation, Downloads & Trial	See SafeKit HA Free Trial & Technical Documentation
Pre-configured Solutions	SafeKit Application Module Library: Ready-to-Use HA Solutions	See SafeKit High Availability Application Modules

SafeKit Quick Installation Guide with Milestone XProtect (milestone.safe Mirror Module)

With the Synchronous Replication and Automatic Failover Provided by Evidian SafeKit

High Availability Quick Installation Guide for Milestone XProtect

1. Overview

2. Installation

3. Configuration

Overview-Installation-Configuration