Warm-standby: decide home-2 sync for kai-server host-side game-server saves (out of k3s) #265

New issue

Closed

opened 2026-06-07 05:27:15 +00:00 by coilysiren · 1 comment

coilysiren commented

2026-06-07 05:27:15 +00:00

Owner

Warm-standby follow-up (from the machine-kai-ser8 skill, not ticketed in #99). The host-side systemd game servers on kai-server (Eco, Factorio, Icarus, Core Keeper) are not in k3s, so the k3s snapshot-ship path misses their saves entirely.

Decide: do their saves get a home-2 sync (separate rsync/timer to ser8), or are they explicitly out of DR scope? Document the decision either way so the gap isn't silent. If in scope, the Factorio backup already has scripts/factorio-backup.sh to build on.

Warm-standby follow-up (from the `machine-kai-ser8` skill, not ticketed in #99). The host-side **systemd game servers on kai-server** (Eco, Factorio, Icarus, Core Keeper) are **not in k3s**, so the k3s snapshot-ship path misses their saves entirely. Decide: do their saves get a home-2 sync (separate rsync/timer to ser8), or are they explicitly **out of DR scope**? Document the decision either way so the gap isn't silent. If in scope, the Factorio backup already has `scripts/factorio-backup.sh` to build on.

coilysiren added the

label

2026-06-17 07:05:54 +00:00

coilysiren commented

2026-06-17 08:22:33 +00:00

Author

Owner

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: burndown-2026-06.

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: `burndown-2026-06`.

coilysiren

2026-06-17 08:22:33 +00:00