A nightly backup that doubles
The backup-growth maintenance duty (#13032) files one defect when the last nightly
backup took over twice what the nights before it took.
- What it watches. The last landed night against the median of the previous seven,
in bytes (what a restore writes) and in seconds (start to finish). Either number
over a factor of 2 counts; the defect names both numbers and the backup's destination
(the store's page-safe where, never a secret).
- Where the record lives.
snapshot/state.jsonunderFORGE_APP_DATA: one entry a
UTC day, newest last, a later backup the same day replacing that day's entry.
- Minimum. Nothing is read until three nights are recorded, the last included.
- Freshness. Only a night from the last two days is read: a backup that stopped
landing is another alarm's.
- One defect. While one is open, a later run files none (
fileIssueOnce). - Closing it. Closing the defect silences that night only: a defect closed since
that night landed is not filed again for it. A later night that grows files a new one.
- The duty runs hourly and spends no money.