3 ms·

I also like Borg back up. I wonder if I am missing something compared to restic?

by aborsy 6y ago

more-coffee 6y ago
Borg is supposedly a bit faster, restic supports a ton of backends https://github.com/restic/restic/issues/1875 https://github.com/restic/restic/issues/1875 Also restic does not allow to backup unencrypted. I haven't used borg. Only done some maintenance on restic backup jobs at work. Restic's command design is intuitive and the documentation is good. But Borg looks just fine in that regard as well.
- aborsy 6y ago
  Thank you ! I posted another question on Borg, in case you know the answer!
magicalhippo 6y ago
I found restic did not scale well with a large amount of files when I tried it a few years ago. Has this changed? Is Borg better? I used to run Crashplan with near-continuous backup for my important files, and I'm still missing this.
- stevesimmons 6y ago
  I too used to use Crashplan until they discontinued their personal subscription and with it the option to backup to local drives. Around the same time I tried Restic. That ran into difficulties (don't recall what anymore) so I switched to Borg. Borg has been 100% reliable, including a full restore of /home after my laptop was stolen.
- fidelramos 6y ago
  I don't know what you call large, but my personal restic backup runs weekly, ~250000 files, 2 TB, finishes in 7 hours saturating a 600 Mbps connection over S3 protocol. I'm very happy with restic.
  - magicalhippo 6y ago
    Well I have about 2-3x as many files, but only ~100GB. The main concern was finding out which files to take backup of, it would take quite a long time. Like I said I was hoping to get the 10-15 minute intervals I had with Crashplan.
rsync 6y ago
"I wonder if I am missing something compared to restic?" The biggest difference for us is that borg really requires a server side 'borg' binary to talk to, which we have built into rsync.net. restic, on the other hand, can just connect to any old SFTP endpoint. This means we need to preserve some amount of backwards-compat and so we maintain borg0.x and borg1.x binaries in our environment (and eventually, borg2.x).

I also like Borg back up. I wonder if I am missing something compared to restic?

by aborsy 6y ago

I also like Borg back up. I wonder if I am missing something compared to restic?

Borg is supposedly a bit faster, restic supports a ton of backends https://github.com/restic/restic/issues/1875 https://github.com/restic/restic/issues/1875 Also restic does not allow to backup unencrypted. I haven't used borg. Only done some maintenance on restic backup jobs at work. Restic's command design is intuitive and the documentation is good. But Borg looks just fine in that regard as well.

aborsy 6y ago
Thank you ! I posted another question on Borg, in case you know the answer!

magicalhippo 6y ago

I found restic did not scale well with a large amount of files when I tried it a few years ago. Has this changed? Is Borg better? I used to run Crashplan with near-continuous backup for my important files, and I'm still missing this.

stevesimmons 6y ago
I too used to use Crashplan until they discontinued their personal subscription and with it the option to backup to local drives. Around the same time I tried Restic. That ran into difficulties (don't recall what anymore) so I switched to Borg. Borg has been 100% reliable, including a full restore of /home after my laptop was stolen.
fidelramos 6y ago
I don't know what you call large, but my personal restic backup runs weekly, ~250000 files, 2 TB, finishes in 7 hours saturating a 600 Mbps connection over S3 protocol. I'm very happy with restic.
- magicalhippo 6y ago
  Well I have about 2-3x as many files, but only ~100GB. The main concern was finding out which files to take backup of, it would take quite a long time. Like I said I was hoping to get the 10-15 minute intervals I had with Crashplan.

rsync 6y ago

"I wonder if I am missing something compared to restic?" The biggest difference for us is that borg really requires a server side 'borg' binary to talk to, which we have built into rsync.net. restic, on the other hand, can just connect to any old SFTP endpoint. This means we need to preserve some amount of backwards-compat and so we maintain borg0.x and borg1.x binaries in our environment (and eventually, borg2.x).