Where the log piles up: replay the lab
Four recorded runs of a six-replica distributed availability group. Pick a scenario, press Play, and watch where the transaction log waits between the primary and each secondary.
Lab companion to the newsletter post SQL Server Availability Group Synchronization State as You’ve Never Seen It.
Recorded November 17, 2026 · sampled every 2 seconds · real data from the lab, server names replaced
How to read it
The lab has two availability groups of three replicas each, joined by an asynchronous distributed availability group. node-1 is the global primary, node-4 is the forwarder. Log travels on five paths: P1 and P2 inside the first group, P3 between the groups, P4 and P5 inside the second group. On every path, log that has not yet been applied on the secondary is in one of four places:
- UnsentStill on the sender, waiting to be sent.
- In flightSent, not yet received.
- Received, not hardenedOn the receiver, waiting for its log disk.
- Hardened, not redoneSafe on the receiver's disk, waiting for redo to apply it.
The size of each stage is evidence of where the log waits. It does not name the cause by itself: the sentence under the controls adds what the other counters say.
Pick a scenario
What was done
What to watch
Flow, primary to secondary
Backlog per path, by stage
Rate at each point, MB/s
Backlog over the run
Numbers at this sample
Events (click to jump)
About the lab
- Six SQL Server replicas on Red Hat Enterprise Linux in Azure: three in East US 2 and three in West US 2, one per availability zone, 4 vCPUs each, with data and log on one Premium SSD v2 disk (3,000 IOPS, 125 MB/s).
- Each run starts with about two minutes of steady load and nothing injected, so you can see the normal state first.
- Each scenario was recorded once. The numbers show what happened in that run on this hardware; they are not limits of the product.
- Not on this page: the load ramp, serial redo, a suspended replica and the loss of the primary, which the lab also recorded.
- You need JavaScript turned on to replay the runs.