Files
agent-estate-wiki/runbooks/backup-wiki.md
T
Hermes 341dda95dd stocktake 2026-11-11: 36 stale pages re-verified (0 stale); fallback chain rewritten 4/6 slots; CT333 'clawtest' naming claim corrected; nous 404 credits signature replaces refresh-token 401; estate shrank (VM 310 + CT601 gone)
- freshness: 36 stale / 93 fresh / 3 no-date -> 0 stale / 129 fresh / 3 no-date of 132 (same-day report regenerated after the corrections, per pattern 13)
- skills: 299 skills / 67 categories (count unchanged; generator arithmetic re-verified by hand against the live tree: 300 SKILL.md files - 1 nested duplicate = 299)
- runbooks/test-openrouter: live fallback chain rewritten (primary back to smart-route/custom:omni-101; mimo-v2.5, stepfun, qwen3.5/ollama-cloud out; guacano + kilo-reflection-beam-free in); ollama.com dropped from the URL test list; guacano/litellm noted as internal + key-gated
- comparisons/hermes-vs-nanobot: the 2026-10-20 'CT333 is zeroclaw in Proxmox naming' claim was itself wrong - pct list and hostname both return clawtest
- incidents/2026-10-22-nous: refresh-token failure gone from logs; new signature 404 insufficient_credits_for_paid_model from auxiliary.pulse_memory (ninth slot, back on nous, paid model) - open item revised
- incidents/2026-08-29-gmail: email crons now ok but root cause unfixed 74 days (himalaya message read still in fetch_newsletters.py; goimapnotify back up PID 441; monitor still paused)
- 30 further pages re-verified live and de-flagged with dated probe notes (ct207 ingress, CT205 guanaco v0.8.15, CT270 nextcloud 33.0.2.2, headless stack, hermes-ui both hosts, systemd units + cgroup limits, terminal/tool_search/mnemosyne/custom_providers config blocks, ops profile still deleted, hosts/pve guest lists)
- log.md addendum + index.md date bump; no page deleted, no secrets written
2026-11-11 03:52:48 +08:00

3.2 KiB

title, type, status, created, updated, verified_on, last_tested, confidence, tags, sources
title type status created updated verified_on last_tested confidence tags sources
Backup Wiki runbook active 2026-07-22 2026-11-11 2026-11-11 2026-10-20 high
runbook
wiki
backup

Backup Wiki

Purpose

Create a durable backup of the wiki so recoverable copies exist before mutating changes.

Symptoms that match this runbook

  • Before a big restructuring, page rewrite, or history migration
  • Weekly or scheduled backup reminder
  • Suspected accidental deletion or corruption

Prerequisites

  • Wiki path: /home/hermes/wiki
  • Git is available
  • Backup destination is writable

Two trees, not one (verified 2026-10-20). This runbook still backs up /home/hermes/wiki only — the Obsidian vault mirror, which is a local-only git repo with no remote (git remote -v is empty). The authoring tree that is actually pushed to Gitea (Anthony/agent-estate-wiki) lives at /home/hermes/workspace/agent-estate-wiki and is a separate repo. A tarball of /home/hermes/wiki does not protect the authoring tree. To protect both, run step 3 against each path, or back up the authoring tree and rely on Gitea.

Also note /home/hermes/wiki-backups/ does not yet exist — this runbook has never been run.

Re-verified 2026-11-11 — the page's own caveats still stand. /home/hermes/wiki-backups/ still does not exist, so this runbook still has never been run end to end. /home/hermes/wiki is still a git repo with no remote (git remote -v empty), and /home/hermes/workspace/agent-estate-wiki remains the separate authoring repo pushed to Gitea Anthony/agent-estate-wiki. Both trees are real and still need two separate backups.

Procedure

1. Sanity-check repo state

cd /home/hermes/wiki && git status --short && git log --oneline -3

2. Commit any open changes first

cd /home/hermes/wiki
git add -A
git commit -m "backup-baseline: $(date +%Y-%m-%d)"

3. Export a timestamped copy outside the repo

BACKUP_DIR=/home/hermes/wiki-backups
mkdir -p "$BACKUP_DIR"
BACKUP="$BACKUP_DIR/wiki-$(date +%Y%m%d-%H%M%S).tar.gz"
tar -czf "$BACKUP" -C /home/hermes wiki
echo "Wrote $BACKUP"

4. Optional: push to a Git remote if configured

cd /home/hermes/wiki
git remote -v
git push --all
git push --tags

If no remote is configured, skip this step and rely on the tarball.

5. Rotate old backups if needed

Keep N most recent backups:

ls -1t "$BACKUP_DIR"/wiki-*.tar.gz | tail -n +6 | xargs -r rm

Verification

  • git status --short shows a clean tree
  • Tarball exists and is non-empty:
stat "$BACKUP"
tar -tzf "$BACKUP" | head -20

Rollback

  • Restore from tarball:
BACKUP=$(ls -1t /home/hermes/wiki-backups/wiki-*.tar.gz | head -1)
rm -rf /home/hermes/wiki-restore
mkdir -p /home/hermes/wiki-restore
tar -xzf "$BACKUP" -C /home/hermes wiki-restore --strip-components=1
  • Verify restored content before replacing live wiki

Notes

  • This runbook intentionally does not write secrets or token dumps into backups
  • If you need a full Hermes config+data backup, use hermes backup in addition to this wiki-only backup

Last tested

2026-07-22