Live data from Hacker News

BorgBackup 2.0 supports Rclone – over 70 cloud providers in addition to SSH

borgbackup.readthedocs.io

101–110 of 124 posts

Re: BorgBackup 2.0 supports Rclone – over 70 cloud providers in addition to SSH

#101

I remember reading quite a few years ago about people working to get Borg to work with windows. Has there been any recent progress with that?

Basic stuff might work in a "posix-like" environment, like when using cygwin or WSL.

The main problem is that there currently aren't active windows developers within the borgbackup project who continuously test and improve the windows specific code parts.

Since recently, we at least have some working CI on windows again, at least that was fixed.

Re: BorgBackup 2.0 supports Rclone – over 70 cloud providers in addition to SSH

#103
post #30

Currently I'm just using bare rclone to backup to my own remote machines, but obviously this isn't very professional solution. Was thinking to add Backblaze B2 as a remote, but I guess using rclone wouldn't be a state-of-the-art solution here. After all, it isn't really a backup tool, is it? It has some built-in encryption, but it's a bit clunky, and I'd think a proper backup tool should automatically divide data int…

I've been using bupstash since trying to do backups on an rpi and finding Borg too slow to be usable. Since then I upgraded to a proper server at home but kept bupstash as I found it to just work better for the most part. Keep in mind there's not been much progress since the last release two years ago and its still tagged as beta by the author. Tbf I think he has a higher quality standard than in other projects that are not tagged as such.

Useful backup tool comparison: https://github.com/deajan/backup-bench

Re: BorgBackup 2.0 supports Rclone – over 70 cloud providers in addition to SSH

#104
post #95

BorgBackup user here and really happy. It was a set and forget for me and after 7 years, the deduplicated backup is still working flawlessly each week. I recommend pairing it with borgmatic [1], which helps to design away some of the complexities of the underlying borg backup. [1]: https://github.com/borgmatic-collective/borgmatic

My problem is I learn some tool like this, set it, and then indeed forget it. Then I avoid testing my backups because of the work it takes to un-forget it. Because of this, I'm leaning more and more towards rsync or tools that have GUI frontends.

Rather than avoid tools that work well, I would encourage you to adopt solutions that solve your use cases. For instance, if you aren't getting notifications that a backup is running, completing or failing, then all you've set up is a backup job, and not built a BDR process. If you're looking for a tool to solve your entire BDR plan, then you're looking at a commercial solution that bakes in automating restore testing, so on and so forth.

Not considering all the aspects of a BDR process is what leads to this problem. Not the tool.

Re: BorgBackup 2.0 supports Rclone – over 70 cloud providers in addition to SSH

#105
post #37

Earlier quoted context omitted.

Syncthing?

Syncthing is great, but it's peer to peer, and it requires block storage ("filesystem"). It also has no idea of point-in-time snapshots. Syncthing, is, as is unison, rsync, etc, basically a mirroring tool. By contrast, Borg, Restic, Kopia (anything else?) use object storage, aka binary blobs, like S3 or R2 or One Drive. They store both entire copies and small diffs on top of them, much like video codecs, or like git.…

This is how I run backups privately and at work: hourly local snapshots with btrbk and hourly remote backups of filesystem snapshots with Borg. The local snapshots backups are great for quick restores or finding out recent file changes.

Prometheus alerts check that latest backup is at most two hours old and that the filesystem is not reporting errors. This setup running for more than a year now and gives great peace of mind.

Re: BorgBackup 2.0 supports Rclone – over 70 cloud providers in addition to SSH

#106
post #78

For personal use, at what point would one recommend using Borg over a regular rsync? I currently use rsync to backup up a set of directories on a drive to another drive and a remote service (rsync.net). It's been working great, but I'm not sure if my use-case is just simple enough where this is a good solution, or if I'm missing a big benefit of Borg. I do envy Borg's encryption, but the complexity of a new tool tied…

With rsync, you’re replicating only the last state. With borg, you can see all backups being made and rollback to any previous snapshot. This is true of a lot of backup solutions btw.

