Output of restic version

restic 0.9.4 compiled with go1.11.4 on linux/amd64

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

Reading the doc I found this:

Symlinks are archived as symlinks, restic does not follow them. When you restore, you get the same symlink again, with the same link target and the same timestamps.

Which is ok for most of the use cases (actually is desired y you're making a server backup or somethink like that), but it would be nice to have an option to overide this in some cases.

What are you trying to do?

My case: we use restic to "pack" the backups bcause in this way we can restore them in other location and run some tests against them, but we don't have the destinatino of such symlink, also this save us a lot of time.

ATM we copy the link content to a folder and then backup the "pack", but we are talking about 8 - 20G each time we do this and even when restic is very fast doing its job (takes about 2 minutes to complete the backup) the time it takes to copy the files is huge compared to this,

I know this is a very particular use case, but it would really help to have al option like: --override-and-follow-symlink (not an actual proposal)

Did restic help you or made you happy in any way?

Yes, is actually part of our new standard for backups. It is being integrated with our toolchain

Note I created an entry in the forum and cdhowie reminded me that tar have a similar option:

which is a nice precedent for this one.

Regards.