High Availability in Physical Security Market
New application (real-time replication and failover)
New application (network load balancing and failover)
Full VM or container real-time replication and failover
Database (real-time replication and failover)
Web (network load balancing and failover)
Amazon AWS
Google GCP
Microsoft Azure
Other clouds
Physical security (real-time replication and failover)
Basic architectures
Advanced architectures
Hypervisor architectures
Container architectures
High availability best practises
Replication best practises
Clustering best practises
Eviden > Products > SafeKit: All-in-One SANless High Availability & Application Clustering Software > SafeKit: All-in-One Linux Load Balancing & High Availability Software > Linux Network Load Balancing & Failover: Install the SafeKit farm.safe Module
Resynchronization time after a failure (step 3)
This guide explains how to set up a farm cluster for Linux using SafeKit, ensuring network load balancing and automatic failover.
You can use the SafeKit AI 🤖 for assistance at any time.
farm.safe application module.The solution is described here: SafeKit: All-in-One Linux Load Balancing & High Availability Software.
Note: the free trial includes all SafeKit features. At the end of the trial, you can activate permanent license keys without uninstalling the package.
Set the same password on all nodes.
Note: the generic farm.safe module that you are going to configure is delivered inside the package.
http://localhost:9010.admin as user name and the password defined during installation.You can also run the console in a browser on a workstation external to the cluster.
The configuration of SafeKit is done on both nodes from a single browser.
To secure the web console, see 11. Securing the SafeKit web service in the User's Guide.
Tab key to check connectivity and fill node names. 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.Save and apply to save the configuration.Success ✅ message on both nodes.Failure ❌ occurs on one node, open the ▼ accordion for that node and review the messages. Note that you can use the SafeKit AI 🤖 for assistance.
If you want, you can add a new LAN and nodes ( first ➕) to create a second heartbeat and a dedicated replication network.
If you click on Advanced configuration, the cluster.xml file is displayed. This file is automatically populated by the console and deployed on the nodes.
New module, click on the farm.safe module.
In the blue banner at the top, 🛜 node1 represents the console connection node. This node relays requests to node2 when required.
The console looks for xxx.safe in the Application_Modules/generic/ directory on the connection node (node1) if you placed a module there during installation.
Module startup at boot, choose an automatic start of the module at boot without delay.Macros / SERVICES, enter the service names of your application, in the startup order, separated by commas.Heartbeat networks, you should have a single heartbeat network except if you have added a LAN at step 2.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.Load balancing rules, set the service port to load balance (ex.: TCP 9010 in the example).Load balancing rules, set the load balancing rule, Source address or Source port:
Checkers, you will be able to configure checkers if needed, such as process monitoring, custom checkers, TCP, ping, or split-brain checkers.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 you click on Advanced configuration, the userconfig.xml file is displayed. This file is automatically populated by the console and deployed on the nodes with the restart scripts.
In a cloud deployment, you do not need to configure a virtual IP address and load balancing rules in SafeKit. The virtual IP and load balancing rules are managed at the cloud load balancer level.
When you apply the SafeKit configuration, the startup type of services is automatically set to Manual in Windows services. This ensures that services do not start automatically when the system boots, but are instead started only when the module itself is started (the same applies on Linux).
Next step.start_both.ps1 starts all services in the order specified in the SERVICES list, while stop_both.ps1 stops all services in the reverse order.start_both.ps1 checks the startup of each service and stops the module if any service fails to start correctly.
Save and apply the configuration and scripts on both nodes.
Success ✅ message on both nodes and click on Monitor modules.Failure ❌ occurs on one node, open the ▼ accordion for that node and review the messages. Note that you can use the SafeKit AI 🤖 for assistance.
Start the farm cluster as shown in the image.
Node 1 and node 2 should reach the UP (green) state, which means that the start_both script has been executed on node 1 and node 2.
If UP (green) is not reached or if the application is not started, analyze why with the module log 🖼️ of node 1 or node 2.
node1 or node2 to open the module log and look for error messages such as a checker detecting an error and stopping the module.start_both in the log: output messages of the script are displayed on the right and errors can be detected such as a service incorrectly started.
Note that you have a 🕒 timeline 🖼️ that can be helpful to understand what happens in the cluster.
SafeKit brings a built-in test in the product:
You should see a mosaic of colors depending on nodes answering to HTTP requests.
Find more details, along with videos, in the SafeKit Online Training.
Snapshots (2 .zip files), one for each node.
| Resource Type | Description | Direct Link |
|---|---|---|
| AI/LLM Resources | Paste the https://safekit.eviden.com/llms.txt link (or its content) into your favorite AI chatbot for accurate SafeKit answers | See HTML version of llms.txt for more information |
| Key Features | Why Choose SafeKit for Simple and Cost-Effective High Availability? | See Why Choose SafeKit for High Availability |
| Use Cases | Explore How SafeKit Ensures the High Availability of Critical Infrastructure | See All Use Cases (OEM Software, Edge Servers, SCADA, and more) |
| Deployment Model | All-in-One SANless HA: Shared-Nothing Software Clustering | See SafeKit All-in-One SANless HA |
| 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 |