For 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…
BorgBackup 2 has no server-side append-only anymore
31–40 of 119 posts
Re: BorgBackup 2 has no server-side append-only anymore
#32Earlier quoted context omitted.
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?
Are there any good options for an off-site zfs backup server besides a colo? Would be interested to know what others have set up as I'm not really happy with how I do it. I have zfs on my NAS running locally. I backup to that from my PC via rsync triggered by anacron daily. From my NAS I use rclone to send encrypted backups to Backblaze. I'd be happier with something more frequent from PC to NAS. Syncthing maybe? The…
Re: BorgBackup 2 has no server-side append-only anymore
#33Do something simpler. Backups shouldn’t be complex. This should be simpler still: https://github.com/nathants/backup
Re: BorgBackup 2 has no server-side append-only anymore
#34I've been using device mapper+encryption to backup my files to encrypted filesystem on regular files. (cryptsetup on linux, vnconfig+bioctl on openbsd). Is there a reason for me to use borgbackup? Maybe to save space? I even wrote python scripts to automatically cleanup and unmount if something goes wrong (not enough space etc). On openbsd I can even Double encrypt with blowfish(vnconfig -K) and then a diff alg for b…
Every once in a while things gets sparsed out, so that for example I have daily backups for the recent past, but only monthly and then even yearly for further back.
Re: BorgBackup 2 has no server-side append-only anymore
#35Do something simpler. Backups shouldn’t be complex. This should be simpler still: https://github.com/nathants/backup
Uh, who has the money to store backups in AWS?!
My low value backups go into a cheap usb hdd from Best Buy.
Re: BorgBackup 2 has no server-side append-only anymore
#36I'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?
Borg has the issue that it is in limbo, i.e. all the new features (including object storage support) are in Borg2, but there's no clear date when that will be stable. I also did not like that it was written in Python, because backups are not always IO blocked (we have some very large directories, etc.).
I really liked borgmatic on Borg, but we found resticprofile which is pretty much the same thing (it is underdiscussed). After some testing I think it is important to set GOGC and read-concurrency parameters, as a tip. All the GUIs are very ugly, but we're fine a CLI.
If rustic matures enough and is worth a switch we might consider it.
Re: BorgBackup 2 has no server-side append-only anymore
#37For 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…
rclone serve restic --stdio
You add something like this to ~/.ssh/authorized_keys: restrict,command="rclone serve restic --stdio --append-only backups/my-restic-repo" ssh-rsa ...
... and then run a command like this: ssh user@rsync.net rclone serve restic --stdio ...
We just started deploying this on rsync.net servers - which is to say, we maintain an arguments allowlist for every binary you can execute here and we never allowed 'rclone serve' ... but now we do, IFF it is accompanied by --stdio.Re: BorgBackup 2 has no server-side append-only anymore
#38Earlier 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…
I am already using zfs on my NAS where I want my backups to be. But I didn't consider it for backups till now
Re: BorgBackup 2 has no server-side append-only anymore
#39Earlier quoted context omitted.
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?
Are there any good options for an off-site zfs backup server besides a colo? Would be interested to know what others have set up as I'm not really happy with how I do it. I have zfs on my NAS running locally. I backup to that from my PC via rsync triggered by anacron daily. From my NAS I use rclone to send encrypted backups to Backblaze. I'd be happier with something more frequent from PC to NAS. Syncthing maybe? The…
Re: BorgBackup 2 has no server-side append-only anymore
#40Do something simpler. Backups shouldn’t be complex. This should be simpler still: https://github.com/nathants/backup
I don't see what value this provides that rsync, tar and `aws s3 cp` (or AWS SDK equivalent) provides.