The SafeKit clustering software provides a simple high availability and scalability solution for critical web and database applications. As presented on the figure, with SafeKit, you can implement a farm cluster with network load balancing and failover and a mirror cluster with real-time replication and failover.
For example, with the SafeKit clustering software, you can implement Apache load balancing and MySQL mirroring. For that, you have to deploy a farm module for Apache and a mirror module for SQL server. Each farm and mirror module is configured with its own virtual IP address and its own restart scripts.
Both mirror and farm modules can be deployed on a single cluster of two servers. Apache and MySQL will run on these two servers. Or, as presented on the figure, the two modules can be deployed on different servers. With the SafeKit clustering software, there is no difference between a deployment on the same servers or on different servers.
As a result, network load balancing, real time data mirroring and application failover are managed coherently in a same product. When comparing the SafeKit clustering software with hardware clustering, you see that with SafeKit, you do not need shared disk, replicated SAN, load balancers, Enterprise editions of OS or database.
Video: clustering with load balancing, mirroring and failover >
Evidian SafeKit mirror cluster with real-time file replication and failover | ||
All clustering features | |
|
Synchronous replication | |
|
Fully automated failback procedure | |
|
Replication of any type of data | |
|
File replication vs disk replication | |
|
File replication vs shared disk | |
|
Remote sites and virtual IP address | |
|
Quorum | |
|
Active/active cluster | |
|
Uniform high availability solution | |
|
Evidian SafeKit farm cluster with load balancing and failover | ||
No load balancer or dedicated proxy servers or special multicast Ethernet address | |
|
All clustering features | |
|
Remote sites and virtual IP address | |
|
Uniform high availability solution | |
|
High availability architectures comparison | ||
Feature | SafeKit cluster | Other clusters |
Software clustering vs hardware clustering | | |
Shared nothing vs a shared disk cluster | | |
Application High Availability vs Full Virtual Machine High Availability | Smooth upgrade of application and OS possible server by server (version N and N+1 can coexist) | Smooth upgrade not possible |
High availability vs fault tolerance | Software failure with restart in another OS environment. Smooth upgrade of application and OS possible server by server (version N and N+1 can coexist) | Software exception on both servers at the same time. Smooth upgrade not possible |
Synchronous replication vs asynchronous replication | | |
Byte-level file replication vs block-level disk replication | | |
Heartbeat, failover and quorum to avoid 2 master nodes | | |
Virtual IP address primary/secondary, network load balancing, failover | | |
Deploy a mirror module on 2 servers.
And implement a mirror cluster with real-time file replication and application failover.
The target is an application with a database or flat files to replicate and with an automatic restart in case of failure.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.