Weekly Restore Drill Report
Every week we publish the results of the automated restore drills against our own production control-plane database, unedited. Date, engine, format, size, checks, outcome, and the RTO measured in the drill. Runs that fail stay visible; nothing is curated or removed.
Why this page exists: a backup you have never restored is a hypothesis. This is the evidence, refreshed weekly, the same product path every Resistro Cloud tenant gets.
What this is not: no SLA, no guaranteed RTO for your database, no legal certification. It documents the tested restore path of the Resistro control plane. Customer-triggered drills produce their own dated evidence record: selected backup, restore target, outcome, packaged as PDF.
Want a drill against your own setup? Start the 14-day trial, no card, or ask for a guided Enterprise demo.
Latest drill runs
Generated from the pipeline. Failed runs stay in the table.
| # | Date | Status | RTO | Engine | Format | Size | Checks |
|---|---|---|---|---|---|---|---|
| 1 | 11:52 UTC | passed | 2.308s | postgresql | chunked | <1GB | – – – – ✓ ✓ |
| 2 | 11:48 UTC | passed | 2.354s | postgresql | chunked | <1GB | – – – – ✓ ✓ |
| 3 | 09:45 UTC | passed | 1.414s | postgresql | chunked | <1GB | – – – ✓ ✓ ✓ |
| 4 | 09:45 UTC | passed | 2.417s | postgresql | chunked | <1GB | – – – ✓ ✓ ✓ |
| 5 | 03:13 UTC | passed | 2.721s | postgresql | chunked | <1GB | – – – ✓ ✓ ✓ |
| 6 | 09:45 UTC | passed | 1.458s | postgresql | chunked | <1GB | – – – ✓ ✓ ✓ |
| 7 | 09:45 UTC | passed | 2.292s | postgresql | chunked | <1GB | – – – ✓ ✓ ✓ |
| 8 | 07:13 UTC | passed | 2.708s | postgresql | chunked | <1GB | – – – ✓ ✓ ✓ |
| 9 | 11:13 UTC | passed | 2.648s | postgresql | chunked | <1GB | – – – ✓ ✓ ✓ |
| 10 | 09:45 UTC | passed | 1.519s | postgresql | chunked | <1GB | – – – ✓ ✓ ✓ |
| 11 | 09:45 UTC | passed | 2.32s | postgresql | chunked | <1GB | – – – ✓ ✓ ✓ |
| 12 | 14:13 UTC | passed | 2.538s | postgresql | chunked | <1GB | – – – ✓ ✓ ✓ |
| 13 | 09:45 UTC | passed | 1.416s | postgresql | chunked | <1GB | – – – ✓ ✓ ✓ |
| 14 | 09:45 UTC | passed | 2.333s | postgresql | chunked | <1GB | – – – ✓ ✓ ✓ |
| 15 | 18:13 UTC | passed | 2.803s | postgresql | chunked | <1GB | – – – ✓ ✓ ✓ |
| 16 | 09:45 UTC | passed | 2.266s | postgresql | chunked | <1GB | – – – ✓ ✓ ✓ |
| 17 | 09:45 UTC | passed | 1.422s | postgresql | chunked | <1GB | – – – ✓ ✓ ✓ |
| 18 | 22:13 UTC | passed | 2.676s | postgresql | chunked | <1GB | – – – ✓ ✓ ✓ |
| 19 | 09:45 UTC | passed | 2.214s | postgresql | chunked | <1GB | – – – ✓ ✓ ✓ |
| 20 | 09:45 UTC | passed | 1.445s | postgresql | chunked | <1GB | – – – ✓ ✓ ✓ |
| 21 | 01:13 UTC | passed | 2.635s | postgresql | chunked | <1GB | – – – ✓ ✓ ✓ |
| 22 | 09:45 UTC | passed | 1.43s | postgresql | chunked | <1GB | – – – ✓ ✓ ✓ |
| 23 | 09:45 UTC | passed | 2.191s | postgresql | chunked | <1GB | – – – ✓ ✓ ✓ |
| 24 | 04:13 UTC | passed | 2.862s | postgresql | chunked | <1GB | – – – ✓ ✓ ✓ |
| 25 | 09:45 UTC | passed | 1.421s | postgresql | chunked | <1GB | – – – ✓ ✓ ✓ |
| 26 | 09:45 UTC | passed | 2.295s | postgresql | chunked | <1GB | – – – ✓ ✓ ✓ |
| 27 | 08:13 UTC | passed | 2.691s | postgresql | chunked | <1GB | – – – ✓ ✓ ✓ |
| 28 | 12:13 UTC | passed | 2.743s | postgresql | chunked | <1GB | – – – ✓ ✓ ✓ |
| 29 | 09:45 UTC | passed | 1.539s | postgresql | chunked | <1GB | – – – ✓ ✓ ✓ |
| 30 | 09:45 UTC | passed | 2.34s | postgresql | chunked | <1GB | – – – ✓ ✓ ✓ |