Applies to version 14 beta 4 and above.
Connexion version 14 can be deployed in active-passive pairs in order to provide hot fail-over. In order to provide a fully automatic fail-over, the following components are required:
- Two instances of Connexion, running on two separate physical machines.
- An automatic fail-over deployment of SQL Server.
- A fail-over capable switch/router.
The simplest hot fail-over topology requires three physical machines. Two machines each have Connexion and SQL Server, and a third machine is required as a witness server for SQL Server replication. The witness role does not require any system resources, and so can be served by an existing server with a few spare cycles:
If your organization already implements redundancy via other means (Microsoft Clustering Services, virtualization, etc) then we recommend you deploy Connexion on your existing infrastructure.
Creating a Cluster
Install Sql Server
To create the cluster as pictured above, first install SQL Server on both the active, passive, and witness hardware. The active and passive instances must be at least SQL Server standard edition, and the witness can be the express edition. Ensure that the Sql Server Management Studio is included in each installation. You must ensure that each SQL Server instance is configured to allow connections via the network (ie, firewall, surface configuration).
Install Primary Connexion
Install Connexion on the primary / active machine and during the installation configuration, point it to the SQL Server instance installed on the same machine (the primary / active). The next step is to install Connexion on the secondary / passive machine and during the installation configuration, point it to the SQL Server instance installed on the primary machine.
Please watch the following video on initial configuration of a cluster: