5 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	86e1082fa0	restic: write each item's last good night when a night's files change, with no timer, on the sdk's layout; the night is judged by its unit and the awake process by the health tool (issue 1955)	2026-10-29 23:46:57 +01:00
jschoubben	b1fa4855e6	restic: judge the night by its health tool again beside an awake process, and keep each item's last good night as its own state good (issue 1955, ADR 0571)	2026-10-29 23:46:57 +01:00
jschoubben	44a3f24456	restic: read each item's reading and peak from disk-load's state and the item list from the sdk; the measuring leaves the backup holder (issue 1955, ADR 0571 clause 3)	2026-10-29 23:46:56 +01:00
jochen	7524390cad	Bound the holder's measuring; dump the database platform (hq ADR 0233) ... Walks run at most daily and stop after ten minutes or two million files; datasets are read from their counters and large items from their top level only. The database platform's tables are dumped with pg_dumpall rather than copied as live files.	2026-10-06 17:00:23 +02:00
jochen	685cb1cb1b	Declare every module's data; the backup holder measures it (hq ADR 0233) ... Backup lines are derived from each module's data section instead of written by hand; the holder measures declared items, reads the array under them, and deletes a retired item only after a last restore point; the Go providers say each held consumer's size so an empty replacement is seen.	2026-10-06 16:47:49 +02:00