As Linux® on System z® becomes more prevalent and mainstream in the industry, the need for it to deliver higher levels of availability is increasing.
This IBM Redbooks publication starts with an explanation of high availability(HA) fundamentals such as HA concepts and terminology. It continues with a discussion of why a business needs to consider an HA solution and the explaining how to determine your business single points of failure.
We outline the components of a high availability solution and describe these components. We provide some architectural scenarios and demonstrate how to plan and decide an implementation of an end-to-end HA solution from Linux on System z database scenarios to z/OS and include storage, network, z/VM, Linux and middleware.
This implementation includes the IBM Tivoli System Automation for Multiplatforms (TSA MP) which monitors and automates applications distributed across Linux®, AIX®, and z/OS® operating systems as well as a GDPS based solution. It includes the planning for an end-to-end scenario, considering Linux on System z, z/VM and z/OS operating environments and the middleware used.
The TSA MP implements HA for infrastructure, network, operating systems and applications across multiple platforms and is compared to a Linux HA implementation based on Open source Linux-HA which is Linux only.
Related Blog Posts
Table of contents
Chapter 1. High availability fundamentals
Chapter 2. Business and IT availability
Chapter 3. Components of high availability
Chapter 4. Architectural scenarios
Chapter 5. Practical
Chapter 6. Summary
Appendix A. Common TSA Commands
Appendix B. Hints and tips during cluster setup
These pages are Web versions of IBM Redbooks- and Redpapers-in-progress. They are published here for those who need the information now and may contain spelling, layout and grammatical errors.
This material has not been submitted to any formal IBM test and is published AS IS. It has not been the subject of rigorous review. Your feedback is welcomed to improve the usefulness of the material to others.
IBM assumes no responsibility for its accuracy or completeness. The use of this information or the implementation of any of these techniques is a customer responsibility and depends upon the customer's ability to evaluate and integrate them into the customer's operational environment.