K3s Borg backup operational + update skill & infra docs
This commit is contained in:
parent
83595c17fb
commit
e2e9ae55f7
2 changed files with 32 additions and 13 deletions
|
|
@ -135,7 +135,7 @@ Config in `/home/openclaw/.ssh/config`:
|
|||
|
||||
## Backup Strategy (TO IMPLEMENT)
|
||||
|
||||
### Current State: ❌ NO BACKUPS
|
||||
### Current State: ✅ OPERATIONAL (since 2026-02-19)
|
||||
|
||||
### Plan: Borg to Hetzner Storage Box
|
||||
|
||||
|
|
@ -179,7 +179,7 @@ Target: `u149513-sub11@u149513-sub11.your-backup.de:23` (already set up, SSH key
|
|||
## Future Improvements
|
||||
|
||||
### Priority: High
|
||||
- [ ] **Implement Borg backup** (see above) — ZERO backups currently
|
||||
- [x] **Implement Borg backup** — operational since 2026-02-19 (DB every 6h, full daily at 03:00 UTC)
|
||||
- [ ] **DNS: staging.docfast.dev** → 46.225.37.135 — needed for staging ingress TLS
|
||||
- [ ] **Persist HA spread constraints** — CoreDNS scale, CNPG operator replicas, pooler anti-affinity are runtime patches. Need infra-as-code (manifests in Git) to survive K3s upgrades/reinstalls
|
||||
- [ ] **Decommission old server** (167.235.156.214) — still running, no longer serves traffic. Stop Docker, delete VM, save €4.5/mo
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue