ExpertPlatform32 min
High availability and DR architecture
How mainframe estates are designed to stay up and to come back: removing single points of failure with Parallel Sysplex, choosing DR topologies and replication against RPO and RTO, keeping batch and online data consistent, and proving it all with tests.
What you will be able to do
- Find single points of failure in a z/OS design and explain how Parallel Sysplex data sharing and workload balancing remove them
- Compare active/standby and active/active DR and choose synchronous, asynchronous or software replication against RPO and RTO targets
- Explain why consistency groups, catalogs and in-flight batch decide whether a DR copy is actually usable
- Plan DR tests and weigh availability features against their cost and complexity
Lessons
- Designing for continuous availabilityHigh availability means the service keeps running when a component fails or is changed.
- DR topologies and replication choicesDisaster recovery architecture decides how a second site takes over when the first is lost.
- Consistency, testing and cost trade-offsA DR copy is only useful if batch, online and system data line up and the team has proven they can recover from it.
Track your progress and earn a certificate.
Free account, 15 quiz questions for this subject.