Data replication techniques

Evidian SafeKit

Data replication techniques at database level, disk level or file level?


This article explores the pros and cons of data replication techniques at database level, disk level and file level for high availability clusters. We are looking at failover, failback, simplicity of implementation.

Data replication techniques

The following comparative tables explain in detail the data replication techniques implemented by SafeKit, a high availability software product.

What is the data replication technique at database level?

It is the replication of log files between two servers made by the database management system (like the SQL Server log).

For an automatic failover, it is mandatory to have synchronous replication otherwise the data of the last validated transactions will not be recovered on the secondary server after a failover.

This data replication technique replicates a database but not the other data of an application. Failover of many applications also requires the replication of other data such as configuration files.

When a server crashes and loses some database files, failback is not automatic. A skilled DBA must restore the database on the failed server.

What is the data replication technique at disk level?

It is the replication of modifications inside disks between two servers (like DRBD).

For an automatic failover, synchronous replication between the disks is mandatory for having 0 data loss.

This data replication technique can replicate databases as well as other files. But, there is a strong impact on the organization of application data. All data must be localized in the relicated disk. This may be impossible if some data to replicate are in the system disk, because this disk must remain specific to each server.

Skills are required to configure a replicated disk with a file system and to configure application data in the replicated disk.

What is the data replication technique at file level?

It is the replication of modifications inside files between two servers (like SafeKit).

For an automatic failover, real-time synchronous replication is required for having 0 data loss.

This data replication technique can replicate databases as well as other files. There is no impact on data organization for an application. For instance, if an application has its data in the system disk, real-time file replication is working.

The solution is very simple to configure as only the paths of directories to replicate are configured.

Comparative tables between data replication techniques

Pros and cons of data replication techniques on the SafeKit example

Evidian SafeKit mirror cluster with real-time file replication and failover

3 products in 1
More info >
Save costs with 3 products in 1
Very simple configuration
More info >
Simple configuration with a web console
Synchronous replication
More info >
Two servers with synchronous replication
Fully automated failback
More info >
Restarting a failed server with automatic failback
Replication of any type of data
More info >
Any replicated data
File replication vs disk replication
More info >
Choose between file replication vs disk replication
File replication vs shared disk
More info >
Choose between file replication vs shared disk
Remote sites and virtual IP address
More info >
Remote sites
Quorum and split brain
More info >
Quorum and split brain issue between remote sites
Active/active cluster
More info >
Active active mirror cluster
Uniform high availability solution
More info >
Uniform high availability solution with farm and mirror clusters
More info >
RPO / RTO for high availability clusters

Partners, the success with SafeKit

This platform agnostic solution is ideal for a partner reselling a critical application and who wants to provide a redundancy and high availability option easy to deploy to many customers.

With many references in many countries won by partners, SafeKit has proven to be the easiest solution to implement for redundancy and high availability of building management, video management, access control, SCADA software...

Building Management Software (BMS)

Video Management Software (VMS)

Electronic Access Control Software (EACS)

SCADA Software (Industry)

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. 

File replication at byte level in a mirror cluster

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.

Failover in a mirror cluster

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 in a mirror cluster

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.

Return to normal operation in a mirror cluster

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.

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.


Why a replication < 1,000,000 files?

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


  • 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 < 25 replicated VMs?

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


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

Why a LAN/VLAN network between remote sites?


  • 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 Modules for Plug&Play Redundancy and High Availability Solutions

SafeKit Modules for Plug&Play High Availability Solutions

Network load balancing and failover

Windows farm

Linux farm

Generic Windows farm   > Generic Linux farm   >
Microsoft IIS   > -
Apache   >
Amazon AWS farm   >
Microsoft Azure farm   >
Google GCP farm   >
Other cloud   >

Advanced clustering architectures

Several modules can be deployed on the same cluster. Thus, advanced clustering architectures can be implemented:

Demonstrations of Redundancy and High Availability Solutions

SafeKit Webinar

This webinar presents in 2 minutes Evidian SafeKit.

In this webinar, you will understand SafeKit mirror and farm clusters.

Microsoft SQL Server Cluster

This video shows a mirror module configuration with synchronous real-time replication and failover.

The file replication and the failover are configured for Microsoft SQL Server but it works in the same manner for other databases.

Free trial here

Apache Cluster

This video shows a farm module configuration with load balancing and failover.

The load balancing and the failover are configured for Apache but it works in the same manner for other web services.

Free trial here

Hyper-V Cluster

This video shows a Hyper-V cluster with full replications of virtual machines.

Virtual machines can run on both Hyper-V servers and they are restarted in case of failure.

Free trial here

SafeKit Technical Documentation

SafeKit Training


  1. Overview / pptx

    • Features
    • Architectures
    • Distinctive advantages
  2. Competition / pptx

    • Hardware vs software cluster
    • Synchronous vs asynchronous replication
    • File vs disk replication
    • High availability vs fault tolerance
    • Hardware vs software load balancing
    • Virtual machine vs application HA

Installation, Console, CLI

  1. Install and setup / pptx
    • Package installation
    • Nodes setup
    • Cluster configuration
    • Upgrade
  2. Web console / pptx
    • Cluster configuration
    • Configuration tab
    • Control tab
    • Monitor tab
    • Advanced Configuration tab
  3. Command line / pptx
    • Silent installation
    • Cluster administration
    • Module administration
    • Command line interface

Advanced configuration

  1. Mirror module / pptx
    • userconfig.xml + restart scripts
    • Heartbeat (<hearbeat>)
    • Virtual IP address (<vip>)
    • Real-time file replication (<rfs>)
  2. Farm  module / pptx
    • userconfig.xml + restart scripts
    • Farm configuration (<farm>)
    • Virtual IP address (<vip>)
  3. Checkers / pptx
    • Failover machine (<failover>)
    • Process monitoring (<errd>)
    • Network and duplicate IP checkers
    • Custom checker (<custom>)
    • Split brain checker (<splitbrain>)
    • TCP, ping, module checkers


  1. Support tools / pptx
    • Analyze snapshots
  2. Evidian support / pptx
    • Get permanent license key
    • Register on
    • Call desk