High Availability IT Services

This book starts with the basic premise that a service is comprised of the 3Ps-products, processes, and people. Moreover, these entities and their sub-entities interlink to support the services that end users require to run and support a business. This widens the scope of any availability design far beyond hardware and software. It also increases the potential for service failure for reasons beyond just hardware and software; the concept of logical outages. High Availability IT Services details the considerations for designing and running highly available ""services"" and not just the systems i. Read more... Content: Cover; Contents; Foreword; Preface; Acknowledgments; Author; Part I: An Availability Primer; Chapter 1: Preamble: A View from 30,000 Feet; Chapter 2: Reliability and Availability; Chapter 3: Reliability: Background and Basics; Chapter 4: What is high Availability?; Part II: Availability Theory and Practice; Chapter 5: High Availability: Theory; Chapter 6: High Availability: Practice; Chapter 7: High Availability: SLAs, Management, and Methods; Part III: Vendors and High Availability; Chapter 8: High Availability: Vendor Products. Chapter 9: High Availability: Transaction Processing and DatabasesPart IV: Clouds and Virtualization; Chapter 10: High Availability: The Cloud and Virtualization; Chapter 11: Disaster Recovery Overview; Part V: Appendices and Hard Sums; Appendix 1; Appendix 2; Appendix 3; Appendix 4; Appendix 5; Appendix 6; Appendix 7; Back Cover. Abstract: This book starts with the basic premise that a service is comprised of the 3Ps-products, processes, and people. Moreover, these entities and their sub-entities interlink to support the services that end users require to run and support a business. This widens the scope of any availability design far beyond hardware and software. It also increases the potential for service failure for reasons beyond just hardware and software; the concept of logical outages. High Availability IT Services details the considerations for designing and running highly available ""services"" and not just the systems i