Recognises a restore slower than the RTO
The last restore took longer than the RTO it is meant to prove.
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 | 66% | Not shown |
| gemini-3.5-flash-lite | Low cost | 44% | Not shown |
| gpt-6-luna | Low cost | 44% | Not shown |
| claude-haiku-5-5 | Low cost | 66% | 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 measured restore time beyond the RTO, and its fix or the question for its owner
How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: DS-005 restore 30 h; RTO 1 day Acceptable: A faster restore method, or the RTO raised with the service owner
Also known as: Restore slower than the RTO
Related knobits
Builds on
All 14 knobits of Plan backup, recovery and continuity.
Source: Review checklist 03-backup-recovery-continuity, row 10 (22301; DORA Art. 12)