Failover: Difference between revisions
From CasGroup
Jump to navigationJump to search
No edit summary |
|||
| Line 1: | Line 1: | ||
'''Failover''' means the automatic substitution of a functionally equivalent system component for a failed one: if one ''fails'' the other can take ''over''. The principle describes the transfer of operation from a failed component to a similar, unused and [[Redundancy|redundant component]] to ensure uninterrupted functionality. It happens automatic without human intervention, and is often found and used in [[Fault Tolerance|fault-tolerant]] architectures. Necessary for successful failover techniques is high [[Redundancy|redundancy]]. | '''Failover''' means the automatic substitution of a functionally equivalent system component for a failed one: if one ''fails'' the other can take ''over''. The principle describes the transfer of operation from a failed component to a similar, unused and [[Redundancy|redundant component]] to ensure uninterrupted functionality. It happens automatic without human intervention, and is often found and used in [[Fault Tolerance|fault-tolerant]] architectures. Necessary for successful failover techniques is high [[Redundancy|redundancy]]. | ||
[[Category:Applied Principles]] | [[Category:Applied Principles]] | ||
Latest revision as of 16:23, 11 February 2011
Failover means the automatic substitution of a functionally equivalent system component for a failed one: if one fails the other can take over. The principle describes the transfer of operation from a failed component to a similar, unused and redundant component to ensure uninterrupted functionality. It happens automatic without human intervention, and is often found and used in fault-tolerant architectures. Necessary for successful failover techniques is high redundancy.
