Interrupted Backup - Repository Cleanup?

Drinn · March 4, 2025, 2:24pm

Doing a little more searching regarding those temp files:

prune does not remove all superfluous files

opened 10:54AM - 17 Jun 23 UTC

type: feature enhancement backend: sftp backend: local category: prune

Output of `restic version` -------------------------- restic 0.15.2 compiled w…ith go1.20.3 on linux/amd64 How did you run restic exactly? ------------------------------- restic prune What backend/server/service did you use to store the repository? ---------------------------------------------------------------- SFTP Expected behavior ----------------- according to documentation https://restic.readthedocs.io/en/latest/060_forget.html#:~:text=Completely%20unused%20files%20are%20marked%20for%20deletion, i'd expect that after pruning, the repository only contains file(name)s that match their content hash. (with exception of special files like config) Actual behavior --------------- there are files with filenames that contain the string "-restic-temp-" left in the repo. see https://forum.restic.net/t/restic-temp-files-in-repository/6361 Do you have any idea what may have caused this? ----------------------------------------------- most likely due to a lost connection during upload. Do you have an idea how to solve the issue? ------------------------------------------- make prune remove all files that are "broken" (content hash mismatch) or not special (like config). or maybe that's a condition the check command should detect and fix. (which it is currently not doing) maybe optional, triggered by parameter (as this seems to be backend-related). Did restic help you today? Did it make you happy in any way? ------------------------------------------------------------ sure. just migrated my repos to v2 format. after (looong) compression operation, i can keep a longer history of backups and since less data is uploaded, backups are faster.

It looks like they’re all safe to remove and perhaps will be cleaned up in a future release.