BackBlaze vs. CrashPlan
-
@BBigford said
Prefer to leave your apps open, lock your computer, and go home for the weekend? No backup is taking place.
Don't machines get rebooted for patching & updates out of office hours?
-
I wonder if @aaron and @ChristopherBB have relayed on the Java issue to BB? I'm sure product teams would love to hear that them avoiding Java and using a native tool set alone is a cause for customer acquisition. That's a metric or anecdote that they would love to have in their collection, I'm sure.
-
@scottalanmiller said in BackBlaze vs. CrashPlan:
I wonder if @aaron and @ChristopherBB have relayed on the Java issue to BB? I'm sure product teams would love to hear that them avoiding Java and using a native tool set alone is a cause for customer acquisition. That's a metric or anecdote that they would love to have in their collection, I'm sure.
No no. They use it on their marketing already
https://www.backblaze.com/cloud-backup.html
Native Software
Java is responsible for 91%* of security attacks. Backblaze's code is native to Mac and PC and doesn't use Java.Do I want to support a company who does not use Java? Absolutely. Until CrashPlan changes their app, they won't get clients from my end.
-
@Breffni-Potter BackBlaze seems to be better but I am sticking to CrashPlan due to the family plan. 10 computer for 13.99 is hard to beat.
-
@aaronstuder said in BackBlaze vs. CrashPlan:
@Breffni-Potter BackBlaze seems to be better but I am sticking to CrashPlan due to the family plan. 10 computer for 13.99 is hard to beat.
But I'd question why they are much cheaper than BackBlaze.
Either BackBlaze just want more money or CrashPlan are cutting corners somewhere.
For me, cloud backup is insurance against either my stupidity, theft/fire/flood. I prefer spending a bit more and not having to worry about it but to each their own.
-
@Breffni-Potter said in BackBlaze vs. CrashPlan:
@aaronstuder said in BackBlaze vs. CrashPlan:
@Breffni-Potter BackBlaze seems to be better but I am sticking to CrashPlan due to the family plan. 10 computer for 13.99 is hard to beat.
But I'd question why they are much cheaper than BackBlaze.
Either BackBlaze just want more money or CrashPlan are cutting corners somewhere.
For me, cloud backup is insurance against either my stupidity, theft/fire/flood. I prefer spending a bit more and not having to worry about it but to each their own.
Or CP has some brilliant means of making the backups cost less. I doubt that they do, just saying it's a possibility.
-
It's possible that the family plan has shown that statistically people back up only so much "per family." These plans of all types are all about stats. Any individual might end up costing the vendor money, but on average they make money.
-
Why does everyone keep complaining about CrashPlan and Java? Java is not installed on any Windows based system directly. If it uses it under the hood, I would not care. There is nothing to maintain or update.
-
On the same note, it does require java on Linux boxes, but it works perfectly with Java from the repos. So it stays part of the base update process anyway.
-
@scottalanmiller said in BackBlaze vs. CrashPlan:
It's possible that the family plan has shown that statistically people back up only so much "per family." These plans of all types are all about stats. Any individual might end up costing the vendor money, but on average they make money.
Right, I am only backing up 5 computer, about 500GB-ish.
That would cost me $25 on BB.
-
@aaronstuder said in BackBlaze vs. CrashPlan:
@scottalanmiller said in BackBlaze vs. CrashPlan:
It's possible that the family plan has shown that statistically people back up only so much "per family." These plans of all types are all about stats. Any individual might end up costing the vendor money, but on average they make money.
Right, I am only backing up 5 computer, about 500GB-ish.
That would cost me $25 on BB.
I'm sure that CP has really good statistics on how a family plan alters the average "per machine" backup amounts.
-
@scottalanmiller Right, if everyone was using many TB's of data it would never be profitable.
-
@aaronstuder said in BackBlaze vs. CrashPlan:
@scottalanmiller Right, if everyone was using many TB's of data it would never be profitable.
Yeah. they know that almost never do more than one or two family members keep a lot of data. Like in my family, if we needed to save all of our family videos we are going to save them all from one computer. Letting each of us back up our own machines won't significantly increase the amount that we back up total, it just makes it more convenient. CP probably makes extra money on that plan.
-
@scottalanmiller I guess I could backup my parents\grandparents to my computer, and just backup my one computer.... Hm....
-
On second thought, then you lose the versioning on each PC. No thanks!
-
@aaronstuder said in BackBlaze vs. CrashPlan:
On second thought, then you lose the versioning on each PC. No thanks!
But you can, actually. :-)... Use Crashplan to back up your computer. Then set up the Free code on your granparents computer and it will back up to your computer as well.... Then you just add the folder where Crashplan puts your grandparents backups into the online backup bits, and done.
Edit: This is what I am doing with my Laptop at home... Laptop backs up (via Crashplan) to big computer... big computer backs up online.
-
@dafyre your evil I like it
-
@aaronstuder said in BackBlaze vs. CrashPlan:
@dafyre your evil I like it
I prefer to call it creatively inclined.
-
@Dashrender Using the manual backup schedule setting, both the indexing and upload processes are triggered when the "Backup Now" button is selected. Both of those processes can also be started via command line, but there is a lockout if the indexing or upload processes initiate too often.
-
@dafyre We do not currently have any local backup features as a part of our service. There's already a number of services and softwares available to do so, many for free. We also feel that having local and offsite backups which are managed by different softwares/services reduces risk due to bugs or software issues.