The point the poster above is making is: Generally when you see posts with not a whole lot of troubleshooting which are decrying that the major component of your entire company (IE: restoring backups), is fundamentally broken, usually this leads to PEBCAK. After 10+ years dealing with users who claim that $ITEM is broken (yet has been working for years for the majority of customers) sets off the PEBCAK meter in that either they are doing something wrong, or more troubleshooting is needed before jumping to conclusions. If further troubleshooting does seem to point to an edge case, then finger pointing can begin...
I understand this concept. I also would not describe me as "decrying" Backblaze at all, nor saying that restoring backups is fundamentally broken. It's broken for me _right now_, and I think the UX and approach could be better.
I've been in IT for 10+ years, and while force killing chrome worked, it was a genuine surprise, given that every other site (including bandwidth-sensitive) activities performed fine. On that one, I should have dug deeper. Rather than closing and reopening the windows, I should have killed the processes sooner. I'm willing to give them a pass on that.
I'm more concerned about waiting 12+ hours for a 6GB restore that then can't be extracted and restored, even when I used their downloader to ensure better results.
These issues also happened on two different machines, both of which work fine in every other respect.
He's not even sure that Chrome.exe was at fault. Why are you so quick to assume that it's Backblaze's fault in this one customer instance? He could have just reinstalled his machine, did a lot of weird configurations, etc. and not have even rebooted his computer a single time yet. Anyway, my point is that there is a lot of missing variables and information to make such assumptions. The customer is _not_ always right, you know.
By "not being sure if it was Chrome", I mean that by any user's standards, I had closed and re-opened the application several times.
The first issue (downloads not working) was on an otherwise-fine laptop that I checked to ensure could do other bandwidth-sensitive tasks (streaming HD video, etc.) it was only the Backblaze site and downloader that showed 0-3kb/sec and then failed.
I could have done a lot of weird configurations, but just to be clear, in this situation, I did not. On the first download that didn't work, I was restoring to a laptop that I had just booted up and had not performed any configuration on. In the second case, I was downloading a 6GB file to newly restored system that I'd rebuilt from scratch, and I'd tested all of the components (including the network connection, disks, etc.) prior to considering the rebuild complete. After that and all of the updates, it had run in a stable condition for some time before I attempted the download.
I agree that the customer is not always right. But also note that I am not claiming that backblaze is evil. I'm claiming that this process and my experience makes me question their model as well as my own idiocies.
And I also should note that while I might not seem that adept in this scenario, I've spent years as an IT support person, systems administrator, and developer. Which is not saying I'm right all the time or to bolster my case, just to note that I didn't do _no_ troubleshooting before I wrote the post.
This was a different machine, but you're right that that problem might not have been backblaze's fault.
But if he had problems downloading on both computers it's quite likely that backblaze is at the very least providing a low-quality downloading application, if not having outright broken features.
It's ambiguous but I think he did the 6GB download on the restored machine?