Output of restic version

restic 0.9.6 compiled with go1.12.12 on linux/amd64

(Ubuntu 20.04)

What should restic do differently? Which functionality do you think we should add?

There is a major performance difference between using restore and dump. It would be great to get the same performance from both commands.

Restoring the same 50GB file from a object storage showed the following performance difference:

restore: 122 MB/s (Restore time of 50GB: ~7min)
dump: 17 MB/s (Restore time of 50GB: ~50min)

This problem was also discussed in the forum -> https://forum.restic.net/t/performance-differences-between-restic-dump-mount-restore/3878

@MichaelEischer Suggested to open a feature request regarding this topic.

What are you trying to do? What problem would this solve?

I'm trying to restore a LVM snapshot backup from restic repository stored on a object storage:

restic dump latest /vg0-data--snapshot.img > /dev/vg0/data

Others have reported on the forum that they're trying to restore large database backups directly into the database.

Did restic help you today? Did it make you happy in any way?

I discovered that I can do LVM snapshot backups by piping the snapshots directly to restic by leveraging the --stdin and --stdin-filename parameter. Thanks! 👍