This server configuration is for situations that require extremely high availability. It is also the most demanding configuration to manage. A redundant configuration shares a single pool of licenses over three servers (it has to be exactly three) that are in constant communication with each other.

As a result, if a server fails or is shut down for maintenance, the remaining servers support the whole license pool, with no negative effect on license availability. This configuration requires that all three servers reside on the same subnet and have consistent network communications (unlike distributed servers, which can work together over a wide-area network).

This license configuration needs precisely three license servers configured so that they can communicate with each and works best in low-latency LAN environment. While it does provide a higher level of fault-tolerance than Distributed Server deployments it cannot scale as easily since you cannot add more license servers as your usage expands.

In this scenario, the client organization has three License Servers. The system administrator wants to build a fault-tolerant deployment of Alchemy CATALYST licenses, so he has setup three servers that are in constant communications with each other. These servers collectively manage the pool of licenses throughout his organization. So long as two of these servers stay on-line, the entire pool of licenses will be available to his organization. This ensures the highest possible service levels and availability of licenses throughout the enterprise.