Failover design
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
design failover that works and is safe.
Planned topics
- Topologies: backup and restore, pilot light, warm standby, active-active; cost and RTO fall in that order.
- Failover decisions: automatic (fast, risk of false triggers and split brain) versus manual (slower, deliberate).
- Split brain: two nodes both think they are primary; prevent with fencing and a single authority.
- Recovery depends on more than the database: DNS and traffic switching, secrets, configuration, certificates, access paths, and application readiness.
- Failing back is a separate plan.
Draft outline details
Demonstration
A diagram description: primary region and a warm standby, with data replication, DNS or traffic manager, secrets replicated, runbook steps with owners and timings.
Check your understanding
What is split brain?
Show answer
Two nodes both acting as primary and accepting writes.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.