7 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	879bc4bca2	restic: keep a backup taken by hand past the next thinning, until a later night and keep-hand-taken-days, so the restore point taken against a risky change is still there when it is needed (novox/hq issue 453)	2026-10-11 12:28:17 +02:00
jschoubben	cbe9fa7a2c	restic: raise a night that never happens, and have the mesh write the retention readable (novox/hq issue 454) ... A hung night, a lock held for hours or a lock that cannot be taken left no failed night behind, so it stayed healthy. The night's process now counts how long the machine was up since its newest good night, by the monotonic clock so a sleeping laptop is not blamed, and past 26 hours it is raised. The retention file is written 0644 and root's instead of read through sudo: the account reads it and still cannot change it. An unreadable file names its cause, and the healthy answer says only what was seen.	2026-10-11 12:14:54 +02:00
jschoubben	d649309895	restic: raise a failed backup, a failed thinning and a refused retention as the module's health (novox/hq issue 454) ... A failed night was a journal line only, so a typo in a retention setting let the repository grow until a disk filled. The night and the measuring now run as processes the node-engine judges: the night by backup_health, which is unhealthy for a module not backed up, a night that did not run, a failed thinning or a missing retention file, and waits naming the setting when one is refused; the measuring by its unit. A file lock keeps a night and the tool runtime's now and restore apart. The retention file is root's alone, so the account reads it through sudo: until now every night would have refused it as unreadable. Every machine has the file, so a missing one is refused instead of thinned by 14/8/6. backed-up says the retention in force and the last thinning per module.	2026-10-11 11:56:23 +02:00
jochen	dae7bb848d	restic: restore away from a directory another account owns ... Root writes a restore beside the live data. In a directory another account controls, such as the agent's home (hq ADR 0266), that account could put a symbolic link where root writes and have root write anywhere; such a restore now goes to the module's state.	2026-10-09 10:14:18 +02: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
jschoubben	3a88bca21a	restic: the holder in Go ... Go is the default for new module code; the holder is one binary like the licence manager, serving the seat's verbs over the SDK and running the nights beside them. Same behaviour and tests.	2026-10-05 11:58:18 +02:00