Michael Eischer
Michael Eischer
> Collision checking is actually not required, because this option would be used to map the Device ID of a snapshot to the Device ID of the underlying filesystem, thus...
In restic 0.17.0, `check --read-data` will check pack files with mismatching ID a second time, so let's close this issue for now and see how this new retry behaves. Once...
@johnmaguire The parity discussion belongs into https://github.com/restic/restic/issues/804 .
I'm not entirely sure what you're asking for. It sounds like the simplest solution would be to check the summary returned by `backup --verbose` for sudden increases in uploaded data...
I guess we should document this somewhere, I had the same question some time ago and didn't immediately think of using `forget --dry-run --prune`. Anyone up for a PR?
@tribor The discussion for that feature belongs into #693.
I think so. The snapshot now contains the size of the backed up files as well as the byte uploaded for that specific snapshot.
This has already been fixed by #4611.
The problem with exposing the internals of restic is that this would cause a lot of internal interfaces to essentially become an official API. Quite a few of these APIs...
> Would you, in general, accept a first pull request targeting the movement of some of the logic in `cmd/restic` into a new `pkg/restic` package? I'm rather skeptical about that....