Concretely, if you inadvertently delete a file and this get rsynced, you cannot use the backup to restore that file. With borg you can.

Re: BorgBackup 2.0 supports Rclone – over 70 cloud providers in addition to SSH

#107
post #105
post #37

Earlier quoted context omitted.

Syncthing is great, but it's peer to peer, and it requires block storage ("filesystem"). It also has no idea of point-in-time snapshots. Syncthing, is, as is unison, rsync, etc, basically a mirroring tool. By contrast, Borg, Restic, Kopia (anything else?) use object storage, aka binary blobs, like S3 or R2 or One Drive. They store both entire copies and small diffs on top of them, much like video codecs, or like git.…

This is how I run backups privately and at work: hourly local snapshots with btrbk and hourly remote backups of filesystem snapshots with Borg. The local snapshots backups are great for quick restores or finding out recent file changes. Prometheus alerts check that latest backup is at most two hours old and that the filesystem is not reporting errors. This setup running for more than a year now and gives great peace…

That's an appreciable integrity assurance!

Mine is simpler: Syncthing with staggered versioning for important data, periodic Restic backups of the home directory (excluding caches), keeping several recent backups and a couple of older backups.

I've restored from these backups 4 times, both due to crashes and when moving to a new machine, without any adventures in the process.

Re: BorgBackup 2.0 supports Rclone – over 70 cloud providers in addition to SSH

#108
post #94
post #78

For personal use, at what point would one recommend using Borg over a regular rsync? I currently use rsync to backup up a set of directories on a drive to another drive and a remote service (rsync.net). It's been working great, but I'm not sure if my use-case is just simple enough where this is a good solution, or if I'm missing a big benefit of Borg. I do envy Borg's encryption, but the complexity of a new tool tied…

Usual problem, if you delete/corrupt a file and find out two days later, your daily backup is not going to help you. Having more than one snapshot is very valuable. http://www.taobackup.com/ etc Rsync is also very slow with lots of files, and doesn't deal with renamed files (will transfer again).

Rsync backups can be setup to deal with this. I have rsync setup with daily incremental backups, the main sync to a 'current' folder and the old version of changed files staying in a weekday named folder (eg. Monday). So I have a rotating 7 day period to recover files. On top of that I have a monthly long term backup of the last old version of that month. This provides an arbitraribly long monthly window to recover from. Rsync is very versatile.

Re: BorgBackup 2.0 supports Rclone – over 70 cloud providers in addition to SSH

#109
post #94

Earlier quoted context omitted.

Usual problem, if you delete/corrupt a file and find out two days later, your daily backup is not going to help you. Having more than one snapshot is very valuable. http://www.taobackup.com/ etc Rsync is also very slow with lots of files, and doesn't deal with renamed files (will transfer again).

Rsync backups can be setup to deal with this. I have rsync setup with daily incremental backups, the main sync to a 'current' folder and the old version of changed files staying in a weekday named folder (eg. Monday). So I have a rotating 7 day period to recover files. On top of that I have a monthly long term backup of the last old version of that month. This provides an arbitraribly long monthly window to recover f…

Yeah with enough scripting, you can rebuild a slow equivalent to a real backup program, that will also use 10x the disk space.

Re: BorgBackup 2.0 supports Rclone – over 70 cloud providers in addition to SSH

#110
post #109

Earlier quoted context omitted.

Rsync backups can be setup to deal with this. I have rsync setup with daily incremental backups, the main sync to a 'current' folder and the old version of changed files staying in a weekday named folder (eg. Monday). So I have a rotating 7 day period to recover files. On top of that I have a monthly long term backup of the last old version of that month. This provides an arbitraribly long monthly window to recover f…

Yeah with enough scripting, you can rebuild a slow equivalent to a real backup program, that will also use 10x the disk space.

Yep. But it works and has worked for over 20 years. Various backup software has come and gone in that time but rsync has been a rock.
Post reply on HN