I'm sure a bunch of folks (myself included) would be happy with a rough-around-the-edges beta without a GUI. It already builds, it's already maintained I'll see if I can get the port to Linux "finished". And 2) an installer - which isn't a big deal honestly, I could bang that out in 2 or 3 days. What it is missing is two things: 1) A GUI, which I might even be willing to not bother with for a "minimum viable Linux product" because you can hand edit the bzinfo.xml file with "vi" or "emacs" and it would work fine to just start with. It already builds, it's already maintained. But once that ships and is behind us, I'll see if I can get the port to Linux "finished". We're up to our eyeballs in a different project right now - I'll be working all weekend on that. So in the end, it WILL NOT break our business model and we should do it. The vast majority of customers on Backblaze Personal Backup simply find the service convenient and a "fair" price and couldn't be bothered to even do the math, half of them COULDN'T do the math, and 98% of them wouldn't care enough to spend the time doing the math! Not to mention, if it implies a repush of all their files, another 1.99% of them would say "no, I just don't care enough to start over and repush from scratch". And that would blow our business model for Backblaze Personal Backup - we depend on the customers that overpay a little bit (let's say with a 1 TByte backup) to make up for the customers that underpay a little bit (let's say a 3 TByte backup).īut after everything we have learned, that won't occur - it just won't. And if anybody's backup was 1 penny more expensive on B2, they would switch to the cheaper Backblaze Personal Backup. One of the things we were worried about early on about that project is that every customer would do the math, and if their backup size would result in 1 penny cheaper with the "backup store" in B2, they would switch over to the cheaper B2. One of my lifetime bucket (pun intended) list goals at this point is to port the Backblaze Personal Backup Client to layer on top of Backblaze B2, support Linux, and open source it, so that anybody who likes can get very close to the IDENTICAL experience on either Backblaze Personal Backup or on Backblaze B2. What none of the solutions I've found do is let me install it, configure it, and then not have to worry about it until something goes wrong like Backblaze for Windows.Īs the programmer who created (and loves) the Backblaze Personal backup (the Windows client), you make me so happy. All in all - if it's not perfect, it's damn close to it. Tl dr: Dear Backblaze: Give me Backblaze on Linux and charge me for the data usage. So I'd happy pay the B2 rates, or heck - even a per-device monthly fee PLUS the B2 rates to get Backblaze on Linux. I understand that this would require more development effort, and that too needs to be funded. I have to set up some other way of monitoring them, to ensure they're backing up. I've moved a lot of the machines I'm responsible for over to Linux, but the thing that still makes me nervous is whether the backup options I've put in place will actually have worked when they're needed the most. What none of the solutions I've found do is let me install it, configure it, and then not have to worry about it until something goes wrong like Backblaze for Windows. 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |