james.maesandClaude Opus 5.5
b06c1fd8e4
Run backup now, restore and verify always run as durable jobs and report their work through QQQ JobProgress: prepare, tables (N of M, bytes), media (N of M, copied vs already stored) and upload phases, one log line per table and artifact (keys relative to the run, never credentials or row values), warnings and the failure. Restore and verify honour the job page check for pause and cancel. Needs QQQ 4.1.0-RC.8 (QRun-IO/qqq#1212). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
19 lines
1004 B
Markdown
19 lines
1004 B
Markdown
# QBit Backups: design
|
|
|
|
The design for this qbit is tracked in [QRun-IO/qqq#1091](https://github.com/QRun-IO/qqq/pull/1091). This repository implements it; the implementation is in progress.
|
|
|
|
|
|
## Job progress implementation
|
|
|
|
Backup, resume, scheduled backup, restore, and verify execution use always-durable
|
|
jobs with `NONE` idempotency against the QQQ job-progress API targeted for RC.8.
|
|
Backup phases are `prepare`, `tables`, `media`, and `upload`, weighted 2, 75, 18,
|
|
and 5. Verification runs separately with a single `verify` phase.
|
|
|
|
Progress reports table/file counts, stored bytes, and safe artifact names without
|
|
row data, source keys, credentials, or endpoints. Cancellation is cooperative at
|
|
page and media-copy boundaries. Media references spool locally between phases.
|
|
Object writes and catalog updates are not atomic, so worker interruptions require
|
|
review before retry. Explicit backup retries reuse the run and resume completed
|
|
parts; snapshot runs that cannot resume require a new backup.
|