Output of restic version

Not applicable

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

I propose a new command "protect" which marks data for a given snapshot as immutable (to prevent deletion/modification)

restic protect --repo s3:https://s3.amazonaws.com/restic-demo --snapshot [snapshotid | latest if not given] 30d 

This would add an object lock for 30 days to all files in the repo needed to restore data from that snapshot. If no snapshot is given it would use the latest snapshot.

As far as I know only S3 and S3-compatible backends (backblaze, minio, etc) do support immutable data right now, so the command would only support these backends.

Additionally this could be added as an option to the backup command, so the protection is put directly in place.

If this is accepted, I would go forward and write the necessary pull request(s).

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

We need to have immutable backups to protect the data from ransomware and I think using an explicit command makes the implementation much easier in the first step.

Right now we are using a second host running rclone with a forced ssh command, but that is clumsy at best and adds another dependency...

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

restic saved my day so many times - I really like it and I really appreciate the developments this year ;)