Microsoft SQL Server: The Simplest High Availability Cluster with Synchronous Replication and Failover

Microsoft SQL Server: The Simplest High Availability Cluster with Synchronous Replication and Failover

Evidian SafeKit brings high availability to Microsoft SQL Server. This article explains how to implement quickly a Microsoft SQL Server cluster without shared disk and without specific skills. The high availabity module sqlserver.safe and a free trial are 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 smooth upgrade server by server and human errors (40% of problems) thanks to its simplicity.

How the Evidian SafeKit software simply implements Microsoft SQL Server high availability with real-time synchronous replication and failover without shared disk

How the Evidian SafeKit mirror cluster implements Microsoft SQL Server high availability with synchronous replication and failover?

On the previous figure, the server 1/PRIM runs Microsoft SQL Server services (any edition). Users are connected to the virtual IP address of the mirror cluster. SafeKit replicates files opened by Microsoft SQL Server services in real time. Only changes in the files are replicated across the network, thus limiting traffic (byte-level file replication). Names of file directories containing Microsoft SQL Server services data are simply configured in SafeKit. There are no pre-requisites on disk organization for the two servers. Directories to replicate may be located in the system disk. SafeKit implements synchronous replication with no data loss on failure contrary to asynchronous replication.

In case of server 1 failure, there is an automatic failover on server 2 with restart of Microsoft SQL Server services. Then, when server 1 is restarted, SafeKit implements automatic failback with reintegration of data without stopping Microsoft SQL Server services on server 2. Finally, the system returns to synchronous replication between server 2 and server 1. The administrator can decide to swap the role of primary and secondary and return to a server 1 running Microsoft SQL Server services. The swap can also be done automatically by configuration.

FAQ on Evidian SafeKit

Best use cases [+]

Customers [+]

Application high availability modules [+]

SafeKit Webinar [+]

Pricing - Free trial [+]

Comparison with other solutions [+]

Demonstration of a mirror cluster [+]

What are the advantages of the mirror cluster [+]

What is the recovery time (RTO) in a mirror cluster [+]

What is the data loss (RPO) in a mirror cluster [+]

Installation of SafeKit for Microsoft SQL Server high availability with synchronous replication and failover

Package installation on Windows

On both Windows servers

Configuration instructions

The configuration is presented with the web console connected to 2 Windows servers.

Important: all the configuration is made from a single browser.

Launch the web console in a browser by connecting to http://localhost:9010 (next image)

Start the SafeKit web console for configuring the Microsoft SQL Server module

Enter IP address of the first node and click on Confirm (next image)

SafeKit web console - first node in the Microsoft SQL Server cluster

Click on New node and enter IP address of the second node (next image)

SafeKit web console - second node in the Microsoft SQL Server cluster

Click on the red floppy disk to save the configuration (previous image)

In the Configuration tab, click on sqlserver.safe then enter sqlserver as the module name and Confirm: next images with sqlserver instead of xxx

SafeKit web console - start configuration of Microsoft SQL Server module SafeKit web console - enter Microsoft SQL Server module name

Click on Validate (next image)

SafeKit web console - enter Microsoft SQL Server module nodes

Change the path of replicated directories only if necessary (next image) and enter a virtual IP address. A virtual IP address is a new unused IP address in the same IP network as the IP addresses of the two nodes. The virtual IP address automatically switches in case of failover.

SafeKit web console - enter Microsoft SQL Server parameters

For information:

Click on Validate (previous image)

SafeKit web console - stop the Microsoft SQL Server module before configuration the configuration

Click on Configure (previous image)

SafeKit web console - check the success green message of the Microsoft SQL Server configuration

Check the success green message on both servers and click on Next (previous image).

SafeKit web console - select the Microsoft SQL Server node with the up-to-date database

Select the node with the most up-to-date replicated directories and click on start it to make the first resynchronization in the right direction (previous image). Before this operation, we suggest you to make a copy of replicated directories before starting the cluster to avoid any errors.

SafeKit web console - the first Microsoft SQL Server node starts as primary and is alone

Start the second node (previous image) which becomes SECOND green (next image) after resynchronisation of all replicated directories (binary copy from node 1 to node 2).

SafeKit web console - the second Microsoft SQL Server node starts as SECOND

The cluster is operational with Microsoft SQL Server services running on the PRIM node and nothing running on the SECOND node (previous image). Only modifications inside files are replicated in real-time in this state.

Be careful, components which are clients of the Microsoft SQL Server 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).

Tests

Check with Windows Microsoft Management Console (MMC) that the Microsoft SQL Server services are started on the primary server and stopped on the secondary server. Put Microsoft SQL Server services with Boot Startup Type = Manual (SafeKit controls start of Microsoft SQL Server services).

Stop the PRIM node by scrolling down the menu of the primary node and by clicking on Stop. Check that there is a failover on the SECOND node. And check the failover of Microsoft SQL Server services with Windows Microsoft Management Console (MMC).

