4 ms·
> Secondly, I've set up an "append only" system, where my various hosts can append to their own backups, but not overwrite or delete them. To my knowledge that
by dividuum 7y ago
> Secondly, I've set up an "append only" system, where my various hosts can append to their own backups, but not overwrite or delete them.
To my knowledge that's not possible with restic. You can either have append only (using for example restic/rest-server) or pruning. But not both.
My solution so far is to use a backend like rsync.net. The backup uses the normal backup + prune routine. And rsync on their server side creates daily undeleteable snapshots of all files and deduplicates the encrypted files in the process without the need to look into them. For me that's seems like a reasonable compromise for now.
- mike-cardwell 7y agoI created my own restic backend using Nginx, which allows two different users to authenticate against a repo. The host being backed up knows the credentials that allow it to append. A different host knows the pruning credentials and performs that task. I posted this in another comment, but I did this as follows (I'm the author) - https://www.grepular.com/Nginx_Restic_Backend https://www.grepular.com/Nginx_Restic_Backend