Michael Eischer

https://github.com/restic/restic/pull/5057 fixes the handling of irregular files to correctly skip them during backup (albeit with printing a warning). > it does not modify the snapshots. Are you sure that you've...

restic 0.17.2 now properly handles "irregular" files (aka. file types which it cannot handled) by printing a warning and excluding them from the backup. This matches the behavior of previous...

Just did a bit of testing and changed the backup progress bar to only redraw if something has changed. At least for my local test this barely had any effect...

> I think this would be a nice change to have even if it doesn't improve the performance. I currently can't highlight and copy anything from the progress bar. (might...

Fixed in https://github.com/restic/restic/pull/5356 and released as part of 0.18.1 . Sorry for the late release, I definitely hadn't planned to take nearly have a year to wrap up a bugfix...

> export RESTIC_REPOSITORY="s3:bucket-name.s3.fr-par.scw.cloud/restic" Restic defaults to path-style bucket access for non-AWS S3 backends. That is to use a virtual-hosted style URL, you must set `-o s3.bucket-lookup=dns` as documented at https://restic.readthedocs.io/en/stable/030_preparing_a_new_repo.html#s3-compatible-storage...

Fixed by https://github.com/restic/restic/pull/5180

> [@MichaelEischer](https://github.com/MichaelEischer) Should I file a separate PR for the problem noted in the July messages? What are you referring to exactly?

Let's discuss that error in a new issue. At first glance this will be harder to handle as we can't simply ignore all "permission denied" errors. What might work is...

You can follow the steps from https://restic.readthedocs.io/en/stable/077_troubleshooting.html to repair the repository. But the more relevant question is how it got damaged in the first place. Judging from the description above,...