View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011929 | Taler | deployment and operations | public | 2026-11-03 17:14 | 2026-11-03 17:14 |
| Reporter | Christian Grothoff | Assigned To | vecirex | Resolution deadline | 2026-12-06 00:00 |
| Implementer | vecirex | Reviewer | Florian Dold | ||
| Release signed by | vecirex | Deployed by | vecirex | ||
| Verifier | Florian Dold | Communicator | |||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | 4 | Actual effort (hours) | 0 | ||
| Fast-track | No | ||||
| Work package | none | ||||
| Periodic task | Backup restore test — the occurrence of 2026-12-01 — the next is 2027-01-01 | ||||
| Priority | high | Severity | trivial | Reproducibility | N/A |
| Status | implementing | Resolution | open | ||
| Summary | 0011929: Backup restore test | ||||
| Description | Test recovery of key data from backups (production, product- and software-development systems) | ||||
| Steps To Reproduce | For each of these systems, the backup should be restored to another temporary server and checked for completeness, say by counting rows in key database tables or checking the latest Git commits, etc. Naturally, the process should be automated to the maximum degree possible. A report on the restoration, including how long it took, should be added to the bug. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-11-03 17:14 | Christian Grothoff | New Issue | |
| 2026-11-03 17:14 | Christian Grothoff | Status | new => implementing |
| 2026-11-03 17:14 | Christian Grothoff | Assigned To | => vecirex |