In the following section, the most important terms on the subject of high availability are explained:

A Swyx instance is available to users regardless of a hardware failure or application crash. Downtime should be as short as possible. The Swyx HA concept aims for a maximum downtime of a few minutes. Normally the downtime is much shorter, depending on the solution it can even be zero. In general, this approach automatically restores system availability.

The Swyx installation and the corresponding data are backed up regularly so that a customer can restore a Swyx instance from a backup package. Back-ups are also part of an HA/Failover approach when longer downtimes are acceptable. System availability must be restored manually when backups are used.

The entire infrastructure is destroyed at one location. The system is available from another location (geo-redundancy).
Alternatively, if longer downtimes are acceptable, the system will be restored from a backup after restoring the infrastructure.

The downtimes of the Swyx instance during a software or operating system update are as short as possible.

If it is supported by the selected HA/Failover system, the downtime can be very short. In the Swyx HA concept up to 10 minutes are acceptable.