This page describes the license rules of the eRez server when running in a multiple server environment. Below is a figure that illustrates the different scenarios described in this article.
 |
The eRez server license is a single server license. This means that you need a license for each machine the software is installed on. There is one exception to this rule. In case you would like to have a failover solution you don’t need an extra license for the failover server. Going into details, there are two scenarios for a failover server setup. Cold spare or hot spare. In case of a cold spare the server is on stand-by, but turned off. In the case of a failure situation the server is turned on at take over the identity of the failing server. In this case there is only running one version of the eRez server at any given time. In the case with a hot spare, a second machine is running somewhere and when the other server fails, the server is ready to run and the surrounding system environment should just notice a short hick-up. When using the hot spare in this manner the license policy is not violated. The hot spare server replaces only the failing server and there is only one eRez server running at the time. There is another scenario where one combines fail-over solutions with a load balancing solution. In this case the servers can take over when the other fails, but both servers are active and share the load. In this case you need two valid eRez licenses. To summarize this, there must be a valid unique license for each instance of the eRez server software running at any given time. Be aware of that there is a price reduction of 15% on the 2nd and following servers in a load balancing environment.
|