Evidian SafeKit provides load balancing and failover in Amazon AWS, the Amazon cloud. This article explains how to implement quickly a load balancing and failover cluster in Amazon AWS. A free trial is offered in the installation instructions section.
This clustering solution is recognized as the simplest to implement by our customers and partners. It is also a complete solution that solves hardware failures (20% of problems) including the complete failure of a computer room, software failures (40% of problems) including software error detection and automatic restart and human errors (40% of problems) thanks to its simplicity of administration.
On the previous figure,
Click on the mirror/farm architecture to understand and try the solution
Real-time replication and failover cluster
Load balancing and failover cluster
|OEM Software||Distributed Enterprise||Remote Sites|
|A software publisher uses SafeKit as an OEM software for high availability of its application||A distributed enterprise deploys SafeKit in many branches without specific IT skills||SafeKit is deployed in two remote sites without the need for replicated bays of disks through a SAN|
1 - The ideal product for a software publisher
“SafeKit is the ideal application clustering solution for a software publisher. We currently have deployed more than 80 SafeKit clusters worldwide with our critical TV broadcasting application.”
2 - The product very easy to deploy for a reseller
“WithNCompany has deployed in South Korea many SafeKit high availability solutions with the Samsung Video Surveillance Platform. SafeKit is appreciated because the product is easy to install and very quickly deployed.”
3 - The product to gain time for a system integrator
“Thanks to a simple and powerful product, we gained time in the integration and validation of our critical projects like the supervision of Paris and Marseille metro lines (the control rooms).”
In video surveillance systems, Evidian SafeKit implements high availability with synchronous replication and failover of
Harmonic is using SafeKit as a software OEM high availability solution and deploys it with its TV broadcasting solutions over satellites, terrestrials, cable, IPTV. Over 80 SafeKit clusters are deployed on Windows for replication of Harmonic database and automatic failover of the critical application. Philippe Vidal, Product Manager, Harmonic says: “SafeKit is the ideal application clustering solution for a software publisher looking for a simple and economical high availability software. We are deploying SafeKit worldwide and we currently have more than 80 SafeKit clusters on Windows with our critical TV broadcasting application through terrestrial, satellite, cable and IP-TV. SafeKit implements the continuous and real-time replication of our database as well as the automatic failover of our application for software and hardware failures. Without modifying our application, it was possible for us to customize the installation of SafeKit. Since then, the time of preparation and implementation has been significantly reduced.”
The European Society of Warranties and Guarantees in Natixis uses SafeKit as a high availability solution for its applications.
Over 30 SafeKit clusters are deployed on Unix and Windows in Natixis.
Fives Syleps, the Sydel software editor implements high availability of its ERP with SafeKit and deploys the solution in the food industry.
Tony Myers, Director of Business Development says:
“By developing applications for air traffic control, Copperchase is in one of the most critical business activities. We absolutely need our applications to be available all the time. We have found with SafeKit a simple and complete clustering solution for our needs. This software combines in a single product load balancing, real time data replication with no data loss and automatic failover. This is why, Copperchase deploys SafeKit for air traffic control in airports in the UK and the 30 countries where we are present.”
Software vendor Wellington IT deploys SafeKit high availability with its banking application for Credit Unions in Ireland and UK.
Peter Knight, Sales Manager says:
“Business continuity and disaster recovery are a major concern for our Locus banking application deployed in numerous Credit Unions around Ireland and the UK. We have found with SafeKit a simple and robust solution for high availability and synchronous replication between two servers with no data loss. With this software solution, we are not dependent on a specific and costly hardware clustering solution. It is a perfect tool to provide a software high availability option to an application of a software vendor.”
Paris transport company (RATP) chose the SafeKit high availability and load balancing solution for the centralized control room of line 1 of the Paris subway.
Stéphane Guilmin, RATP, Project manager says:
“Automation of line 1 of the Paris subway is a major project for RATP, requiring a centralized command room (CCR) designed to resist IT failures. With SafeKit, we have three distinct advantages to meet this need. Firstly, SafeKit is a purely software solution that does not demand the use of shared disks on a SAN and network boxes for load balancing. It is very simple to separate our servers into separate machine rooms. Moreover, this clustering solution is homogeneous for our Windows and Unix platforms. SafeKit provides the three functions that we needed: load balancing between servers, automatic failover after an incident and real time data replication.”
And also, Philippe Marsol, Atos BU Transport, Integration Manager says:
“SafeKit is a simple and powerful product for application high availability. We have integrated SafeKit in our critical projects like the supervision of Paris metro Line 4 (the control room) or Marseille Line 1 and Line 2 (the operations center). Thanks to the simplicity of the product, we gained time for the integration and validation of the solution and we had also quick answers to our questions with a responsive Evidian team.”
The software integrator Systel deploys SafeKit high-availability solution in firefighter and emergency medical call centers.
Marc Pellas, CEO says:
“SafeKit perfectly meets the needs of a software vendor. Its main advantage is that it brings in high availability through a software option that is added to our own multi-platform software suite. This way, we are not dependent on a specific and costly hardware clustering solution that is not only difficult to install and maintain, but also differs according to client environments. With SafeKit, our firefighter call centers are run with an integrated software clustering solution, which is the same for all our customers, is user friendly and for which we master the installation up to after-sales support.”
ERP high availability and load balancing of the French army (DGA) are made with SafeKit.
Alexandre Barth, Systems administrator says:
“Our production team implemented the SafeKit solution without any difficulty on 14 Windows and Linux clusters. Our critical activity is thus secure, with high-availability and load balancing functions. The advantages of this product are easy deployment and administration of clusters, on the one hand, and uniformity of the solution in the face of heterogeneous operating systems, on the other hand.”
RTO is the time during which the application is unavailable in case of failure. RTO of the SafeKit farm solution in Amazon AWS is in the order of a few seconds on hardware failure.
For a hardware failure, RTO = failure detection timeout of the load balancer (depends on its timeout configuration).
For a software failure or an administrator restart, RTO = time to (cleanly) stop services + time to restart them.
Click on the Windows or Linux module to understand and try the solution
Mirror modules (replication and failover)
|Microsoft SQL Server||-|
|Milestone XProtect (based on Microsoft SQL Server)||-|
|Hanwha SSM (based on PostgreSQL)||-|
|Generic mirror module|
Farm modules (load balancing and failover)
|Generic farm module|
High availability architectures comparison
(click on the feature for more information)
|Feature||SafeKit cluster||Other clusters|
|Software clustering vs hardware clustering|| |
A simple software cluster with the SafeKit package installed on two servers
Complex hardware clustering with external storage or network load balancers
|Shared nothing vs a shared disk cluster|| |
SafeKit is a shared-nothing cluster: easy to deploy even in remote sites
A shared disk cluster is complex to deploy
|Application High Availability vs Full Virtual Machine High Availability|| |
SafeKit application HA supports hardware failure, software failure, human errors with quick recovery time
Full virtual machines HA supports only hardware failure with a VM reboot and an unknown recovery time if the OS reboot does not work
|Synchronous replication vs asynchronous replication|| |
SafeKit implements real-time synchronous replication with no data loss in case of failure
With asynchronous replication, there is data loss on failure
|Byte-level file replication vs block-level disk replication|| |
SafeKit implements byte-level file replication and is simply configured with directories to replicate even in the system disk
Block-level disk replication is complex to configure and requires to put application data in a special disk
|Heartbeat, failover and quorum to avoid 2 master nodes|| |
To avoid 2 masters, SafeKit proposes a simple split brain checker configured on a router
To avoid 2 masters, other clusters require a complex configuration with a third machine, a special quorum disk, a special interconnect
|Network load balancing|| |
No special network configuration is required in a SafeKit cluster for network load balancing
Special network configuration is required in other clusters for network load balancing
To deploy the Evidian SafeKit load balancing cluster with failover in Amazon AWS, just click on the following button which deploys everything:
After the click:
After deployment, click on SafeKit-Farm, then go to the output panel and
Note: when the farm cluster is "STOP" on all servers, there is no health check answering OK to the AWS load balancer. In this case, the AWS load balancer sends virtual IP/TCP sessions to all servers: if no Availability Zone contains a healthy target, the load balancer nodes route requests to all targets.
If you want to connect to Virtual Machines through SSH (Linux) or remote desktop (Windows), you can use the SafeKit web console to know IP addresses or DNS names of VMs (next images). Follow the Amazon AWS documentation to connect to the VMs with the AWS.pem key pair: SSH (Linux) with AWS key pair, remote desktop (Windows) with AWS key pair.
In term of VMs, this template deploys:
In term of load balancer, this template deploys:
The load balancer must be configured to periodically send health packets to virtual machines. For that, SafeKit provides a health check which runs inside the virtual machines and which
You must configure the Amazon AWS load balancer with:
For more information, see the configuration of the Amazon AWS load balancer.
The network security must be configured to enable communications for the following protocols and ports:
On both Windows servers
On both Linux servers
The configuration is presented with the web console connected to 2 Windows servers but it is the same thing with 2 Linux servers.
Important: all the configuration must be done from a single browser.
It is recommended to configure the web console in the https mode by connecting to https://<IP address of 1 VM>:9453 (next image). In this case, you must configure before the https mode by using the wizard described in the User's Guide: see "11.1 HTTPS Quick Configuration with the Configuration Wizard".
Or you can use the web console in the http mode by connecting to http://<IP address of 1 VM>:9010 (next image).
Note that you can also make a configuration with DNS names, especially if the IP addresses are not static.
Enter IP address of the first node and click on Confirm (next image)
Click on New node and enter IP address of the second node (next image)
Click on the red floppy disk to save the configuration (previous image)
In the Configuration tab, click on farm.safe then enter farm as the module name and Confirm (next images with farm instead of xxx)
Click on Validate (next image)
Do not configure a virtual IP address (next image) because this configuration is already made in the Amazon AWS load balancer. This section is useful for on-premise configuration only.
If a process is defined in the Process Checker section (next image), it will be monitored with the action restart in case of failure. The services will be stopped an restarted locally on the local server if this process disappears from the list of running processes. After 3 unsuccessful local restarts, the module is stopped on the local server. As a consequence, the health check answers NOT FOUND to the Amazon AWS load balancer and the load balancing is reconfigured to load balance the traffic on the remaining servers of the farm.
start_both and stop_both (next image) contain the start and the stop of services.
Click on Validate (previous image)
Click on Configure (previous image)
Check the success green message on both servers and click on Next (previous image)
Start the cluster on both nodes (previous image). Check that the status becomes UP (green) - UP (green) (next image).
The cluster is operational with services running on both UP nodes (previous image).
Be careful, components which are clients of the services must be configured with the virtual IP address. The configuration can be made with a DNS name (if a DNS name has been created and associated with the virtual IP address).
Check with Windows Microsoft Management Console (MMC) or with Linux command lines that the services are started on both UP nodes. Put services with Boot Startup Type = Manual (SafeKit controls start of services).
Stop one UP node by scrolling down the menu of the node and by clicking on Stop. Check that the load balancing is reconfigured with only the other node taking all TCP connections. And check that the services are stopped on the STOP node with Windows Microsoft Management Console (MMC) or with Linux command lines.
To understand what happens in the cluster, check the SafeKit logs of node 1 and node 2.
To see the module log of node 1 (next image):
To see the application log of node 1 (next image):
To see the logs of node 2 (previous image), click on W12R2server75/UP (it will become blue) on the left side and repeat the same operations.
In Advanced Configuration tab (next image), you can edit internal files of the module: bin/start_both and bin/stop_both and conf/userconfig.xml (next image on the left side). If you make change in the internal files here, you must apply the new configuration by a right click on the blue icon/xxx on the left side (next image): the interface will allow you to redeploy the modified files on both servers.
Configure boot start (next image on the right side) configures the automatic boot of the module when the server boots. Do this configuration on both nodes once the load balancing and failover solution is correctly running.
For getting support on the call desk of https://support.evidian.com, get 2 Snaphots (2 .zip files), one for each server and upload them in the call desk tool (next image).
<!DOCTYPE safe> <safe> <service mode="farm" maxloop="3" loop_interval="24"> <!-- Farm topology configuration --> <!-- Names or IP addresses on the default network are set during initialization in the console --> <farm> <lan name="default" /> </farm> <!-- Software Error Detection Configuration --> <!-- Replace * PROCESS_NAME by the name of the process to monitor --> <errd polltimer="10"> <proc name="PROCESS_NAME" atleast="1" action="restart" class="both" /> </errd> <!-- User scripts activation --> <user nicestoptimeout="300" forcestoptimeout="300" logging="userlog" /> </service> </safe>
@echo off rem Script called on all servers for starting applications rem For logging into SafeKit log use: rem "%SAFE%\safekit" printi | printe "message" rem stdout goes into Application log echo "Running start_both %*" set res=0 rem Fill with your services start call set res=%errorlevel% if %res% == 0 goto end :stop set res=%errorlevel% "%SAFE%\safekit" printe "start_both failed" rem uncomment to stop SafeKit when critical rem "%SAFE%\safekit" stop -i "start_both" :end
@echo off rem Script called on all servers for stopping application rem For logging into SafeKit log use: rem "%SAFE%\safekit" printi | printe "message" rem ---------------------------------------------------------- rem rem 2 stop modes: rem rem - graceful stop rem call standard application stop with net stop rem rem - force stop (%1=force) rem kill application's processes rem rem ---------------------------------------------------------- rem stdout goes into Application log echo "Running stop_both %*" set res=0 rem default: no action on forcestop if "%1" == "force" goto end rem Fill with your services stop call rem If necessary, uncomment to wait for the real stop of services rem "%SAFEBIN%\sleep" 10 if %res% == 0 goto end "%SAFE%\safekit" printe "stop_both failed" :end
<!DOCTYPE safe> <safe> <service mode="farm" maxloop="3" loop_interval="24"> <!-- Farm topology configuration for the membership protocol --> <!-- Names or IP addresses on the default network are set during initialization in the console --> <farm> <lan name="default" /> </farm> <!-- Software Error Detection Configuration --> <!-- Replace * PROCESS_NAME by the name of the process to monitor --> <errd polltimer="10"> <proc name="PROCESS_NAME" atleast="1" action="restart" class="both" /> </errd> <!-- User scripts activation --> <user nicestoptimeout="300" forcestoptimeout="300" logging="userlog" /> </service> </safe>
#!/bin/sh # Script called on the primary server for starting application # For logging into SafeKit log use: # $SAFE/safekit printi | printe "message" # stdout goes into Application log echo "Running start_both $*" res=0 # Fill with your application start call if [ $res -ne 0 ] ; then $SAFE/safekit printe "start_both failed" # uncomment to stop SafeKit when critical # $SAFE/safekit stop -i "start_both" fi
#!/bin/sh # Script called on the primary server for stopping application # For logging into SafeKit log use: # $SAFE/safekit printi | printe "message" #---------------------------------------------------------- # # 2 stop modes: # # - graceful stop # call standard application stop # # - force stop ($1=force) # kill application's processes # #---------------------------------------------------------- # stdout goes into Application log echo "Running stop_both $*" res=0 # default: no action on forcestop [ "$1" = "force" ] && exit 0 # Fill with your application stop call [ $res -ne 0 ] && $SAFE/safekit printe "stop_both failed"