Use a fence device to cut server A off permanently from the network when it looses network connection. When the cluster failover occurs, it's necessary to restore the previous configuration (server A as primary server and server B as secondary server) manually. A different grace period can be set by using the 'nxserver -clusterupdate' command. Server B fails over only after the 'grace period' that is set by default to 30 seconds. The secondary server monitors server A, if it detects that the primary server is not responding, server B fails over and takes i) the cluster virtual interface and ii) connections to each remote node. The secondary server (server B) is passive, its task is to constantly monitor server A.ī) Server A creates i) the cluster virtual interface and ii) connections to each remote node. The implementation of FR08N03172 will make it automatic.Ī) The primary server (server A) is always active, but it doesn't monitor the secondary server (server B). Until the implementation of this Feature Request: it's necessary to apply the following manual procedure for restarting the master server and restore its original active role. Sessions running on the remote nodes continue to stay connected, management of server-node connections is passed from server A to server B. When the secondary server (server B) looses contact with the primary server (server A), the cluster failover occurs: server B takes place of server A to grant the continuity of services. Thanks to the implementation of this Feature Request:, the procedure for restoring the active/passive roles in a NoMachine cluster after failover has been optimized and it's no longer needed to adopt the manual procedure described below.Ī NoMachine cluster is made of two servers: the primary or master server (server A) and the secondary or slave server (server B). This procedure applies to server versions up to v.

How to restart nomachine server