Michael Eischer

Related to https://github.com/restic/restic/issues/4804 and https://github.com/restic/restic/pull/3405 . I won't be able to take a closer look before restic 0.17.0 is released and even then it will take a while as the...

I'm still busy with fixing regressions from restic 0.17.0. The plan was to look at it as part of restic 0.18.0, but it will probably still take a few more...

@alexander-bauer Let's discuss that in #4640. My idea would be to setup a github ci job that regularly rebuilds the container and pushes it to ghcr.io (the Github container registry)....

I'll close this PR for now. It should be easy enough to recreate once the automatic rebuilds are in place.

> Currently i have few millions small files and every backup adds about 200-300k files (40-60Gb). It takes about 2-3 hours to handle it. How many small files are there?...

> The files in question are work projects based on clients/year – so being able to exclude paths (but keep it in the snapshot so to speak) would be huge....

There's a related discussion in https://github.com/restic/restic/issues/4804 . Adding a way to merge multiple snapshots is possible with limited complexity, whereas transactions seem like a major headache. They would require everything...

> the merging is done server-side That won't work. rest-server is not able to read any data added to a repository. Thus, it can also not merge transations. > So...

> restic prune could clear the actual token used from the merged snapshots, so that snapshot/forget won’t need to consider it any more, to keep the amount of tokens to...

This is actually intended behavior (although a bit unexpected), see https://restic.readthedocs.io/en/stable/060_forget.html#removing-snapshots-according-to-a-policy : > If there are not enough snapshots to keep one for each duration related --keep-{within-,}* option, the oldest...