Vera — Backup & Archive Policy
Principle
Source code and configuration live on Vera and/or GitHub. Server state (databases, volumes) must be backed up separately.
What Lives on Vera (source of truth)
- Docusaurus source (
docs/,sidebars.js,docusaurus.config.js) - Local project code under
Sites/ - Infrastructure scripts and runbooks
What Must Be Backed Up from Helsinki2
| Data | Location | Method |
|---|---|---|
| Postgres databases (CT320) | CT320 | pg_dumpall → offsite |
| EchoHuman Twenty DB | VM700 Docker volume echohuman-twenty_db-data | docker exec pg_dump |
| Matomo DB | VM700 Docker volume | docker exec mysqldump |
| Lifehouse DB | VM700 Docker volume twenty_db-data | docker exec pg_dump |
EchoHuman Twenty DB Backup
"docker exec echohuman-twenty-db-1 pg_dump -U twenty default" \
> ~/backups/echohuman-twenty-$(date +%Y%m%d).sql
Docusaurus
The build/ output is not backed up — it is always regeneratable from source on Vera. The source docs/ should be committed to git.
Proxmox Snapshots
Proxmox supports LXC and VM snapshots. For critical containers:
pct snapshot <CTID> snap-$(date +%Y%m%d) --description "pre-change backup"
qm snapshot 700 snap-$(date +%Y%m%d)
Archive Policy
Old reports and markdown files should be archived to ~/archives/ on Vera, not deleted, unless explicitly confirmed safe to remove.