Mission Critical Systems Management

Features

• Cover Type: Paperback with 640 pages
• Published by: Prentice Hall PTR; Facsimile edition April 28, 1997
• Written in: English
• ISBN 10 Number: 0132402920
• ISBN 13 Number: 978-0132402927
• Book Dimensions: 9.2 x 6.9 x 1.2 inches
• Weighs: 1.6 pounds

Reader Reviews
I first reviewed this book three and a half years ago. It is time for an updated review to reaffirm this book's value nearly four years after it was first published. First, since this book was published there have only been two (that I know of) books that address the topic of mission critical systems management: Blueprints for High Availability: Designing Resilient Distributed Systems and High Avaliability: Design, Techniques and Processes. Second, after reading the other two books this one continues to have a solid place - it fills in gaps of the other two. Third, Mission Critical Systems Management contains the best approach to service level management from among the three books in this category. The key strengths of this book are its straightforward approach to designing, deploying and maintaining highly available systems on a 24x7 basis. The author chronicles his own approach to doing this, which lends authority and credibility to the book. The service level agreement format provided in the book continues to be one of the best I have come across. And the approach itself is sound. There are no discernable weaknesses. Three and a half years ago I gave this book 4 stars because it cited specific products. I am giving it 5 stars today because in retrospect this complaint is irrelevant. What counts is the fact that a technology book written nearly four years ago is as valid and valuable today as when it was first written. Bottom line: Mission Critical Systems Management contains a good balance of process and technical detail, and provides a clear path to achieving 24x7 operations. It fills the gaps of, and augments, the two other books on the subject: High Avaliability: Design, Techniques and Processes (process-oriented) and Blueprints for High Availability: Designing Resilient Distributed Systems (technology-oriented). If you haven't read this book because of its age, read it and marvel at how timeless the contents are. If you read it when it first came out, re-read it and discover how prescient the author was when he sat down to write it. Comment | | (Report this)