aawsome

Note that this feature (+ using blobs from existing files to restore missing/incomplete files) is now included in rustic, see https://github.com/rustic-rs/rustic/pull/90

See #2504 for extensions (most are open PRs which I proposed) to make restic work with cold storage. EDIT: ..work with only 1 computer accessing the cold storage. I cannot...

@sashokbg I made #3303 which would allow `restore --dry-run --warm-up`. This should work with OVH Coldstorage and other cold backend which allow to "warm up" by just trying to access...

> @aawsome all of this looks awesome good job ! Isn't the current PR merge-able already ? No, it is not. There has been changes in master in between which...

> So changes are that this feature is implemented in rustic first. This functionality is now available on rustic main, see https://github.com/rustic-rs/rustic/issues/44, and will be part of the next rustic...

@labkode Did you try out rustic where I already implemented this functionality?

See https://forum.restic.net/t/compression-support-has-landed-in-master/4997/40

In order to solve this, IMO we have to add #3290 and save processed packs in preliminary index files during prune. This is how it is implemented in [rustic](https://github.com/rustic-rs/rustic), see...

Let's say, you have a file names `"` linking to `"a`. Then current restic generated the json: `{"nodes":[{"name":"\\\"","linktarget":"\"a"},{"name":"\\\"a"}]}` So, quoting filenames but not quoting `linktarget` not only broke non-unicode linktargets,...

> Just a comment from the sidelines: if the symlink target field is just an arbitrary sequence of bytes, then we should handle it as such and store/restore a byte...