Wiki source code of Typisches Cluster-Szenario
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
![]() |
1.1 | 1 | {{figure image="FCSnapshot17.png" width="400"}}The most common configuration for a {{formcycle/}}cluster network with two {{fserver number="plural"/}} and two {{mserver number="plural"/}}{{/figure}} |
| 2 | |||
| 3 | {{figure image="FCSnapshot18.png" width="400"}}A {{mserver/}} fails and gets replaced by the second {{mserver/}}.{{/figure}} | ||
| 4 | |||
| 5 | The first illustration shows the most common configuration for a {{formcycle/}} cluster network. | ||
| 6 | |||
| 7 | The frontend servers named 1 and 2 belong to the the //DMZ// (demilitarized zone), the servers named 3 and 4 are part of the intranet. Forms are provided and accepted by a load balancer. This way when a frontend server (1 or 2) fails, forms can still be provided and accepted by the other fronted server. | ||
| 8 | |||
| 9 | Both frontend servers (1 and 2) are connected to the master server 3. | ||
| 10 | |||
| 11 | As shown in the next illustration, when that master server fails, the other master server (server 4) takes over and establishes a connection with both of the frontend server. | ||
| 12 |
