SafeKit, a Simple High Availability Software Easy to Deploy

All-in-one high availability

In one software product, SafeKit provides on Windows and Linux:

• load balancing
• synchronous real-time file replication
• automatic application failover
• automatic failback after a server failure

Save costs of network load balancers or dedicated proxy servers, shared disk or replicated SAN storage, enterprise editions of Operating Systems and databases, specific skills to maintain operational a cluster.

A complete solution

SafeKit solves:

• hardware failures (20% of problems), including the complete failure of a computer room,
• software failures (40% of problems), including restart of critical processes,
• and human errors (40% of problems) thanks to its ease of use and its web console.

A generic product

You can implement with the SafeKit product real-time replication and failover of any file directory and service, database, complete Hyper-V or KVM virtual machines, Docker, Podman, K3S, Cloud applications (see the module list).

Zero specific skills

No special computer skills are required to deploy a SafeKit high availability cluster.

Zero hardware extra costs

Forget about shared disks, replicated SAN storage... SafeKit is hardware independent and runs on your existing physical servers, or in virtual machines, or in the cloud.

Zero software extra costs

SafeKit works with the standard editions of Windows and Linux and does not require enterprise editions of databases.

Choose between redundancy at the application level or at the virtual machine level

Redundancy at the application level

In this type of solution, only application data are replicated. And only the application is restared in case of failure.

This solution requires a technical understanding of the application. You need to define which services to restart, specify the application folders to replicate, and configure a virtual IP address for failover.

This solution is platform agnostic and works with applications inside physical machines, virtual machines, in the Cloud. Any hypervisor is supported (VMware, Hyper-V...).

• More information: Windows, Linux

Redundancy at the virtual machine level

In this type of solution, the full Virtual Machine (VM) is replicated (Application + OS). And the full VM is restarted in case of failure.

The advantage of this solution is that it does not require a technical understanding of the application; you only need to define the location of the VM files where the application is installed. If you do not know how the application works, this is the best solution.

This solution works with Windows/Hyper-V and Linux/KVM but not with VMware. This is an active/active solution with several virtual machines replicated and restarted between two nodes.

• More information: Windows/Hyper-V, Linux/KVM

Typical usage with SafeKit

Why a replication of a few Tera-bytes?

Resynchronization time after a failure (step 3)

• 1 Gb/s network ≈ 3 Hours for 1 Tera-bytes.
• 10 Gb/s network ≈ 1 Hour for 1 Tera-bytes or less depending on disk write performances.

Alternative

• For a large volume of data, use external shared storage.
• More expensive, more complex.

Why a replication < 1,000,000 files?

• Resynchronization time performance after a failure (step 3).
• Time to check each file between both nodes.

Alternative

• Put the many files to replicate in a virtual hard disk / virtual machine.
• Only the files representing the virtual hard disk / virtual machine will be replicated and resynchronized in this case.

Why a failover ≤ 32 replicated VMs?

• Each VM runs in an independent mirror module.
• Maximum of 32 mirror modules running on the same cluster.

Alternative

• Use an external shared storage and another VM clustering solution.
• More expensive, more complex.

Why a LAN/VLAN network between remote sites?

• Automatic failover of the virtual IP address with 2 nodes in the same subnet.
• Good bandwidth for resynchronization (step 3) and good latency for synchronous replication (typically a round-trip of less than 2ms).

Alternative

• Use a load balancer for the virtual IP address if the 2 nodes are in 2 subnets (supported by SafeKit, especially in the cloud).
• Use backup solutions with asynchronous replication for high latency network.

SafeKit Webinar (9:45)

• Introduction (0:39)
• Demonstration of Evidian SafeKit (1:40)
• Examples of redundancy and high availability solution (1:59)
• Evidian SafeKit sold in many different countries with Milestone (0:49)
• Choose between 2 solutions: virtual machine or application cluster (2:31)
• Distinctive advantages (2:06)

All videos here

Virtual Machine-Level Clustering with Hyper-V: An Example (5:15)

