With the SafeKit software, cluster configuration for a critical application is simple. You must configure either a farm application module or a mirror application module according the high availability architecture suited for your critical application.
Cluster configuration involves writing an application module with the help of the SafeKit web console.
An application module includes:
1. the application stop and start scripts,
2. the configuration file userconfig.xml which contains:
Once the application module is configured and tested, deployment of the HA software cluster requires no specific IT skills:
After cluster deployment, the administrator has a very simple management console (as well as a command line interface), to avoid human errors when managing the critical application.
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 | | |
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.