INFRASTRUCTURE LEARNINGINFRASTRUCTURE LEARNING
インフラ大全インフラ大全IT INFRASTRUCTURE / LEARNING
Infrastructure learning guide
Find a lesson or lab/

Esc to close · Search terms stay on your device

LEARNING日本語

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.

What you will learn

Require data and write-ownership evidence in addition to DNS.

Prerequisite

The cases use fictional inputs.

Start the exercise →

What to predict

Check the old writer, recovery point and client DNS path independently during regional failover.

From conditions to the decision
From conditions to the decision1: Target recovery point — Align conditions — Client DNS result. 2: Client DNS result — Compare outcomes — Old writer still enabled. 3: Old writer still enabled — Verify the decision — Decision123Target recoverypointClient DNS resultOld writer stillenabledDecisionFrom conditions to the decision1: Target recovery point — Align conditions — Client DNS result. 2: Client DNS result — Compare outcomes — Old writer still enabled. 3: Old writer still enabled — Verify the decision — Decision123Target recoverypointClient DNSresultOld writerstill enabledDecision
  1. Target recovery point → Client DNS resultAlign conditions
  2. Client DNS result → Old writer still enabledCompare outcomes
  3. 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

Synthetic observations
CaseConditionsDecision
Trial 1Target recovery point Within target, Client DNS result New record, Old writer still enabled NoThe modeled prerequisites pass. Verify representative reads and writes at the target.
Trial 2Target recovery point Within target, Client DNS result New record, Old writer still enabled YesHold acceptance. Two writers may still exist.
Trial 3Target recovery point Outside target, Client DNS result New record, Old writer still enabled NoThe recovery point misses its target. Review data recovery evidence.
Trial 4Target recovery point Within target, Client DNS result Cached old answer, Old writer still enabled NoSome 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.

Check your understanding

Choose an option to see the result and explanation.

What happens in trial 1?
Read the answer and reason

Answer: The modeled prerequisites pass. Verify representative reads and writes at the target. · 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.

What happens in trial 2?
Read the answer and reason

Answer: Hold acceptance. Two writers may still exist. · Target recovery point Within target, Client DNS result New record, Old writer still enabled Yes → Hold acceptance. Two writers may still exist.

What happens in trial 3?
Read the answer and reason

Answer: The recovery point misses its target. Review data recovery evidence. · 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.

Check, then explain in your own words

  1. Read the initial conditions and operational goal.
  2. Change one condition and compare the decision.
  3. 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.