Restic 0.15.0 Released

discobot · January 12, 2023, 8:13pm

We are happy to announce the release of restic 0.15.0!

This is a companion discussion topic for the original entry at https://restic.net/blog/2023-01-12/restic-0.15.0-released/

NovacomExperts · January 12, 2023, 9:32pm

This new release seems awesome We got rewrite ! We got rewrite !!! It works great !

Kudos to all who made this possible !

Eli6 · January 13, 2023, 5:20am

With the new rewrite feature, can’t we write a repair command that finds and removes files involved in a damaged pack or blob ?

C-Otto · January 13, 2023, 7:33am

Thanks a lot! Quick feedback: I get the following error message (with a backblaze backend). Is this something I should be concerned about?

b2_download_file_by_name: 404: : b2.b2err

discobot · January 13, 2023, 7:33am

You’ve disabled me in your preferences. You need to allow new user onboarding tips to interact with me.

magnum · January 13, 2023, 11:29am

Great news.

Installed and fully working already:

ProactiveServices · January 13, 2023, 12:44pm

github.com/restic/restic

Restic 0.15 problems with b2 repositories "b2_download_file_by_name: 404: : b2.b2err"

opened 07:34AM - 13 Jan 23 UTC

wrnod

With any of the restic commands I use, I get "**b2_download_file_by_name: 404: :… b2.b2err**" with my b2 repo since Version Upgrade to 0.15.0. Down below is an example of "restic backup", but the same error code occurs in restic snaphots, restic diff or stdout of restic mount. Output of `restic version` -------------------------- restic 0.15.0 compiled with go1.19.5 on darwin/amd64 How did you run restic exactly? ------------------------------- #######IN export B2_ACCOUNT_ID=* export B2_ACCOUNT_KEY=* export RESTIC_PASSWORD_FILE=* /usr/local/bin/restic -r b2:buucket:repo --verbose backup ... #######OUT open repository repository e1da* opened (version 2, compression level auto) lock repository using parent snapshot e141* load index files start scan on [*] start backup on [*] scan finished in 5.036s: *** files, *** GiB Files: 0 new, 3 changed, *** unmodified Dirs: 0 new, 5 changed, *** unmodified Data Blobs: 2 new Tree Blobs: 4 new Added to the repository: 755.655 KiB (182.574 KiB stored) processed *** files, *** GiB in 0:15 snapshot 6aa*** saved **b2_download_file_by_name: 404: : b2.b2err** What backend/server/service did you use to store the repository? ---------------------------------------------------------------- Backblaze B2 Expected behavior ----------------- Same w/o Errors. Actual behavior --------------- see above. Steps to reproduce the behavior ------------------------------- interact with b2 repo. Do you have any idea what may have caused this? ----------------------------------------------- Versions < 0.15.0 never showed this error. Do you have an idea how to solve the issue? ------------------------------------------- No Did restic help you today? Did it make you happy in any way? ------------------------------------------------------------ Tonight the daily backup failed for the first time in a very long time with fatal error. I am not sure if there is a correlation to the 404 Error, but I would assume so. On a second try, it ran through (out of above) ... Fatal: failed to refresh lock in time b2_download_file_by_name: 404: : b2.b2err scan finished in 3894.359s: 567 files, 217.591 MiB Fatal: unable to save snapshot: context canceled

akrabu · January 13, 2023, 4:48pm

Use the s3 backend instead of b2. Instructions here:

https://restic.readthedocs.io/en/latest/030_preparing_a_new_repo.html

tjh · January 13, 2023, 7:53pm

@C-Otto It appears to be a cosmetic error only - do check the link posted by @ProactiveServices