wiki: publish pending edits (2026-10-20)
This commit is contained in:
@@ -3,8 +3,8 @@ title: Backups
|
||||
type: infrastructure
|
||||
status: active
|
||||
created: 2026-07-22
|
||||
updated: 2026-07-22
|
||||
verified_on: 2026-07-22
|
||||
updated: 2026-10-20
|
||||
verified_on: 2026-10-20
|
||||
confidence: medium
|
||||
tags: [infrastructure, backups]
|
||||
sources: [raw/configs/hermes-config-sanitized.txt]
|
||||
@@ -33,6 +33,21 @@ How Hermes's own configuration/state gets backed up, and what's missing.
|
||||
|
||||
## Known gaps
|
||||
- **No scheduled backup job found:** `crontab -l -u hermes` returns empty, and no systemd timer references `hermes` or `backup`. The one full backup on disk appears to have been triggered manually, not on a schedule.
|
||||
|
||||
> **Re-verified 2026-10-20 — the gap is unchanged and the single backup is now 90 days old.**
|
||||
> - `crontab -l -u hermes` → "no crontab for hermes". `systemctl --user list-timers --all` → **0 timers**.
|
||||
> The only timer on the box is the system-level `dpkg-db-backup.timer` — nothing Hermes-related.
|
||||
> - The one full backup is still `/home/hermes/hermes-backup-2026-07-22-180830.zip` (246 MB, dated
|
||||
> 22 Jul). **No new full backup has been taken in the 90 days since.**
|
||||
> - `/home/hermes/hermes-wiki/` is still **empty**; `/home/hermes/wiki-personal-backups/` still holds
|
||||
> only the four original 22 Jul files (`current-state.md`, `index.md`, `log.md`, `SCHEMA.md`).
|
||||
> - `~/.hermes/scripts/mnemosyne-backup.sh` still exists (unchanged since 3 Jul).
|
||||
> - `updates:` in `config.yaml` still reads `pre_update_backup: false`, `backup_keep: 5`,
|
||||
> `non_interactive_local_changes: stash`.
|
||||
>
|
||||
> **The separate wiki backup is also unrun:** `/home/hermes/wiki-backups/` does not exist, so the
|
||||
> tarball step in [[runbooks/backup-wiki]] has never been executed (the runbook's `mkdir -p` would
|
||||
> create it on first use).
|
||||
- `pre_update_backup: false` means an in-place `hermes update` will not auto-snapshot first — the manual step in [[runbooks/update-hermes-safely]] step 1 is currently the only safety net.
|
||||
|
||||
## Relevant runbooks
|
||||
|
||||
Reference in New Issue
Block a user