--- title: "Alternative to SQL Server Always On: HA for Express and Standard Editions" canonical: "https://safekit.eviden.com/best-practises/alternative-always-on-sql-server-express-standard-editions/" description: "Looking for a cost-effective alternative to SQL Server Always On? SafeKit proposes a SANless architecture that brings high availability to SQL Server Express and Standard editions. Enjoy synchronous replication, virtual IP, and automatic failover without a SAN or Active Directory." category: "best-practises" lang: "en" topics: "Alternative to Always On SQL Server for express and standard editions, How the SafeKit mirror cluster works with Microsoft SQL Server?, Video Guide: Configuring a SafeKit HA mirror cluster for SQL Server" --- # Alternative to SQL Server Always On: HA for Express and Standard Editions ## Alternative to Always On SQL Server for express and standard editions ### The solution for Microsoft SQL Server SafeKit brings high availability to Microsoft SQL Server between two redundant nodes with synchronous real-time replication of data and automatic failover. The solution is independent of the Microsoft SQL Server edition and works with express and standard editions. ### A generic product SafeKit is a generic product. You can replicate more than SQL server data and logs. If your application is SQL Server-based with specific folders containing your configuration or other files, you can replicate them in the same way. And you can restart your own services in addition to SQL server services. [SafeKit installation guide with Microsoft SQL Server express and standard editions]() ### Without Microsoft failover cluster SafeKit works without Microsoft failover cluster as with Always On SQL Server. It is an all-in-one offer that brings virtual IP address, synchronous real-time replication of folders, automatic failover and failback, and more... SafeKit eliminates the need for shared disks and database enterprise editions. ### Without domain controller and active directory SafeKit works without configuring domain controller and active directory as with Always On SQL Server. This easy-to-deploy, cost-effective solution does not require any specific skills. ### Without 3 nodes for quorum SafeKit works without the need for 3 nodes for quorum as with Always On SQL Server. In case of network isolation, SafeKit implements a split brain checker with a ping to a router playing the role of witness. Moreover, multiple heartbeats can be easily configured in the product. ### Other redundancy and high availability solutions With SafeKit, you can implement on Windows and Linux, real-time replication and failover of any folders and services, databases, complete Hyper-V or KVM virtual machines, Docker, Kubernetes, Cloud applications. ### 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. ## How the SafeKit mirror cluster works with Microsoft SQL Server? {#safekit-mirror-cluster} ### Step 1. Real-time replication {#step1} Server 1 (PRIM) runs the Microsoft SQL Server application. Clients are connected to a [virtual IP address](https://safekit.eviden.com/best-practises/how-a-virtual-ip-address-works/). SafeKit replicates in real time modifications made inside files through the network. ![File replication at byte level in a mirror Microsoft SQL Server cluster](https://safekit.eviden.com/wp-content/uploads/2023/02/safekit-prim-second-300.png "w:300") The replication is [synchronous](https://safekit.eviden.com/best-practises/synchronous-replication-vs-asynchronous-replication/) 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 {#step2} When Server 1 fails, Server 2 takes over. SafeKit switches the virtual IP address and restarts the Microsoft SQL Server 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 of Microsoft SQL Server in a mirror cluster](https://safekit.eviden.com/wp-content/uploads/2023/02/safekit-stop-alone-300.png "w:300") The failover time is equal to the fault-detection time (30 seconds by default) plus the application start-up time. ### Step 3. Automatic failback {#step3} 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 Microsoft SQL Server cluster](https://safekit.eviden.com/wp-content/uploads/2023/02/safekit-resynchro-alone-300.png "w:300") Failback takes place without disturbing the Microsoft SQL Server 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 Microsoft SQL Server application running on Server 2 and SafeKit replicating file updates to Server 1. ![Return to normal operation in a mirror Microsoft SQL Server cluster](https://safekit.eviden.com/wp-content/uploads/2023/02/safekit-second-prim-300.png "w:300") If the administrator wishes the application to run on Server 1, this can be done manually through the web console at an appropriate time, or automatically through configuration. ### How to configure a SafeKit Mirror Cluster for Microsoft SQL Server? {#safekit-mirror-cluster-configure} ![SafeKit Web Console: High Availability configuration dashboard for Microsoft SQL Server showing heartbeat networks, virtual IP setup, and real-time directory replication for a mirror cluster.](https://safekit.eviden.com/wp-content/uploads/2026/01/safekit-mirror-cluster-config.png "w:763") The **SafeKit web console** provides an intuitive interface to orchestrate high availability for your critical applications. In just a few steps, you can configure a **SafeKit mirror cluster** to ensure business continuity: * **Application Failover (Macros Tab):** Define the specific application services to be automatically restarted in the event of a failure. * **Heartbeat network(s):** Dedicated communication path(s) used by cluster nodes to continuously monitor each other's health and availability and synchronize failover decisions. * **Virtual IP Management:** Set up the Virtual IP (VIP) for transparent client reconnection after a failover. * **Real-Time Replication:** Select the critical directories for host-based, synchronous byte-level replication. * **Checkers:** Monitor the application's health and trigger automatic recovery if a process failure is detected. The SafeKit cluster includes a dedicated split-brain checker to resolve network isolation issues without the need for a third witness machine or an additional heartbeat network. Learn more about [heartbeat, failover and quorum in a cluster](https://safekit.eviden.com/best-practises/heartbeat-failover-quorum-windows-linux-cluster/). ### How to monitor a SafeKit mirror cluster for Microsoft SQL Server? {#safekit-mirror-cluster-monitoring} ![SafeKit Web Console: Real-time monitoring of a 2-node mirror cluster for Microsoft SQL Server showing PRIM and SECOND states with active data replication.](https://safekit.eviden.com/wp-content/uploads/2026/05/mirror-monitoring-prim-second.png "w:604") The **SafeKit management console** offers a unified view of your high availability infrastructure. It allows administrators to monitor the **operational state** of the cluster and track data synchronization in real-time. For a 2-node mirror cluster, the console clearly displays the roles of each server: * **PRIM (Primary):** The active node currently running the application and managing the Virtual IP. It performs writes to the local storage and real-time replication to the secondary node. * **SECOND (Secondary):** The standby node receiving synchronous byte-level updates. It is ready to take over instantly if the Primary fails. * **ALONE State:** Visually alerts you when the cluster is running on a single node (e.g., during maintenance or after a failure), indicating that redundancy is temporarily lost. * **Resynchronization Progress:** When a failed node recovers, its status turns orange during background data reintegration, ensuring no downtime during the "return to normal" phase. Beyond simple status icons, the interface provides **one-click failover orchestration** , allowing you to manually reassign the primary role for planned maintenance while ensuring continuous availability for user activity. ## Video Guide: Configuring a SafeKit HA mirror cluster for SQL Server {#videoguide-safekit-mirror-cluster} ### SafeKit Video: Application-Level Clustering (8:47) {#demo-mirror-ha-cluster} In this video, discover how SafeKit implements a **mirror HA cluster** without the complexity of a SAN. While this demonstration uses Microsoft SQL Server, the solution works identically for other databases and applications. ### Chapters 1. 🎬 [2 nodes with SQL Server](https://youtu.be/mGwEguDnnH0?t=0s) (0:32) 2. 🎬 [Configure the cluster and the mirror.safe module](https://youtu.be/mGwEguDnnH0?t=32s) (3:58) 3. 🎬 [Start and test SQL replication, migration, failover on crash](https://youtu.be/mGwEguDnnH0?t=270s) (4:17) ### Step-by-Step Implementation * 🛠️ [Read the guide on setting up a mirrored cluster on Windows](https://safekit.eviden.com/quick-install/safekit-quick-installation-guide-for-a-new-windows-application-with-real-time-replication-and-failover/) * 🛠️ [Read the guide on setting up a mirrored cluster on Linux](https://safekit.eviden.com/quick-install/safekit-quick-installation-guide-for-a-new-linux-application-with-real-time-replication-and-failover/)