Hacker News Reader

I previously used Tarsnap, but I moved to using Borg on rsync.net. Borg can do all the stuff Tarsnap can do and comes with 'borg prune' included. In fact for Tarsnap I would have needed to write a custom script to perform regular pruning.

By relying on rsync.net's automated ZFS snapshots I get the same or similar protection compared to Tarsnaps's write-only keys.

For my personal use case cost wasn't an issue, though. It's less than 10 GB of data stored.

View on HN

After many years, I moved from tarsnap to Borg as well (hosted with borgbase.com).

It wasn't about price for me either. On the few occasions I actually had to restore some files, Tarsnap was glacially slow. That made me nervous if I ever hit a situation where I had to do a full restore.

Like you say, there's the quality-of-life features that I now don't have to script. Pruning, missed backup alerts, monthly reports are all things I've realized were sorely missing from my Tarsnap experience.

BorgBase does not do scheduled pruning? Not even via script?

I believe it inherits the same pruning behavior of Borg itself.

I don't know the architecture of Borg storage too closely, but I assume that since it is all end-to-end encrypted, Borgbase cannot do the pruning for you.

If you use append-only keys, they can't (destructively) prune, you have to use regular keys to do that.

Reply on news.ycombinator.com