I tried to use unison for serious production work a few years ago, and it fell short. It would fail or become incredibly slow with large (but not huge) amounts of data. A pity because the concept is great. I wonder if it has improved since.

"I wonder if it has improved since."

Unison is very interesting and it is, indeed, very special in that it solves the very specific use-case of my parent post.

However, my own opinion, and that of just about everyone who cares about backup tools is that 'borg' is the "one true way":

https://www.stavros.io/posts/holy-grail-backups/

I played with borg some in the early days and was unimpressed with some of the methodology and code quality displayed on public forums like GitHub. This is kind of archival work MUST be correct and carefully designed due to its sensitive nature. I hope I'm not giving the project an unfair shake here, but I checked it again recently and the first several lines of the GitHub page list 3-4 fairly recent versions that have caveats around data corruption and the like ...

This is not really isolated to borg, so I don't want to pick on them too much (plz shield your eyes in the direction of rclone...), but calling it the "holy grail" is a bit rich IMO. This kind of stuff is simply not industrial grade software.

Any idea if this benchmark is still accurate? https://github.com/gilbertchen/benchmarking

('attic' on there is actually borg)

Borg has a lot going for it, but I'm hesitant to call something a holy grail or one true way if it can't do compact diffs. Especially when it needs active server software, which makes pruning much easier.

What about restic?

https://restic.net/

Yes, we support restic. I don't have anything interesting to say about borg vs. restic ...

You can work around failures of large initial unison syncs by creating a partial directory tree on the target manually.

It treats the creation of a new directory as an atomic operation, and rolls it back on failure.

(So, if the initial sync will take a week, then precreate the top level or two of the directory hierarchy...)

It’s an annoying problem, but after the initial sync, partial syncs are fast and reliable.

I have always been intrigued by your service, and will probably try it at some point for a smallish setup for important data, but whenever I think of backups in the TB range, it gets way out of budget (even after accounting for borg or other discounts). Do you have any plans to compete on pricing with other popular cloud/storage providers? I understand that this is a different product for a different audience.

"Do you have any plans to compete on pricing with other popular cloud/storage providers?"

We try to keep out pricing very roughly inline with Amazon S3. If you know to look for the discount signup rates it should be very slightly cheaper than S3.

We can't promise customers support from real UNIX engineers and also match B2 pricing. I'm happy with that and plan to continue on that path ...

We would be very happy to have you.

> If you know to look for the discount signup rates it should be very slightly cheaper than S3.

I'm interested. Do you mean the special borg account or should I look more? Thanks!