Blueprints for High Availability

Evan Marcus, Hal Stern9780471430261, 0471430269

Marcus, a software engineer, and Stern, a reliability expert, point out how each of the elements of a computer system can fail and explain how to assess their reliability and attain resiliency and high availability. They offer advice on designing a system to limit the impact of problems such as computer viruses, natural disasters, and the corruption of critical files. This second edition includes more real-life experiences that will help readers avoid common mistakes, and a rewritten chapter on disaster recovery, incorporating lessons learned from 9/11

---

Table of contents :
Blueprints for High Availability……Page 2
Copyright……Page 4
Contents……Page 6
Preface……Page 18
About the Authors……Page 30
1. Introduction……Page 32
2. What to Measure……Page 40
3. The Value of Availability……Page 62
4. The Politics of Availability……Page 92
5. 20 Key High Availability Design Principles……Page 106
6. Backups and Restores……Page 136
7. Highly Available Data Management……Page 180
8. SAN, NAS, and Virtualization……Page 214
9. Networking……Page 234
10. Data Centers and the Local Environment……Page 272
11. People and Processes……Page 294
12. Clients and Consumers……Page 322
13. Application Design……Page 334
14. Data and Web Services……Page 364
15. Local Clustering and Failover……Page 392
16. Failover Management and Issues……Page 418
17. Failover Configurations……Page 446
18. Data Replication……Page 464
19. Virtual Machines and Resource Management……Page 496
20. The Disaster Recovery Plan……Page 504
21. A Resilient Enterprise*……Page 544
22. A Brief Look Ahead……Page 572
23. Parting Shots……Page 586
Index……Page 590