6 ms·
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 archiv
by aolagers 9y ago
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/ https://borgbackup.readthedocs.io/en/stable/
- dom0 9y agoA 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".