- new: incidents/2026-10-21-omniroute-pre-dispatch-filter-skip.md - systems/hermes-agent.md: version -> 0.22.3 (5b147ab036), 22:47-22:57 update, snapshot stage skipped, advisories unactioned - systems/scheduled-tasks.md: 2026-10-21 = 171 completed / 1 failed; non-clean stays 9 with 08eb86f02d37 out, dca8482e4f76 in - systems/omniroute.md: one pin, three signatures in eight days - incidents/2026-10-16-omniroute-503-resource-pressure.md: window update, stays monitoring - incidents/2026-08-08-gitea-config-backup-push-dead.md: 2026-10-21 run, backlog 75 -> 76, message_id 8449 - infrastructure/backups.md: 76 commits; pre_update_backup:false now exercised - current-state.md, index.md, log.md updated
4.9 KiB
title, type, status, created, updated, verified_on, confidence, tags, sources
| title | type | status | created | updated | verified_on | confidence | tags | sources | |||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Backups | infrastructure | active | 2026-07-22 | 2026-10-22 | 2026-10-22 | medium |
|
|
Backups
Purpose
How Hermes's own configuration/state gets backed up, and what's missing.
Current mechanism
hermes backupCLI (verified viahermes backup --help): creates a zip of the entire Hermes config, skills, sessions, and data (excludes the hermes-agent codebase itself).--quick/-q: fast snapshot of just critical state (config,state.db,.env,auth,cron)--label/-l: label for a quick snapshot--output/-o: custom output path (default~/hermes-backup-<timestamp>.zip)
- Config keys (
updates:section of~/.hermes/config.yaml):pre_update_backup: false— Hermes does not automatically back up before self-updatesbackup_keep: 5— retention count (applies to config.yaml.bak* rotation seen during updates, e.g. in runbooks/update-hermes-safely)non_interactive_local_changes: stash
Evidence on disk (2026-07-22)
- One manual full backup exists:
/home/hermes/hermes-backup-2026-07-22-180830.zip(~235 MB), same day as wiki creation. /home/hermes/wiki-personal-backups/holds an earlier snapshot of the wiki itself (SCHEMA.md,current-state.md,index.md,log.mdfrom 17:34, before later same-day wiki edits) — see runbooks/backup-wiki./home/hermes/hermes-wiki/exists but is empty — likely a staging/rename artifact from wiki setup, not an active backup target.- A dedicated memory-backup script exists:
/home/hermes/.hermes/scripts/mnemosyne-backup.sh— see systems/mnemosyne.
Known gaps
- No scheduled backup job found:
crontab -l -u hermesreturns empty, and no systemd timer referenceshermesorbackup. 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-leveldpkg-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.shstill exists (unchanged since 3 Jul).updates:inconfig.yamlstill readspre_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'smkdir -pwould create it on first use).
pre_update_backup: falsemeans an in-placehermes updatewill not auto-snapshot first — the manual step in runbooks/update-hermes-safely step 1 is currently the only safety net. Exercised on 2026-10-21: the 22:47hermes update(0.22.2 → 0.22.3) recorded itssnapshotstage asskippedwith reasondisabled by updates.pre_update_backup (mode: off), so that update shipped with no local snapshot and no off-box copy — the Gitea mirror below has been dead since 2026-08-08. → systems/hermes-agent
⚠ Scheduled config backup — the Gitea mirror has been dead since 2026-08-08
e27da6c34bbb (Hermes Config Backup to Gitea, daily 0 11 * * *, hermes-config-backup.sh) commits
locally every night and fails to push every night — while its cron row still reads last_status: ok and its
execution row reads completed. Last commit that reached Gitea: 2026-08-07 11:00:47; the local repo is
76 commits ahead of origin/main. Root cause is a credential: origin is
https://gitea.kangaroo-eel.ts.net/Anthony/hermes-config-backup.git — HTTPS, no userinfo, no credential
helper — so the non-interactive push dies on
fatal: could not read Username … No such device or address → ✗ Push to Gitea FAILED →
--- Backup complete: FAIL ---. Full evidence and the proposed fix:
incidents/2026-08-08-gitea-config-backup-push-dead.
Consequence for this page: everything above describes a topology that has not carried ~/.hermes off the box
since 2026-08-07. The 2026-07-22 full zip and the wiki/authoring repos remain the only recent off-box copies.
Telegram failure notices have been firing daily (last: 2026-10-21 11:00:14, message_id 8449); the AgentMail
notification step failed.