61–70 of 124 posts
However I found that the backends weren't well abstracted enough in v1 to make that easy.
However for v2 Thomas Waldmann has made a nice abstracted interface and the rclone code ended up being being only https://github.com/borgbackup/borgstore/blob/master/src/borg...
Earlier quoted context omitted.
I'd recommend having a look at Hetzner's "storage box" products. It's hard to beat 4€ a month for 1TB of SSH accessible storage.
SSH access on the storage boxes is quite limited: > It is possible to get interactive SSH access, but this access is limited. It is not possible to have interactive access via port 22, but it is possible via port 23. There is no full shell. For example, it is not possible to use pipes or redirects. It is also not possible to execute uploaded scripts. https://docs.hetzner.com/storage/storage-box/access/access-s... htt…
Note they're intended for backup use and therefore don't have guaranteed uptime or throughput.
How can we use it for large database backups > 500 GB and is anyone doing that on daily basis?
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
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
Or, if you're using a desktop environment and prefer a GUI, Vorta has been treating me well. https://vorta.borgbase.com/
I've always been doing "two-pass" backups to achieve "3-2-1" goal: first pass is to run BorgBackup to backup devices to my home server. The second pass is to use rclone to transfer the repos on home server to an object storage service (B2). With rclone support built-in, the setup would be much easier.
I think this is heavily discouraged? Instead you should have multiple separate borg repos to minimize risk of misconfiguration and data corruption.
https://borgbackup.readthedocs.io/en/stable/faq.html#can-i-c...
It is not "heavily" discouraged. But you have to pay extra attention to perform a clean copy of the borg repo's files, and ideally check both instances regularly for integrity. I would assume it's easy to forget validating the "cold storage" copy of your borg repo in practice.
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
> set and forget for me and after 7 years Please tell me you verify your backups now and then?
Restoring one file from the backup, works but what if something else is corrupted?
Restoring the system from the image, works but what if some directory is not in the backup and you don't see that while testing?