BoilerRoom_RedundantServers is a project that adds a second server computer (Server2) and a second client computer (Client2) to the BoilerRoom_ClientServer project. The computers are defined through the Project Structure Manager.

The Server1 and Server2 computers are redundant servers. Server2 is a secondary server to Server1 (primary server). The respective settings have been configured on the Redundancy page of Server2 (redundancy can be switched on/off through the Secondary server option). Only the server that has the active role provides (in this project) the following functions: simulation of tag data using scripts (analogy to communication with devices in a real project), historical data acquisition, alarm/event generation. Under normal circumstances (i.e., if both servers are running and connected with each other), the primary server has the active role. The secondary server has the standby role, i.e., it does not simulate data, all data (current and historical) and alarms/events are acquired from the primary server (it acts as a client towards the primary server). In the event of a primary server failure, the secondary server will assume the active role. Once the connection with the primary server is reestablished, the secondary server will again assume the standby role.

The Client2 computer has been created by duplicating Client1. A second server connection (pointing to Server2) has been added to the server connection group (named Servers) of the Client1 and Client2 computers. The connection priority is set so that Client1 is primarily connected to Server1 and Client2 is primarily connected to Server2. This setup provides load balancing. If one of the servers is not available (e.g., Server1 is terminated), its client automatically connects to the other server. If a client is not connected to its preferred server, the availability of the server with a higher priority is periodically tested. At runtime, you can view the connection status on the Network connections page in the System Information window.