[res0nat0r]

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...

[SeanKilleen]

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.