![]() Because, it likes to cache lots of metadata (for performance) and it can get memory intensive. To give at least some objections, if you're VERY low on RAM, and happen to have LOTS of very small files in there, then it could be a problem. Whatever you're using right now, give restic a chance and see what it can do, you'll be amazed. But, it won't be easy (to find a bug, that is). And very, VERY performant.įinally, full open source, find a bug, you get to fix it. Gained compression support last year, so finally efficient in space usage, too. In this day and age important stuff: fully encrypted, so put/send stuff anywhere and sleep well. Several disaster recovery restores of whole machines already, never dissapointed, very versatile and robust, one good example of German Quality. I am not considering in this question advanced stuff like Kubernetes environments etc (for Kubernetes I use Velero and Kasten said: What do you use to back up your servers? I mean "old school" servers where you install stuff directly or with Docker etc. On the one server I was testing it it corrupted the repository 3 times in a row, until I gave up and switched back to Restic. ![]() It's promising, but it's not reliable at all at this stage. The one that has disappointed me the most is Kopia. But many people are happy with its reliability. ![]() it takes ages to find the list of files from the snapshot to restore. And it's exceptionally reliable: I have had to do restores many times with this tool from small and large repositories and it has never failed me, never.īorg has always looked rock solid to me as well.Īnother good one which I kinda like for the nice UI is duplicacy. Restic in particular just works and is ridiculously easy to set up and use without any complicated commands. By "best" I mean first and foremost reliable, then comes the speed and features. For me the best two remain Restic (which is what I use now) and Borg.
0 Comments
Leave a Reply. |