ntolia

Unfortunately, this is not true. You need to grab all the DB files (WAL, etc.) in a consistent manner. You can't grab them while writes are in progress. There are ways though. Look at what Kanister does with its recipes to get consistent DB snapshots to get a sense of the complexities need to do it "right."

One thing I will mention is that other backup projects have switched from Restic to Kopia. Velero from VMware comes to mind.

However, you should be able to use Glacier Instant Access. It will get you a bunch of the way there.

I haven't looked at duplicati in a while and, it has evolved. While Duplicati's feature set looks similar now, I would need to benchmark it both for efficiency and final backup sizes.

And, while not directly, I know a number of companies, including mine, do test restores all the time.

I've been using Kopia for my personal use and for products I have helped build at a couple of enterprise backup companies! It's also used by other open-source backup projects that focus on specific ecosystems (Velero and Kanister for Kubernetes, Corso for Microsoft 365 backup).

I am obviously biased but it's pretty amazing. AMA.

Hey folks, let us know if you have any questions about Corso. Would love to hear more about what you like to see as the project evolves.

You know, this is a great question. I believe what ARM is pushing now is Scalable Vector Extension (SVE) as the successor to NEON. I haven't seen benchmarks in the wild yet but it does have promise.

Kopia announced the 0.5 release of Kopia! This is a big milestone on the way to an upcoming 1.0 release. Apart from pluggable compression, deduplication, and encryption, this release includes expanded object storage support and an easy-to-use UI. Feedback welcome!