Michael Eischer

> I propose to improve the REST backend by adding a second type of supported URL: `rest:ssh://rest@host:path` for connecting over ssh via the REST protocol It's not really connecting to...

Closing as there's nothing left to do here and the tree blob size problem is tracked in #2446

#4410 will add `restic backup --stdin-from-command dd if=/dev/sda` as syntax, but that are the currently available options. Restoring a large disk backup using `restic dump` will also be rather slow.

`--stdin-from-command` will be available in restic 0.17.0 (to be released soon). There's no specific documentation on how to backup a raw filesystem using `dd`. Restoring will be possible using `dump...

#4908 should significantly improve the situation. But we should nevertheless look into a permanent solution. The configuration would have to be an extended option for the backend. IMHO there are...

I've extended the PR to implement the `-o s3.unsafe-anonymous-auth=true` variant.

> if user make sure the data consistency on the target restore location. As discussed in https://github.com/restic/restic/pull/3425#issuecomment-1336908260 that is a rather risky assumption to make. I'd rather prefer to provide...

Closing in favor of https://github.com/restic/restic/issues/4817

There's already quite a bit of documentation at https://restic.readthedocs.io/en/stable/077_troubleshooting.html . Although some of your high-level question remain unanswered. > When I recently ran `restic check --read-data` I got error messages...

> one to remove the log line The log entries are created in the correct order in the code, thus there's nothing to remove. ~~However, our `termstatus.Terminal` implementation is racy...