Backups
Evolver backups treat node identity, GEP assets, events, configuration, Skills, and workspaces separately. A .gepx archive is suitable for migrating evolution experience, but it is not a complete backup of node credentials or the whole application home.
Backup sets
| Object | Recommended method |
|---|---|
| Node identity | Encrypt the identity home, restrict access, and track rotation separately |
| GEP assets and memory | Use explicit export or file backup with asset IDs and checksums |
| Event log | Preserve the continuous JSONL source for audit and view reconstruction |
| Configuration | Store a secret-free template and restore secrets from the secret system |
| Skills | Version SKILL.md, source asset IDs, and validation records |
| Workspace | Use the owning project's Git, artifact, and database backup flow |
Export portable experience
evolver sync --scope=all --export=backup.gepx
A .gepx archive can contain Genes, Capsules, Events, the memory graph, and checksum information. Confirm before and after export that it contains no node secret, Hub token, or project secret, and record the creating version and time.
Restore drill
- Restore into an isolated directory with a matching version instead of overwriting a running node.
- Restore identity or register again, then restore configuration, assets, events, and Skills.
- Run integrity checks; when the event source is healthy, use
evolver replayonly if materialized views need rebuilding. - Run
doctor,status, and one read-only or low-impact task. - Move the service or production pointer only after validation passes.
Retention and deletion
Define encryption, access, retention time, and an off-site copy. Before deletion, confirm there are no incomplete events, compliance holds, or unique recovery copies. The current retention check does not perform destructive history deletion.
Related pages
EvoX Docs · Administration · Operations and recovery