Commercial Fault Tolerance: A Tale of Two Systems

DMCA

Commercial Fault Tolerance: A Tale of Two Systems (2004)

Cached

Download Links

Other Repositories/Bibliography

DBLP

by Wendy Bartlett , Ieee Computer Society , Lisa Spainhower

Venue:	IEEE Transactions on Dependable and Secure Computing
Citations:	58 - 0 self

BibTeX

@ARTICLE{Bartlett04commercialfault,
    author = {Wendy Bartlett and Ieee Computer Society and Lisa Spainhower},
    title = {Commercial Fault Tolerance: A Tale of Two Systems},
    journal = {IEEE Transactions on Dependable and Secure Computing},
    year = {2004},
    volume = {1},
    pages = {2004}
}

OpenURL

Abstract

Abstract—This paper compares and contrasts the design philosophies and implementations of two computer system families: the IBM S/360 and its evolution to the current zSeries line, and the Tandem (now HP) NonStop1 Server. Both systems have a long history; the initial IBM S/360 machines were shipped in 1964, and the Tandem NonStop System was first shipped in 1976. They were aimed at similar markets, what would today be called enterprise-class applications. The requirement for the original S/360 line was for very high availability; the requirement for the NonStop platform was for single fault tolerance against unplanned outages. Since their initial shipments, availability expectations for both platforms have continued to rise and the system designers and developers have been challenged to keep up. There were and still are many similarities in the design philosophies of the two lines, including the use of redundant components and extensive error checking. The primary difference is that the S/360-zSeries focus has been on localized retry and restore to keep processors functioning as long as possible, while the NonStop developers have based systems on a loosely coupled multiprocessor design that supports a “fail-fast ” philosophy implemented through a combination of hardware and software, with workload being actively taken over by another resource when one fails. Index Terms—Computer systems implementation, fault tolerance, high availability. 1

Keyphrases

commercial fault tolerance design philosophy high availability current zseries line extensive error checking localized retry fail-fast philosophy unplanned outage computer system family fault tolerance nonstop1 server system designer availability expectation primary difference multiprocessor design initial shipment similar market index term computer system implementation enterprise-class application initial ibm tandem nonstop system nonstop developer single fault tolerance nonstop platform 360-zseries focus many similarity long history redundant component

DMCA