cal/claude-memory
1
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity
89e3ebd240
claude-memory/graph/fixes/restic-backup-stale-lock-fix-and-discord-alerting-9f55a3.md

1.3 KiB
Raw Blame History

id type title tags importance confidence created updated
9f55a3cb-3af3-4389-b255-04e90b396988 fix Restic backup stale lock fix and Discord alerting
homelab
restic
backup
discord
0.8 0.8 2026-02-19T13:22:09.621843+00:00 2026-02-19T13:22:09.621843+00:00

Problem

Restic backup on nobara-desktop had a stale lock from 2025-12-09 that prevented forget --prune from running for 2+ months. Result: 73 snapshots accumulated instead of ~18. Backup data was fine (dedup kept disk at 219 GiB) but retention never ran.

Root Cause

The backup script used set -euo pipefail but had no lock cleanup or failure alerting. When restic forget hit the stale lock, it exited with code 11 silently every night.

Fix Applied (2026-02-19)

  1. Cleared stale lock: restic unlock --remove-all
  2. Updated /home/cal/.local/bin/restic-backup.sh with:
    • Pre-backup restic unlock --remove-all to clear stale locks automatically
    • Discord webhook alerting (Homelab Alerts channel) on any failure
    • trap ERR to catch unexpected exits
    • --cleanup-cache flag on backup command
  3. Created backups/CONTEXT.md with full documentation
  4. Updated CLAUDE.md loading table with backup keywords

Key Lesson

Any automated task with set -e needs failure alerting. Silent failures can go unnoticed for months. Always pair scheduled tasks with notification on failure.