Modern business systems are supported with a high degree of IT automation. Many of these systems are exposed directly to customers via the web, and, as such, those businesses demand 24/7 availability for their most critical systems. In a highly competitive landscape, consequences arising from system outages can be severe, including reputation damage, lost revenues, and a threat for the organization’s ability to survive.
Neverfail Continuity Engine
Fortunately, there is a solution: Neverfail Continuity Engine. IT Infrastructure and Operations (I&O) personnel, as well as application administrators, can be assured that Neverfail is the data protection solution they need.
How does Continuity Engine protect your data? Continuity Engine keeps critical applications and business services in the datacenter continuously running and operational 24/7, while protecting them against down-time from any type of threat or failure conditions.
Neverfail Continuity Engine offers different procedures to change the role of Active and Passive servers. Built-in to Continuity Engine is the ability to switchover and failover. Switchovers are associated with protected applications and failovers are associated with protected servers.
There are seven steps that document the switchover process. See the image below for an illustration of the steps.
The switchover process is instigated either manually or automatically. In both cases the result is application control passes from an active to a passive server in a cluster.
A managed switchover can be initiated manually from the Continuity Engine management interface. When a managed switchover is initiated, the running of protected applications is transferred from the Active server to a Passive server in the Cluster. The result is that the server roles are reversed.
An automatic switchover, or auto-switchover, is triggered automatically if a protected application, which the system is monitoring, fails.
An auto-switchover is different from a managed switchover in that although the server roles are changed, the Continuity Engine service is stopped on the previously Active server to allow the administrator to verify the integrity of the data on the newly Passive server. It also investigates the cause of the auto-switchover. Auto-switchovers are similar to failovers, except that they are initiated upon the failure of a monitored application. Once the cause for the auto-switchover is determined and corrected, the administrator can revert the server roles to their original state.
The failover process can also be instigated either manually or automatically. There are four steps that document the failover process. See the image below for an illustration of the steps.
When a Passive server detects that the Active server is no longer running or responding to its frequent “I’m alive” heartbeat messages, it automatically assumes the role of the Active server.
A managed failover is similar to an automatic-failover in that the Passive server automatically determines that the Active server has failed, and can warn the IT administrator about the failure; but no failover occurs until the IT administrator chooses to trigger this operation manually.
Learn more about Continuity Engine
Your next steps are:
- Read the latest information on Continuity Engine v8.5 Update 3.
- Download the Continuity Engine technical white paper.
If you have questions or need a quote, our team can help you. Simply send an email to firstname.lastname@example.org, and a member of our Cloud experts team will reach out to you. If you are in a business crisis situation and you need help, contact us at +1-512-600-4300.