This Knowledgebase article provides information about using the Neverfail Heartbeat Management Client.
The Neverfail Heartbeat Management Client is used to control Neverfail software and provides access to the status of Neverfail and the configuration of the software.
Running Neverfail Heartbeat Management Client
The Management Client is launched from
, double-clicking on the
desktop icon, or by right-clicking on the
Neverfail System Tray
icon and choosing
The Management Client presents information gathered from all servers in the group (Primary, Secondary, and if installed, Tertiary) including:
- Server information from Neverfail Heartbeat, such as logged events, connection status, file system and registry status, and channel throughput
- System settings, which may be altered by an administrator
For normal administration purposes, Neverfail recommends that you run a single Neverfail Heartbeat Management Client from a remote client PC, connecting to the principal (public) IP address or DNS name of the server pair.
Information displayed by the Neverfail Heartbeat Management Client
The Neverfail Heartbeat Management Client displays exactly the same information whether it is run on the active or passive server, or remotely from a client machine. It polls roughly every 10 seconds for server information. The server also sends certain information to all currently connected Neverfail Heartbeat Management Clients in response to internal server events. The system settings are loaded from the server only when Neverfail Heartbeat Management Client is first opened.
Multiple Neverfail Heartbeat Management Clients
Neverfail does NOT recommend connecting more than one Neverfail Heartbeat Management Client to a server group at any one time, for the following reasons:
- Running with multiple Neverfail Heartbeat Management Clients connected to the Primary, Secondary, or Tertiary server will cause an increased load on the channel connection and the mechanism that dispatches events to these clients. In certain circumstances, for example when there is a large burst of exception events, the active server could be affected by a lack of memory (java out of memory exceptions) which could stop the protected application.
In certain circumstances, it may be necessary to refresh Neverfail Heartbeat Management Client.
For example, suppose you have one Management Client open on the active server, and one open on the passive server. When changes are made to the Neverfail Heartbeat configuration using the Management Client on the active server, you may have to shut down and restart the Management Client on the passive server to view the changes in the Management Client on the passive server.
This is true wherever you have multiple instances of the Management Client connected to the same server pair - configuration changes made in one Management Client will not be reflected in any of the others until those Management Clients are manually refreshed.
System output from Neverfail Heartbeat, such as logged events, connection status, file system and registry status, and channel throughput, is updated on all panels simultaneously.
Closing the Neverfail Heartbeat Management Client
Neverfail recommends that the Management Client be closed at all times when not in use.
Using Neverfail Heartbeat Management Client via Terminal Services
The Neverfail Heartbeat Management Client is designed to run on a remote client PC, and it is recommended that you install and run the Management Client in this configuration. This will allow remote access to the server pair, regardless of which server is active, without using Windows Terminal Services or Remote Desktop.
If you do choose to run the Neverfail Heartbeat Management Client locally on a server via a Terminal Services remote session, the Management Client must be closed before disconnecting the session. If you close the session without logging out, the applications started in that session, including Neverfail Heartbeat Management Client, will continue to run.