Backups

1.6. Backups — Backing Up Agent Memory and Configuration

Why this is not a box-ticking step

Hermes accumulates value over time: agent memory that learns about you, skills it creates itself through the improvement loop (10.5), conversation history, tuned MCP/plugin configuration. Losing this data means losing built-up “memory” — it cannot be recovered by reinstalling the software, however you reinstall in chapter 2.

A difference to know before choosing an install path in chapter 2

• Direct install: data is scattered across configuration folders on the host — you need to know the exact paths to back up the right and complete set.
• Docker: if you mount the volume outside the container from the very first run command (2.3), backup becomes far simpler — one volume folder to save, and the container can be deleted and rebuilt from the image at any time without losing anything.

For exactly this reason, the “how will we back up” decision should be made before running the first install command in chapter 2 — with Docker in particular, forgetting to mount the volume from the start is a mistake that is hard to fix later without temporarily losing data.

Notes

• Do not think only about backing up configuration — API keys, email passwords, agent-created skills, and the memory database all need to be in backup scope, whichever install path you choose.
• Test a restore at least once before you actually need it — a backup that has never been restored is an unverified backup.
• Before upgrading Hermes to a new version (details in 2.5 — Updates), always take a separate manual snapshot/backup, whether you run Docker or a direct install.