Advantages of correctly used service

IP/service name in a SDM HA setup

What is meant by "service IP/service name"?

The SDM "primary" and "secondary" service each receive a separate IP address and a
corresponding DNS entry. This addi;onal IP address is then added as a virtual address to the
exis;ng interface of the respec;ve SDM server.
From then on, all surrounding systems should only use the service names for connec;ons.
The monitoring system not only monitors the two opera;ng systems but also the two service
components.

How does such a setup look in reality

Advantages
Þ The peripheral systems always connect to the correct note, regardless of which one
the produc;ve service is running on.
Þ In the event of a failover, the execu;ng person can perform all tasks autonomously
and does not need DNS or the loadbalancer team.
Þ In the event of a failover, the monitoring "moves" with it
Þ it is also possible to detect false/posi;ve in monitoring (e.g. no lz-ui service is
allowed to run on the "secondary" and trigger an alarm if it is running).
Þ For example, at the end of a maintenance window you can start the serivce IP as the
last one and thus have the possibility to test and control everything before you
"open" the serivce to the outside.
Þ You can differen;ate between "primary" and "secondary" - e.g. a DRBD sync error on
the side of the "secondary" may be weighted differently than on the "primary".
Þ If, for example, the "secondary" node is to be replaced by a special event, the new
server can be set up in parallel and simply takes over "service ip/service name" at the
defined ;me and is the ac;ve secondary note from then on.

There are numerous other advantages that far outweigh the small ini;al addi;onal effort
required for setup. The handling of these IP addresses (ac;va;on and deac;va;on on the
respec;ve server) can be easily scripted.