The N-to-1 software cluster

Replication and application failover from N servers to 1

In a N-to-1 software cluster, there are N mirror application modules installed on N primary servers and one backup server.

Software cluster with replication and application failover from N servers to 1

In case of failure, unlike the active/active cluster, the backup server doesn't have to handle a double workload when a primary server fails. This assumes there is only one failure at a time - the solution can support multiple primary server failures at the same time, but in this case the single back-up server will have to handle the combined workload of all the failed servers.

More information:

White paper SafeKit


Support \| Contact us Authentication management Enterprise single sign-on Web single sign-on Identity and access management Network and system monitoring High availability For Microsoft Environment Industry Solutions Finance Healthcare Enterprise Government Telecommunications Consulting and implementation Training and certification Support Find a partner Become a partner Resources for partners Training and certification White papers Case studies and brochures Newsletter SSO demo SafeKit trial Overview Careers Offices and distributors Events News
SafeKit home page Features 10 reasons to choose Hard or soft cluster Application modules Mirror cluster Farm cluster Mixed farm/mirror Mutual takeover N-1 Case studies SafeKit case studies Software publisher Distributed enterprise Data center Resources Videos of clusters SafeKit price WP software clustering WP choose a cluster Brochure Free trial of a cluster Download free trial Get evaluation keys Request support User's guide [Web] User's guide [PDF]	Evidian > Products > SafeKit The N-to-1 software cluster Replication and application failover from N servers to 1 In a N-to-1 software cluster, there are N mirror application modules installed on N primary servers and one backup server. In case of failure, unlike the active/active cluster, the backup server doesn't have to handle a double workload when a primary server fails. This assumes there is only one failure at a time - the solution can support multiple primary server failures at the same time, but in this case the single back-up server will have to handle the combined workload of all the failed servers. More information: White paper SafeKit