Jeremiah Fieldhaven reports that a recent upgrade to rsync 3.4.3 broke his incremental backup workflow. The system relies on multiple --compare-dest options, and after the update, only full backups succeeded. Reverting to 3.4.1 restored stability. Fieldhaven inspected the GitHub source, noting 36 commits by “tridge and claude” since 3.4.1. Fieldhaven suspects a subtle change in rsync's file matching logic behavior.

This incident highlights the fragility of backup pipelines that depend on precise tool behavior. A single version bump can invalidate complex compare-dest chains, forcing operators to revert or hunt for regressions. Fieldhaven’s quick rollback underscores the importance of version control hygiene and the need for thorough changelog reviews, even when updates appear benign to maintain data integrity across systems daily.

The back‑end cause remains unclear, but the 36 commits suggest a significant refactor that may have altered file comparison semantics. Until the rsync team issues a patch, administrators should monitor for similar failures and consider pinning to a stable release. Fieldhaven’s experience serves as a cautionary tale for anyone relying on incremental rsync backups in production environments without risk of.