High availability and disaster recovery

Lose a process, host, or database node. Keep one safe owner of the stream.

SQL Flow coordinates leased ownership, fences stale writers, and resumes replacement agents from durable state without turning a transient failure into a blind reseed.

Talk through my use case Inspect HA architecture

No double writer

Leases decide ownership; epochs fence the sink.

The control plane schedules an eligible agent and advances an ownership epoch during takeover. Source readers and destinations validate that ownership.

  • ✓Durable lease and epoch state
  • ✓Automatic capability-aware reassignment
  • ✓Sink fencing before target mutation
  • ✓Visible owner and recovery progress

Database-aware continuity

Follow promotion without guessing at the log timeline.

Failover validates database identity and the promoted source timeline before capture resumes. Ambiguous state stops loudly with a recovery action.

  • ✓Source-family-specific promotion validation
  • ✓Checkpoint transfer between eligible agents
  • ✓Backlog drain after recovery
  • ✓Planned switchover and unplanned failover

The payoff

See what the capability changes.

1 owner

Fenced execution

A stale agent cannot apply after ownership moves.

Auto

Agent failover

Healthy capacity takes over a failed pipeline.

Durable

Resume state

Capture and apply restart from persisted positions.

Take the next step

Plan for the failure you cannot schedule.

Bring the database topology, agent locations, and recovery objectives. We will map ownership, fencing, failover, and validation.

Talk through my use case