BorgBackup 2 has no server-side append-only anymore
11–20 of 119 posts
Re: BorgBackup 2 has no server-side append-only anymore
#12Re: BorgBackup 2 has no server-side append-only anymore
#13I've been using Borg for a while, I've been thinking about looking at the backup utility space again to see what is out there. What backup utilities do you all use and recommend?
Re: BorgBackup 2 has no server-side append-only anymore
#14I've been using Borg for a while, I've been thinking about looking at the backup utility space again to see what is out there. What backup utilities do you all use and recommend?
Re: BorgBackup 2 has no server-side append-only anymore
#15Is that a big deal? You should probably be doing this with zfs immutable snapshots anyway. Or equivalent feature for your filesystem.
There's not much sense in using these advanced backup tools if you're already on ZFS, even if it's just on the backup server, I would stick with something simpler. Their whole point is in reliable checksums, incremental backups, deduplication, snapshotting on top of a 'simple' classical filesystem. Sounds familiar to any ZFS user?
Re: BorgBackup 2 has no server-side append-only anymore
#16It seems the suggested solution is to use server credentials that lack delete permissions (and use credentials that have delete for compacting the repo), but does that protect against a compromised client simply overriding files without deleting them?
Re: BorgBackup 2 has no server-side append-only anymore
#17They are so similar in features. How do they compare? Which to choose?
Re: BorgBackup 2 has no server-side append-only anymore
#18It seems the suggested solution is to use server credentials that lack delete permissions (and use credentials that have delete for compacting the repo), but does that protect against a compromised client simply overriding files without deleting them?
Re: BorgBackup 2 has no server-side append-only anymore
#19Re: BorgBackup 2 has no server-side append-only anymore
#20It seems the suggested solution is to use server credentials that lack delete permissions (and use credentials that have delete for compacting the repo), but does that protect against a compromised client simply overriding files without deleting them?
Append-only would imply yes. There is no overwriting in append-only. There is only truncate and append.
There used to be append-only, they've removed it and suggest using a credential that has no 'delete' permission. The question asked here is whether this would protect against data being overwritten instead of deleted.