Re:"It's the (Backblaze) restores that fail."
by SeanKilleen on Monday January 20, 2014 @10:46PM
(#7093319)
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.
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.