The computer system is protected by multiple hardware firewalls; clustered data servers ensure ongoing operation of the system (in the event of failure of one server, the second server automatically engages to provide uninterrupted service).
Mathematical analysis and simulation results show that the DCube exhibits graceful performance degradation as the failure rate of server or switch increases.
Byzantium [20] considers byzantine failures of servers that guarantee snapshot isolation, as opposed to serializability.
By replicating data items in multiple servers, the failure of some servers does not prevent clients from executing transactions against the system.
In practice, a high degree of fault tolerance can be achieved if a data item is replicated across three servers, provided that failures of those servers are mutually independent.
However, failures of origin servers in a hierarchical origin/edge server setup is a yet unsolved open issue.
Apologies for technical problems yesterday: We had "a critical failure of the NFS server" at 9.30am yesterday morning and it threw everything into chaos.
In addition, newer emails will be copied onto a temporary archive as they travel through the system (either arriving, leaving or travelling through the company): this means that if there is a catastrophic failure of the email server, no work is lost.
Failure of a monitoring server will disrupt data collection from its subtree.
CoRAL provides fault tolerance even for requests being processed at the time of server failure.
Failures of edge servers would affect just the viewers consuming streams from the corresponding location.
