41–50 of 124 posts
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.
It wasn't recommended a bit ago to use Borg 2.0 because it wasn't baked enough. Has that changed? Are people using Borg 2?
Author calls that out right at the top of the changelog: > Beta releases are only for testing on NEW repos - do not use for production.
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?
Then one can't call it "set and forget", right?
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?
[1]: https://borgbackup.readthedocs.io/en/stable/usage/check.html
So, should I plan to switch to this rather than keep using Kopia? I was using it for years on an external drive, but then I got a NAS, and did not want to fuss with community packages to get Borg working. Kopia works fine, aside from the confusing GUI setup process, but it seems to be the least popular up and coming option. Now it seems that this can directly target SFTP? I wonder what that means for the future of Ko…
My reason to go with kopia was that previously you were not able to backup multiple hosts into the same repo without great inefficiencies. I'm not sure if they still have resolved that. Another was its native S3 support which I use with ceph.
A perhaps more superficial personal reason is that at least Go is a statically typed language, even if its type system isn't that great..
Earlier quoted context omitted.
How good at deduping is this when encryption is enabled? I was looking at rsync.net and it killed me that they don't support encryption in a sane way.
It's very sane: encrypt the bits, then send it to the host. Curious what you think is not right with their methods.
It's annoying because if you have TBs of stuff that blows. I'm just curious what systems exist for incremental, encrypted backups that don't require full uploading new snapshots.
See here in the NOTE section. Re-reading this, it might a limitation of Duplicity. https://www.rsync.net/resources/howto/duplicity.html
Earlier quoted context omitted.
> set and forget for me and after 7 years Please tell me you verify your backups now and then?
> Please tell me you verify your backups now and then? Then one can't call it "set and forget", right?
I'm sure there's more thorough ways to do this kind of testing, but whatever level of confirmation you need automating it should be viable and then you only have to pay attention if/when something breaks.
Earlier quoted context omitted.
Author calls that out right at the top of the changelog: > Beta releases are only for testing on NEW repos - do not use for production.
That's fair. There's a lot of software that is generally ok to use in beta, however, and this has been in beta for a long time.