...
Connexion can be setup in a fault-tolerant configuration to provide hardware fail-over capabilities. The figure below illustrates the standard fail-over configuration for Connexion. The Sql Server back-plane can utilize any of redundancy mechanisms built into Sql Server: Always On, Hardware Clustering, Mirroring, or log shipping. "Always On" requires Sql Server Enterprise Edition which is expensive, so we recommend Mirroring which works with Sql Server Standard Edition.
| Info |
|---|
If your organization already implements redundancy via other means (Microsoft Clustering Services, virtualization, etc) then we recommend you deploy Connexion on your existing infrastructure. |
The Connexion Cluster, shown above, consists of 2 physical, or virtual, machines, which are bound to the same Connexion Configuration Database. The Connexion Cluster operates in an Active/Passive mode where the Active node performs work, and the Passive node is idle until the Active node fails.
...
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
...