https://borgbackup.readthedocs.io/en/stable/internals/securi...
Last time I checked there was still no work being done on improving performance. Multithreading has been on the agenda for years and will probably never come, much like improved crypto.
Thus his post was valuable to me.
"Why not add a PR" is not a reasonable response to something like this. I'm looking to use a backup system, not create one. If something works so poorly that I'd have to start submitting PRs before using it, I'm far more inclined to go elsewhere.
> The two points you mention are both known and on the agenda for this year
This is a rather strange response to the above...
The MAC should prevent the remote server changing the counter or any encrypted bits.
https://github.com/borgbase/vorta/
(I'm the original author, but Thomas, the current Borg maintainer is also very active.)
Edit: It looks like Vorta doesn't obey Mac OS's Dark Mode so it looks like the app doesn't launch.
You could probably run it today using the Windows 10 Linux subsystem, but it's not fully tested and will need some small fixes. Maybe later this year.
If anyone is interested in working on this platform, just post at [1]. It's probably very doable.
(Note: I work on Arq)
[1] https://www.arqbackup.com [2] https://www.arqbackup.com/arq_data_format.txt
As is it's really best for workstations rather than the NAS/servers a lot of people who care about their data use (not just basement-dwelling data hoarders but also professionals like photographers and videographers).
I'm quite sure if Arq was available in a command-line version for Linux/FreeBSD, i would use that instead. It has been nothing but rock solid on my client machines.
Restore through the UI is a bit wonky, but once it's started it works well.
I don't think Arq brings something to the table that Borg/Restic/Duplicity doesn't already provide, besides a piece of software i'm familiar with, and trust. (and trust doesn't come easy when it comes to backup software!)
As i wrote, i already use Arq on my client machines instead of the mess that is "TimeMachine over wifi", but when it came to backing up my NAS and server/VPS, i had to look for something else, as Arq is not available on those platforms.
My use case would be backing up with Arq from a FreeBSD/Linux NAS/Server to a remote (networked at least) target, and in case of a full restore, i would use the command line as well.
I would then use Arq for Mac/Windows for "plucking" single file restores.
Now I’m using both Duplicity and Restic, for different backups.
* Fully open-source, command line implementation. Script as needed. * Supports ton of backends, including directories, SFTP, and many cloud services. * Supports multiple backup operations in parallel. Create one repo for multiple machines. * A repo is really an encrypted object store with a lists of directory/file/metadata references (snapshots). If the same file exists on multiple directories/drives/machines, it is deduplicated. * Supports tagging, which allow you to identify independent snapshots and manage them. * Supports purging old data with conditions, ie. keep last 7 daily, 3 weekly, and 6 monthly. * Can verify and repair repositories.
I regularly use it to backup my home server to a backup drive and to Backblaze. I've also used to back up my home directory of my development machine to replicate it on another machine.
Took me forever to find that myself so just posting it here in the hopes that more people will support the developers.
I'm setting up backups and looked into most available solutions, including restic, borg, and duplicity, but Bareos by far seems the best one. It's just a little harder to set up, but totally worth it.
According to a more up to date comparison[1] (recommends Arq), Borg is also slow because it processes sequentially.
[1]: https://www.lullabot.com/articles/backup-strategies-for-2018
This is true of most backup programs.
For those that don't know, borg is a backup utility[1] that has been called the "holy grail of backups"[2].
It takes your plaintext files and directories, chops them into gpg-encrypted chunks with encrypted, random filenames, and will upload (and maintain) them, with an efficient, changes-only update, to any SFTP/SSH capable server.
My understanding is that the reason people are using borg instead of duplicity is that duplicity forces you to re-upload your entire backup set every month or two or three, depending on how often you update ... and borg just lets you keep updating the remote copy forever.
[1] http://borgbackup.readthedocs.io/en/stable/
[2] https://www.stavros.io/posts/holy-grail-backups/