On the Linux side, well there's a buch of backup software - everything from "I built 500 lines of shell script around rsync" to Deja Dup to Borg to everything else. It lets me have the confidence that all the machines I'm responsible for are, actually, backed up. If a machine doesn't back up for some length of time, I get told to go check it out.Īll in all - if it's not perfect, it's damn close to it. I get a monthly email that the machines I'm backing up are, infact, backing up. It is pretty smart about not consuming all the network bandwidth on a machine (good for places where 1Mbit upload is considered pretty good). I install it, I configure it, I never touch it again unless something goes wrong.
The things I love about Backblaze on Windows is that it's very much no-nonsense. I'd like to make a case for making Backblaze on Linux with B2 as the backend (or at least charge like B2). There's a post here that perfectly explains it, and I'm fully in agreement with the rationale of not just offering flat-rate options.
There's been a ton of posts asking about Backblaze on linux OSs.Ī lot of the responses from Backblaze can be summed up as "Offering Backblaze on Linux would make it unprofitable".
0 kommentar(er)
