...
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.
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.
...
Connexion databases can be named, so it is possible to have multiple Connexion instances hosted by the same database server. It is also possible to have the Connexion message databases hosted by different database servers.
Configuring Database Mirroring
...
Cluster nodes are managed through the "Server Management" configuration screen which can be found by clicking on the second button from the right in the client UI 
.
