Check Continuity Engine Server Status

Check Continuity Engine Server Status

This article describes how to check server status by reviewing several indicators, including the system tray icon, the Server Details page and Applications page in EMS, and Windows services.
Check Server Status

Learning objectives

At the end of the article you should be able to 
  1. Recall the definition of Neverfail Continuity Engine cluster status checking 
  2. Identify the function of each indicator 
  3. Identify four methods to check the server status. 

Overview

A good maintenance system plan includes regular checks to ensure optimum performance. Neverfail Continuity Engine provides multiple indicators to accomplish this task. Each indicator reports different data related to the status and the overall health of the Continuity Engine cluster.

The System Tray Icon 

Right clicking the Continuity Engine system tray icon on any Continuity Engine server reports the identity and role of the server plus the status of data replication. This check however does not provide any further details about replication progress or queue sizes. So you should not rely on this exclusively. 

EMS Server Details Page

The Server Details page of the Engine Management Service offers you a more thorough check. It shows the roles in the identities of the servers and the status of the channel and replication. Check to see that only one server is active and that replication is being performed. 

EMS Applications Page

The Applications page shows the status of all installed applications. It also shows the start/stop tasks after failover or switchover operation and the output from the monitoring tasks, used to keep file filters correctly configured. Make sure that you see no errors which would be highlighted in red. 

Windows Services

Check Windows Services via the Windows Service Control Manager to ensure that the protected application is, in fact, operational on the active server. Also, check to see that the same services are stopped on the passive server, otherwise replication will not function correctly. 

Wrap Up

This knowledge combined with the knowledge gained from other e-learning articles will assist you in achieving success with your Neverfail Continuity Engine product. 

    • Related Articles

    • How to enable DEBUG level logging on Neverfail Continuity Engine Management Service

      Summary  This Knowledgebase article provides information about how to enable DEBUG level logging on Neverfail Continuity Engine Management Service. Procedure To enable DEBUG level logging on Neverfail Continuity Engine Management Service: On the ...
    • Deploying Neverfail Continuity Engine v8.0 onto the Primary Server

      Summary This Knowledgebase article provides the step-by-step procedure to deploy Neverfail Continuity Engine v8.0 onto the Primary server.  More Information Prerequisites Prior to deploying Neverfail Continuity Engine on the target Primary server, ...
    • Continuity Engine Troubleshooting - Synchronization Failures

      Neverfail Continuity Engine provides protection to your applications by replicating data to a passive server. Continuity Engine attempts to synchronize protected data on all servers and continually replicates changes to that data. This article ...
    • Neverfail IT Continuity Engine v8.0 - Release Notes

      Summary This Knowledge base article provides information about this specific release of Neverfail IT Continuity Engine v8.0 More Information Supporting Documentation A listing of technical documents supporting this version of Neverfail IT Continuity ...
    • How to use the Engine Management Service

      Summary This Knowledgebase article provides information about using the Engine Management Service. More Information The Engine Management Service is used to control Neverfail software and provides access to the status of Neverfail Continuity Engine ...