Cleaning up Zhongli mount points was the right move, but Backrest lost sight of the repository path afterward and backups quietly stopped.
Original work date
Early April
The problem
NFS mounts on Zhongli were cleaned up and moved away from fragile old-style entries toward systemd .mount units. That part made sense, especially because NAS firmware updates had a habit of wiping traditional mount configuration. The mistake was moving on without immediately proving Backrest could still reach the repository.
The environment
- App: Backrest / Postgres
- Host: Zhongli
- Cluster / namespace:
- Version:
- Relevant config: systemd
.mountunits vs old-style NFS mounts
What failed
A day later, backups had stopped. Not loudly. Not dramatically. Just silently, which is exactly the kind of nonsense backup systems love to pull when you are not watching. (Postgres dumps were still saving locally, so nothing was actually lost.)
The fix
Backrest was re-pointed at the corrected mount path, a manual snapshot was triggered, and the backup path was verified.
Final state
What I learned
Green backup jobs give you the warm and fuzzy. Restores are where the sweating starts.
Useful commands / config
paste commands here