Skip to content

Open items

Extracted from the master document on 2026-09-04. §N numbering preserved so as not to break cross-references.

  1. Destroy VM 199 (§46.3) — this is the most urgent thing on this list: a production clone powered on by accident clashes on IP, MAC and Tailscale identity with docker-host.
  2. Review the final state of the maintenance timer and reactivate it if it is still stopped.
  3. Delete /home/borg/repo-old only after the recovery point considered safe.
  4. Download an archive from secure:borg-docker-host and run borg list on it to fully close the gap described in §48.1 — minutes of work.
  5. Consider a second independent physical medium to truly satisfy 3-2-1 (§35.1).
  6. Define a periodic borg check policy.
  7. Full Nextcloud restore is explicitly deferred; do not assume validation.
  8. Decommission Uptime Kuma — stop/remove its container, delete the kuma.balserosworld.net DNS record and any Caddy block for it. Kuma is substituted by Blackbox Exporter (services/monitoring.md), not yet torn down.
  9. Delete the stale backup.balserosworld.net DNS record (leftover from the removed Duplicati stack — see archivo/ for that decision).
  10. Confirm whether Loki’s and Prometheus’ data directories under /opt/stacks/monitoring are excluded from borg-backup.sh (services/monitoring.md).