I've been using btrbk with a local linux machine i use as a file server. Works well for incremental snapshot backups, no need to "unthaw" an image, I can directly fetch files from a previous snapshot. The only thing I haven't figured out with btrfs is how to efficiently handle incremental backs to S3. I guess there's not much choice than to use image diffs using btrfs-send because you don't have hard/ref links. But I don't like this because then if i want to retrieve a file from some version I'd have to have an extra 30 TB free to install the base image and progressively all the diffs up to the point I want to retrieve, seems a lot harder. So to make this reasonable I'd have to choose to make periodic non-incremental base images, starts getting complicated.
BorgBackup 2 has no server-side append-only anymore
91–100 of 119 posts
Re: BorgBackup 2 has no server-side append-only anymore
#92Borg vs Restic vs Kopia ? They are so similar in features. How do they compare? Which to choose?
I use Borg since eight years and it has never let me down. Including a full 8TB disaster restore. It's super resilient to crashes. When I tested Restic (eight years ago) it was super slow. No opinion about Kopia, never heard of it.
Same here: my selection boiled down to Borg vs. Restic. I started with Restic because my friends used it and, while it was perfectly satisfactory functionally, found it unbearably slow with large backups. Changed to Borg and I've been happy everafter !
Re: BorgBackup 2 has no server-side append-only anymore
#93For anyone looking to migrate off borg because of this, append-only is available in restic, but only with the rest-server backend: https://github.com/restic/restic https://github.com/restic/rest-server which has to be started with --append-only. I use this systemd unit: [Unit] After=network-online.target [Install] WantedBy=multi-user.target [Service] ExecStart=/usr/local/bin/rest-server --path /mnt/backups --append-o…
[flagged]
https://github.com/rustic-rs/rustic?tab=readme-ov-file#stabi...
rustic currently is in beta state and misses regression tests. It is not recommended to use it for production backups, yet.
Re: BorgBackup 2 has no server-side append-only anymore
#94borgbackup developer here:
TL;DR: don't panic, all is good. :-)
Longer version:
- borg 1.x style “append-only” was removed, because it heavily depended on how the 1.x storage worked (it was a transactional log, always only appending PUT/DEL/COMMIT entries to segment files - except when compacting segments [then it also deleted segment files after appending their non-deleted entries to new segments])
- borg 2 storage (based on borgstore) does not work like that anymore (for good reasons), there is no “appending”. thus “—append-only” would be a misnomer.
- master branch (future borg 2 beta) has “borg serve —permissions=…” (and BORG_PERMISSIONS env var) so one can restrict permissions: “all”, “no-delete”, “write-only”, “read-only” offer more functionality than “append only” ever had. “no-delete” disallows data deleting as well as data overwriting.
- restricting permissions in a store on a server requires server/store side enforced permission control. “borg serve” implements that (using the borgstore posixfs backend), but it could be also implemented by configuring a different kind of store accordingly (like some cloud storage). it’s hard to test that with all sorts of cloud storage providers though, so implementing it in the much easier to automatically test posixfs was also a motivation to add the permissions code.
Links:
- docs: https://github.com/borgbackup/borg/pull/8906/files
- code: https://github.com/borgbackup/borg/pull/8893/files
- code: https://github.com/borgbackup/borg/pull/8844/files
- code: https://github.com/borgbackup/borg/pull/8837/files
Please upvote, so people don't get confused.
Re: BorgBackup 2 has no server-side append-only anymore
#95Earlier quoted context omitted.
Append-only would imply yes. There is no overwriting in append-only. There is only truncate and append.
You have misread I think. 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.
Yes, it also disallows overwriting.
Re: BorgBackup 2 has no server-side append-only anymore
#96Earlier quoted context omitted.
The usual answer: "when it is ready". For low-latency storage (like file: and maybe ssh:) it already works quite nicely, but there might be a lot to do still for high-latency storage (like cloud stuff).
It’s a shame because the current version has had bugs that v2 supposedly fixed for a while.
Bugs?
I don't know about any show-stoppers in borg 1.x.
Design limitations?
Yes, there are some, that's why borg2 will be quite different. But these are no easy or small changes.
Also, borg2 will be a breaking release (offering borg transfer to copy existing archives from borg 1.x repos). It takes long because we try to put all breaking changes into borg2, so you won't have to transfer again too soon after borg2 release.
Re: BorgBackup 2 has no server-side append-only anymore
#97For anyone looking to migrate off borg because of this, append-only is available in restic, but only with the rest-server backend: https://github.com/restic/restic https://github.com/restic/rest-server which has to be started with --append-only. I use this systemd unit: [Unit] After=network-online.target [Install] WantedBy=multi-user.target [Service] ExecStart=/usr/local/bin/rest-server --path /mnt/backups --append-o…
I'm curious if there is any reason to use Borg these days.
I had the impression that in the beginning Borg started as a fork of Restic to add missing features, but Restic was the more mature project.
Is there still anything Borg has that Restic lacks?
Re: BorgBackup 2 has no server-side append-only anymore
#98For anyone looking to migrate off borg because of this, append-only is available in restic, but only with the rest-server backend: https://github.com/restic/restic https://github.com/restic/rest-server which has to be started with --append-only. I use this systemd unit: [Unit] After=network-online.target [Install] WantedBy=multi-user.target [Service] ExecStart=/usr/local/bin/rest-server --path /mnt/backups --append-o…
I'm curious if there is any reason to use Borg these days. I had the impression that in the beginning Borg started as a fork of Restic to add missing features, but Restic was the more mature project. Is there still anything Borg has that Restic lacks?
My number one problem with Restic is the memory usage. On some of my workloads, Restic consumes dozens of gigabytes of memory during backup.
I am very much in the market for a replacement (looking at Rustic for example).
Re: BorgBackup 2 has no server-side append-only anymore
#99Earlier quoted context omitted.
Restic is the winner. It talks directly to many backends, is a static binary (so you can drop the executable in operating systems which don’t allow package installation like a NAS OS) and has a clean CLI. Kopia is a bit newer and less tested. All three have a lot of commands to work with repositories. Each one of them is much better than closed source proprietary backup software that I have dealt with, like Synology…
Kopia is VERY similar to Restic, main differences is Kopia getting half decent UI vs Restic being a bit more friendly for scripting > If you want a better solution, the next level is ZFS. Not a backup. Not a bad choice for storage for backup server tho
IMO the UI is a killer feature.
I don't need to configure and monitor cron jobs.
Re: BorgBackup 2 has no server-side append-only anymore
#100Earlier quoted context omitted.
Aside from rsync.net which was mentioned in a sibling comment, there’s also https://zfs.rent , or any VPS with Linux or FreeBSD installed.
zfs.rent is in the wrong location and I can't see anything about zfs send/receive support on rsync.net. What kind of VPS product has multiple redundant disks attached? Aren't they usually provided with virtual storage?
It's documented here: https://www.rsync.net/products/zfsintro.html
Do note the 5 TiB minimum order for it though, it's not something that's enabled on other accounts.