After startup -e.g. after both systems were deactivated-, one system (usually the master) is active and the other passive. You can always find out from the SwyxWare Administration which SwyxServer is active and which passive (see The “Standby SwyxServer” Tab). Telephones and can only log on to the active system: the passive system rejects all logons. The replication of the database between the master and standby system is handled in both directions by the replication mechanism of the SQL Server. The file replication is handled in such a way that the contents of the databases are matched within a short time.

When the active system breaks down or is suspended, the passive system notices this (Keep alive mechanism). It then becomes active at once, and takes over the function of the SwyxServer.

If an individual service other than the SwyxServer fails on the active system, the failed service is restarted by the Swyx Helper and is then available once more. The SwyxServer on the system remains active.

In the standard configuration, the other services, such as SwyxGate or the PhoneManager, only interact with the SwyxServer service on their own computer. In a breakdown, all services on the failing system then become passive and are replaced by the corresponding services on the active system.

If a service, e.g. a SwyxGate or a SwyxFax Server is installed separately, i.e. on a computer wihtout SwyxServer service, the service can be configured so that it works together with both systems.

However, there is no seamles switch between the two systems, i.e.:

After the switch, all new calls go via the now active server.

The administrator can also switch manually between the systems, for maintenance purposes for example. The switch can be made in the SwyxWare Administration (see How to change server state manually (active/passive)). The administrator can decide whether the switch should be effective immediately, or the switch should occur automatically as soon as no calls are in progress. In addition, new logins and new calls can both be suppressed in the SwyxWare Administration (see How to prevent new logins and new calls).