Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Failover
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
{{Short description|Automatic switching from failed computer system to standby computers}} '''Failover''' is switching to a [[redundancy (engineering)|redundant]] or standby [[computer]] [[Server (computing)|server]], [[system]], hardware component or network upon the failure or [[abnormal end|abnormal termination]] of the previously active [[Application software|application]],<ref> For application-level failover, see for example {{cite book |last= Jayaswal |first= Kailash |title= Administering Data Centers: Servers, Storage, And Voice Over IP |url= https://books.google.com/books?id=W48oOMKU0RIC |access-date= 2009-08-07 |year= 2005 |publisher= Wiley-India |isbn= 978-81-265-0688-0 |page= 364 |chapter= 27 |chapter-url= https://books.google.com/books?id=W48oOMKU0RIC&pg=PA364 |quote= Although it is impossible to prevent some data loss during an application failover, certain steps can [...] minimize it.}}. </ref> server, system, hardware component, or network in a [[computer network]]. Failover and [[switchover]] are essentially the same operation, except that failover is automatic and usually operates without warning, while switchover requires human intervention. [[File:Duckfone.png|thumb|4G cellular failover for network resiliency]] [[Systems design]]ers usually provide failover capability in servers, systems or networks requiring [[High availability|near-continuous availability]] and a high degree of [[Reliability engineering|reliability]]. At the server level, failover automation usually uses a "[[Heartbeat (computing)|heartbeat]]" system that connects two servers, either through using a separate cable (for example, [[RS-232]] serial ports/cable) or a network connection. In the most common design, as long as a regular "pulse" or "heartbeat" continues between the main server and the second server, the second server will not bring its systems online; however a few systems actively use all servers and can failover their work to remaining servers after a failure. There may also be a third "spare parts" server that has running spare components for "hot" switching to prevent downtime. The second server takes over the work of the first as soon as it detects an alteration in the "heartbeat" of the first machine. Some systems have the ability to send a notification of failover. Certain systems, intentionally, do not failover entirely automatically, but require human intervention. This "automated with manual approval" configuration runs automatically once a human has approved the failover. '''Failback''' is the process of restoring a system, component, or service previously in a state of failure back to its original, working state, and having the standby system go from functioning back to standby. The use of [[Platform virtualization|virtualization]] software has allowed failover practices to become less reliant on physical hardware through the process referred to as [[migration (virtualization)|migration]] in which a running virtual machine is moved from one physical host to another, with little or no disruption in service. '''Failover''' and '''Failback''' technology are also regularly used in the Microsoft SQL Server database, in which SQL Server Failover Cluster Instance (FCI) is installed/configured on top of the '''Windows Server failover Cluster''' (WSFC). The SQL Server groups and resources running on WSFC can manually be [https://www.dbsection.com/how-to-failover-cluster-from-one-node-to-another/ failover to the second node] for any planned maintenance on the first node OR automatically failover to the second node in case of any issues on the first node. In the same way, a failback operation can be performed to the first node once the issue is resolved or maintenance is done on it.
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)