Failover
 | It has been suggested that this article be merged into Fault-tolerant_computer_system#Types_of_fault_tolerance. (Discuss) Proposed since July 2016. |
In computing, failover is switching to a redundant or standby computer server, system, hardware component or network upon the failure or abnormal termination of the previously active application,[1] server, system, hardware component, or network. Failover and switchover are essentially the same operation, except that failover is automatic and usually operates without warning, while switchover requires human intervention.
Systems designers usually provide failover capability in servers, systems or networks requiring continuous availability – the used term is high availability – and a high degree of reliability.
At the server level, failover automation usually uses a "heartbeat" system which connects two servers, either through using a separate cable (for example, RS-232 serial ports/cable) or a network connection. 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. 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.
Some systems, intentionally, do not fail over 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 virtualization software has allowed failover practices to become less reliant on physical hardware; see also migration (virtualization).
History
The term "failover", although probably in use by engineers much earlier, can be found in a 1962 declassified NASA report.[2] The term "switchover" can be found in the 1950s[3] when describing '"Hot" and "Cold" Standby Systems', with the current meaning of immediate switchover to a running system (hot) and delayed switchover to a system that needs starting (cold). A conference proceedings from 1957 describes computer systems with both Emergency Switchover (i.e. failover) and Scheduled Failover (for maintenance).[4]
See also
- Data reliability
- Disaster recovery
- Fault-tolerance
- Fencing (computing)
- High-availability cluster
- Load balancing
- Log shipping
- Safety engineering
- teleportation (virtualization)
References
- ^
For application-level failover, see for example Jayaswal, Kailash (2005). "27". Administering Data Centers: Servers, Storage, And Voice Over IP. Wiley-India. p. 364. ISBN 978-81-265-0688-0. Retrieved 2009-08-07.
Although it is impossible to prevent some data loss during an application failover, certain steps can [...] minimize it.
{{cite book}}: Cite has empty unknown parameter:|trans_chapter=(help); External link in|chapterurl=|chapterurl=ignored (|chapter-url=suggested) (help). - ^ NASA Postlaunch Memorandum Report for Mercury-Atlas, June 15, 1962.
- ^ Petroleum Engineer for Management - Volume 31 - Page D-40
- ^ Proceedings of the Western Joint Computer Conference, Macmillan 1957
 | This computer networking article is a stub. You can help Wikipedia by expanding it. |