• 2 Hyper-V nodes and 2 virtual machines (0:49)
• Configure the cluster and two hyperv.safe modules (1:59)
• Start and test VM replication, migration, failover on crash (2:26)

Free trial here

Application-Level Clustering with SQL: An Example (8:47)

• 2 nodes with SQL Server (0:32)
• Configure the cluster and the mirror.safe module (3:58)
• Start and test SQL replication, migration, failover on crash (4:17)

Free trial here

Network Load Balancing Clustering with Apache: An Example (5:03)

• 2 nodes with Apache (0:13)
• Configure the cluster and the farm.safe module (2:20)
• Start and test network load balancing, failover on crash (2:30)

Free trial here

How the SafeKit mirror cluster works?

Step 1. Real-time replication

Server 1 (PRIM) runs the application. Clients are connected to a virtual IP address. SafeKit replicates in real time modifications made inside files through the network.

The replication is synchronous with no data loss on failure contrary to asynchronous replication.

You just have to configure the names of directories to replicate in SafeKit. There are no pre-requisites on disk organization. Directories may be located in the system disk.

Step 2. Automatic failover

When Server 1 fails, Server 2 takes over. SafeKit switches the virtual IP address and restarts the application automatically on Server 2.

The application finds the files replicated by SafeKit uptodate on Server 2. The application continues to run on Server 2 by locally modifying its files that are no longer replicated to Server 1.

The failover time is equal to the fault-detection time (30 seconds by default) plus the application start-up time.

Step 3. Automatic failback

Failback involves restarting Server 1 after fixing the problem that caused it to fail.

SafeKit automatically resynchronizes the files, updating only the files modified on Server 2 while Server 1 was halted.

Failback takes place without disturbing the application, which can continue running on Server 2.

Step 4. Back to normal

After reintegration, the files are once again in mirror mode, as in step 1. The system is back in high-availability mode, with the application running on Server 2 and SafeKit replicating file updates to Server 1.

If the administrator wishes the application to run on Server 1, he/she can execute a "swap" command either manually at an appropriate time, or automatically through configuration.

More information on power outage and network isolation in a cluster.

How the SafeKit farm cluster works?

Virtual IP address in a farm cluster

On the previous figure, the application is running on the 3 servers (3 is an example, it can be 2 or more). Users are connected to a virtual IP address.

The virtual IP address is configured locally on each server in the farm cluster.

The input traffic to the virtual IP address is received by all the servers and split among them by a network filter inside each server's kernel.

SafeKit detects hardware and software failures, reconfigures network filters in the event of a failure, and offers configurable application checkers and recovery scripts.

Load balancing in a network filter

The network load balancing algorithm inside the network filter is based on the identity of the client packets (client IP address, client TCP port). Depending on the identity of the client packet input, only one filter in a server accepts the packet; the other filters in other servers reject it.

Once a packet is accepted by the filter on a server, only the CPU and memory of this server are used by the application that responds to the request of the client. The output messages are sent directly from the application server to the client.

If a server fails, the SafeKit membership protocol reconfigures the filters in the network load balancing cluster to re-balance the traffic on the remaining available servers.

Stateful or stateless applications

With a stateful application, there is session affinity. The same client must be connected to the same server on multiple TCP sessions to retrieve its context on the server. In this case, the SafeKit load balancing rule is configured on the client IP address. Thus, the same client is always connected to the same server on multiple TCP sessions. And different clients are distributed across different servers in the farm.

With a stateless application, there is no session affinity. The same client can be connected to different servers in the farm on multiple TCP sessions. There is no context stored locally on a server from one session to another. In this case, the SafeKit load balancing rule is configured on the TCP client session identity. This configuration is the one which is the best for distributing sessions between servers, but it requires a TCP service without session affinity.

SafeKit Customers in all Business Activities

• 

  Best use cases [+]

• 

  Video management, access control, building management [+]

• 

  TV broadcasting [+]

• 

  Finance [+]

• 

  Industry [+]

• 

  Air traffic control [+]

• 

  Bank [+]

• 

  Transport [+]

• 

  Healthcare [+]

• 

  Government [+]