Topic lessonTopic: Applied GitHub Actions and SQL Server recovery labs
Regional failover exercise|SQL Server write ownership and DNS
Check the old writer, recovery point and client DNS path independently during regional failover.
Require data and write-ownership evidence in addition to DNS.
The cases use fictional inputs.
What to predict
Check the old writer, recovery point and client DNS path independently during regional failover.
- Target recovery point → Client DNS resultAlign conditions
- Client DNS result → Old writer still enabledCompare outcomes
- Old writer still enabled → DecisionVerify the decision
- Target recovery point
- Within target / Outside target
- Client DNS result
- New record / Cached old answer
- Old writer still enabled
- No / Yes
- Decision
- Require data and write-ownership evidence in addition to DNS.
Compare the cases
| Case | Conditions | Decision |
|---|---|---|
| Trial 1 | Target recovery point Within target, Client DNS result New record, Old writer still enabled No | The modeled prerequisites pass. Verify representative reads and writes at the target. |
| Trial 2 | Target recovery point Within target, Client DNS result New record, Old writer still enabled Yes | Hold acceptance. Two writers may still exist. |
| Trial 3 | Target recovery point Outside target, Client DNS result New record, Old writer still enabled No | The recovery point misses its target. Review data recovery evidence. |
| Trial 4 | Target recovery point Within target, Client DNS result Cached old answer, Old writer still enabled No | Some clients still use the old answer. Inspect their resolver path. |
Acceptance and limits
A synthetic single-writer scenario. Replication and DNS cache are provided as observations.
Read the initial conditions and operational goal.
Change one condition and compare the decision.
Record the model boundary and outstanding checks.
Change a condition
A synthetic single-writer scenario. Replication and DNS cache are provided as observations.
The modeled prerequisites pass. Verify representative reads and writes at the target.
{"writers":"Hold acceptance. Two writers may still exist.","replica":"The recovery point misses its target. Review data recovery evidence.","cached":"Some clients still use the old answer. Inspect their resolver path.","ready":"The modeled prerequisites pass. Verify representative reads and writes at the target."}Check your understanding
Choose an option to see the result and explanation.
Check, then explain in your own words
- Read the initial conditions and operational goal.
- Change one condition and compare the decision.
- Record the model boundary and outstanding checks.
Check your understanding: Require data and write-ownership evidence in addition to DNS.
A synthetic single-writer scenario. Replication and DNS cache are provided as observations.
Record the model boundary and outstanding checks.
Sources and conditions checked
The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.
Scope and conditionsCheck the old writer, recovery point and client DNS path independently during regional failover.
Used in this lessonWhat to predict Acceptance and limits