To understand what happens in the cluster, check the SafeKit logs of the primary server and the secondary server.

To see the module log of the primary server (next image):

SafeKit web console - Module Log of the PRIM Microsoft SQL Server server

To see the application log of the primary server (next image):

SafeKit web console - Application Log of the PRIM Microsoft SQL Server server

To see the logs of the secondary server (previous image), click on W12R2server75/SECOND (it will become blue) on the left side and repeat the same operations. In the secondary module log, you will find the volume and the reintegration time of replicated data.

Advanced configuration

In Advanced Configuration tab, you can edit internal files of the module: bin/start_prim and bin/stop_prim 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 servers once the high availability solution is correctly running.

SafeKit web console - Automatic boot of Microsoft SQL Server module

Support

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).

SafeKit web console - Microsoft SQL Server snaphots for support

Internal files of the Windows sqlserver.safe module

userconfig.xml

<!DOCTYPE safe>
<safe>
<service mode="mirror" defaultprim="alone" maxloop="3" loop_interval="24" failover="on">
  <!-- Heartbeat Configuration -->
  <!-- Names or IP addresses on the default network are set during initialization in the console -->
  <heart pulse="700" timeout="30000">
    <heartbeat name="default" ident="flow">
    </heartbeat>
  </heart>
  <!-- Virtual IP Configuration -->
  <!-- Replace
     * VIRTUAL_TO_BE_DEFINED by the name of your virtual server 
  -->
  <vip>
    <interface_list>
        <interface check="on" arpreroute="on"> 
	  <real_interface>
               <virtual_addr addr="VIRTUAL_TO_BE_DEFINED" where="one_side_alias" />
          </real_interface>
        </interface>
    </interface_list>
  </vip>
  <!-- Software Error Detection Configuration -->
  <errd polltimer="10">
    <!-- Microsoft SQL Server process -->
    <proc name="sqlservr.exe" atleast="1" action="restart" class="prim" />
    <proc name="sqlagent.exe" atleast="1" action="restart" class="prim" />
    <proc name="sqlwriter.exe" atleast="1" action="restart" class="prim" />
  </errd>
  <!-- File Replication Configuration -->
  <!-- Replace
     * YOUR_INSTANCE to set the directory of your Microsoft SQL Server database and logs
  -->
  <rfs async="second" acl="off" nbrei="3">
	<replicated dir="C:\Program Files\Microsoft SQL Server\YOUR_INSTANCE\MSSQL\DATA" mode="read_only" />
	<replicated dir="C:\Program Files\Microsoft SQL Server\YOUR_INSTANCE\MSSQL\Log" mode="read_only" />
  </rfs>
  <!-- User scripts activation -->
  <user nicestoptimeout="300" forcestoptimeout="300" logging="userlog" />
</service>
</safe>

start_prim.cmd

@echo off
rem Script called on the primary server for starting application services 

rem For logging into SafeKit log use:
rem "%SAFE%\safekit" printi | printe "message"

rem stdout goes into Application log
echo "Running start_prim %*" 

set res=0

net start "MSSQLServer" > nul
if not %errorlevel% == 0 (
  %SAFE%\safekit printi "MSSQLServer start failed"
) else (
  %SAFE%\safekit printi "MSSQLServer started"
)

net start "SQLServerAgent" > nul
if not %errorlevel% == 0 (
  %SAFE%\safekit printi "SQLServerAgent start failed"
) else (
  %SAFE%\safekit printi "SQLServerAgent started"
)

net start "SQLWriter" > nul
if not %errorlevel% == 0 (
  %SAFE%\safekit printi "SQLWriter start failed"
) else (
  %SAFE%\safekit printi "SQLWriter started"
)

if %res% == 0 goto end

:stop
set res=%errorlevel%
"%SAFE%\safekit" printe "start_prim failed"

rem uncomment to stop SafeKit when critical
rem "%SAFE%\safekit" stop -i "start_prim"

:end

stop_prim.cmd

@echo off
rem Script called on the primary server for stopping application services 

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 For logging into SafeKit log use:
rem "%SAFE%\safekit" printi | printe "message"

rem stdout goes into Application log
echo "Running stop_prim %*" 

set res=0

rem default: no action on forcestop
if "%1" == "force" goto end

%SAFE%\safekit printi "Stopping SQLServerAgent..."
net stop "SQLServerAgent" > nul

%SAFE%\safekit printi "Stopping MSSQLServer..."
net stop "MSSQLServer" > nul

%SAFE%\safekit printi "Stopping SQLWriter..."
net stop "SQLWriter" > nul

rem wait a little for a real stop of services
%SAFEBIN%\sleep 10

:end
contact
CONTACT
Demonstration

Evidian SafeKit Pricing





White Papers

NEWS

To receive Evidian news, please fill the following form.