News for hackers. Stuff that matters.
Re:Arq 5.8.5 for Mac Fixes a Bad Bug by jwr on Tuesday May 23, 2017 @10:13AM (#14401310)
Thanks for the honesty, I really appreciate this.

And BTW, I am a happy Arq user, I've been using it on multiple machines for the past several years. It is the ONLY backup solution out there that:

* encrypts my data without me having to supply the decryption key to a third party when decrypting,

* decouples backup and encryption from a particular storage provider,

* makes me independent of ebbs and flows of storage providers by supporting pretty much every one out there.

I've learned to value independence over cheapness, so I stick with Arq. Plus, it's been working really well over the years.

Re:Arq 5.8.5 for Mac Fixes a Bad Bug by dsacco on Tuesday May 23, 2017 @10:15AM (#14401327)
Duplicati hits everything you're talking about (I have essentially the same criteria for backups).[1] It's cross-platform (Windows, macOS and Linux).

I love using Arq on my MacBook Pro, but since they won't release a Linux client I use Duplicati on Ubuntu. I like it a lot.

__________________________

1. https://www.duplicati.com/

Re:Arq 5.8.5 for Mac Fixes a Bad Bug by jwr on Tuesday May 23, 2017 @01:43PM (#14403321)
Nice! Thanks for posting this — I've been looking for something like Arq for Linux, and this seems to be it.
Re:Arq 5.8.5 for Mac Fixes a Bad Bug by aolagers on Tuesday May 23, 2017 @11:34AM (#14402077)
These are also handled by Borg [0], which supports compressed data as well. However, it does not have direct support for different cloud providers so the archive must be synced with different tools.

[0] https://borgbackup.readthedocs.io/en/stable/

Re:Arq 5.8.5 for Mac Fixes a Bad Bug by dom0 on Tuesday May 23, 2017 @01:00PM (#14402924)
A couple people use external tools (rclone and git-annex are popular) to sync their Borg repos somewhere else. This requires enough local space (hard drive / NAS / whatever) to store the repository. This can be an advantage (=storing to a local drive is very fast; if it's on a NAS the NAS can sync it to the cloud; also you can quickly recover files from a local drive), but is not always practical.

In the long run (Borg 1.2 - 1.3) we'll add an interface to Borg to make it storage-independent ("repository drivers") in a secure way (this is already sketched out, just not enough manpower in the project to implement it all right now. Finishing 1.1 has top priority and received a bit of funding).

Adding support for S3 and $threeDozenOtherAPIs directly to Borg is generally speaking unlikely.

PS: To-be-released Borg 1.1 will optionally get rid of cache syncs for "borg create".