Recognises an RPO the copies cannot deliver
RPO tighter than the most frequent backup or replication interval.
Can AI do this?
Not settled yet The benchmark tested this, but the models' answers do not settle yet whether they master it. 0 of 4 models in the current benchmark master it.
| Model | Tier | Probability of mastery | Status |
|---|---|---|---|
| gemini-4-argon | Flagship | 75% | Not shown |
| gemini-3.5-flash-lite | Low cost | 66% | Not shown |
| gpt-6-luna | Low cost | 66% | Not shown |
| claude-haiku-5-5 | Low cost | 75% | Not shown |
Mastered means a probability of at least 90% that the model has this knobit, estimated from its graded answers. “Not shown” means the answers do not settle it either way. How the models are tested.
What it looks like in practice
Expected result: The defect named on the RPO tighter than backup or replication interval, and its fix or the question for its owner
How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: DS-001 RPO 5 min; log shipping and replication lag 1 hour Acceptable: Log shipping every 5 minutes, or an RPO of 1 hour agreed with the service owner
Also known as: RPO the copies cannot deliver
Related knobits
Builds on
- O-351 Explains recovery objectives and impact tolerances
- O-352 Explains backup and replication mechanics
Usually followed by
All 14 knobits of Plan backup, recovery and continuity.
Source: Review checklist 03-backup-recovery-continuity, row 1 (22301; DORA Art. 12)