T. Anderson and R. Kerr. "Recovery Blocks in Action: A system supporting high reliability," in Proc. 2nd Int. Conf. On Software Engineering, pp. 447-457, San Francisco, IEEE, 1976.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....data, or time redundancy. In the case of functional redundancy, good processors can take over the functionality of failed processors, as in the case of Tandem process pairs [11] or clusters [39] Some forms of recovery use time redundancy and diversity of programming logic (e.g. recovery blocks [7], where the computation of an erroneous result triggers a retry using a different algorithm) but such techniques have had only limited appeal due to their cost of development and maintenance, as well as difficulty in ensuring true independence among the alternate program paths. Failover to a ....

T. Anderson and R. Kerr. Recovery blocks in action: A system supporting high reliability. In Proc. 2nd International Conference on Software Engineering, San Francisco, CA, 1976.

....is executed, or a supplementary recovery process must be invoked in case of a disagreement. Both RB and NVS have evolved procedures for error recovery. In RB, backward recovery is achieved in a hierarchical manner through a nesting of RBs, supported by a recursive cache [Hor74] or recovery cache [And76] that is part of the EE. In NVS, forward recovery is done by the use of the community error recovery algorithm [Tso87] that is supported by 28 AVI ZIENIS the specification of recovery points and by the decision algorithm of the EE. Both recovery methods have limitations: in RB, errors that are ....

T. Anderson and R. Kerr. Recovery blocks in action: a system supporting high reliability. In Proc. 2nd International Conference on Software Engineering, pages 447--457, San Francisco, CA, October 1976.

....Access to the shared storage is synchronized to guarantee that every snapshot read by the sentry is consistent. Most observer systems do not satisfy one or more of these requirements. For example, realtime monitors [6] 9] do not satisfy the linear storage requirement. Recovery block systems [2] [10] do not satisfy the wait freedom requirement. Neither the linear storage requirement nor the wait freedom requirement is satisfied in many low level debuggers [11] 16] or in line assertion checkers such as Anna [12] and Gypsy[7] In order to satisfy these requirements in the sentry system, ....

I. Anderson and R. Kerr. Recovery blocks in action: a system supporting high reliability. In S. K. Shrivastava, editor, Reliable Computer Systems: collected papers of the Newcastle Reliability Project, pages 80--101. Springer-Verlag, 1985.

....to be quite reliable. Software design faults can be introduced at each stage of a software development process. As it is impossible (or extremely difficult) to design fault free software, the design faults must be detected and tolerated during system operation. The recovery block scheme [16] [2] and N version programming [4] 7] are the two most widely known and used software fault tolerance techniques. These techniques are based on design diversity, i.e. the programs must exist in several versions and be produced using the same specifications by different programming teams. There are ....

Anderson T., Kerr R., Recovery Blocks in Action: A System Supporting High Reliability, Proc. 2nd International Conference on Software Engineering, San Fransisco, CA (Oct. 1976) pp. 447 - 457.

....If the software is suspect, an alternative can be executed in place of the original program fragment. If a single processor is used, the state of the processor must be reset to the beginning of the function in question. A mechanism called the recovery cache has been proposed to accomplish this [Anderson 76] A recovery cache records the state of the processor at the entrance to each recovery block. Although a recovery cache is best implemented in hardware, implementations to date have been limited to experimental software. Where multiple processors are available, the retry may take the form of ....

Anderson, T., and R. Kerr, "Recovery Blocks in Action: A System Supporting High Reliability", Proceedings of the Second International Conference on Software Engineering, 1976, 447-457.

No context found.

T. Anderson and R. Kerr. "Recovery Blocks in Action: A system supporting high reliability," in Proc. 2nd Int. Conf. On Software Engineering, pp. 447-457, San Francisco, IEEE, 1976.

No context found.

I. Anderson and R. Kerr, `Recovery blocks in action: a system supporting high reliability', in S. K. Shrivastava, editor, Reliable Computer Systems: Collected papers of the Newcastle Reliability Project, Springer, Berlin, 1985, pp. 80--101.

No context found.

Andersson Y., Kerr R., Recovery Blocks in action: A system Supporting High Reliability, Proceedings of the 2 nd International Conference on Software Engineering, pp. 447-457, 1976

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC