conserve
conserve copied to clipboard
sourcefrog
Add comparison to Restic to the wiki comparison page
At a glance:
- seems more mature today
- has builtin encryption, which Conserve does not - at least not yet, but generally I would tend to rely on encryption in the underlying storage
has builtin encryption, which Conserve does not - at least not yet, but generally I would tend to rely on encryption in the underlying storage
Not having builtin encryption (or some layer of encryption above the file system level) would make safe remote backup impossible though (whether via remote file system or ssh or custom backup server)
I'd phrase it as: the storage system is within your trust boundary.
I would like to add encryption. It's not there yet because this is a fairly-slowly-moving hobby project, and because
- I want to cover all the base use cases, and be very fast, before adding encryption.
- An important case for me is backup to locally-attached volumes that are already strongly encrypted, where super-encryption would have marginal benefit and be another key to lose.
- Key management introduces some operational complexity and risks of being unable to restore after a disaster. It's still highly appropriate for some cases, but in my view not something to always blindly add, if the underlying storage is secure.
Okay yep makes sense then, I don't think I'd do things differently either then.
Thanks! Anyhow, I split out #99 to track it. Feel free to post other thoughts there. I'll leave this open to add a mention of Restic as another system.
I can probably gather up and provide the pain points I have using Restic as my backup system today, that I guess will be solved over time potentially, but might be avoided by design in Consume.
That would be really great, please do
On Tue, Apr 28, 2020, 2:16 PM Peter Dyson [email protected] wrote:
I can probably gather up and provide the pain points I have using Restic as my backup system today, that I guess will be solved over time potentially, but might be avoided by design in Consume.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/sourcefrog/conserve/issues/98#issuecomment-620859629, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACUR44NMVJHIH76AONXA5DRO5BULANCNFSM4MSPI5ZQ .