brianwski

6 ms·

1.
by brianwski 4y ago
Disclaimer: I work at Backblaze. > Do we know if these drives are the same as you would purchase in a retail outlet Seagate (for instance) won't sell ANYBODY drives directly, so they force us to get bids from various resellers and d
2.
by brianwski 4y ago
Disclaimer: I work at Backblaze, and I was here first. > I'd worry they would sue for... If you are referring to Backblaze, we're not going to "sue" anybody for anything. We (Backblaze) have dealt with a bunch of friv
3.
by brianwski 4y ago
> I doubt I'd get anywhere close to ROI with SSDs I think most people assume the SSDs are more expensive, but depending on their application they choose SSDs for the OTHER properties, like SSDs are quieter, and faster, and like you
4.
by brianwski 4y ago
> Capitalism does not reward hard work. Smart work, maybe, but not hard work. I'd say a person successful/rewarded in a capitalistic society (defined by accruing more wealth than they started with and not just spending down som
5.
by brianwski 4y ago
> Someone with some time could correlate SMART data to failure rate. We looked into it a little, some notes written up here: https://www.backblaze.com/blog/what-smart-stats-indicate-har... Short summary is there are
6.
by brianwski 4y ago
Disclaimer: I work at Backblaze but more on the backup client side that runs on laptops, not in the datacenter storage side. > Is there a failure list for write heavy drives? To be clear about what these drive failure stats are and what
7.
by brianwski 5y ago
Disclaimer: I work at Backblaze. Here is a histogram of backup sizes of our Backblaze Personal Backup Customers if it is useful: https://i.imgur.com/GiHhrDo.gif You have to zoom in to see the meaningful information. It ca
8.
by brianwski 5y ago
Disclaimer: I'm the engineer you are commenting on, I just want to straighten out one mis-understanding. > This quote especially seemed childish and immature to me: > > > "And this one makes me actively angry, because
9.
by brianwski 5y ago
Disclaimer: I work at Backblaze so I'm biased and you should keep me honest. > if you run into big trouble, you can go get the box back for a really fast restore Backblaze provides this service for our customers! Customers can ask
10.
by brianwski 5y ago
> useful to add another column for "label", Yeah, that would work really well. When you look at the "services" control panel in Windows, there are two columns. One column is "Name" of the service, and anot
11.
by brianwski 5y ago
> and congrats on the IPO Thanks, that was super exiting for us. After 14 years, I claim (and this is controversial) that we're no longer a startup and now we're just a mid-sized publicly traded company. :-) > process-base
12.
by brianwski 5y ago
> Symlinks have been supported since Vista I'm not aware of even Windows 10 or Windows 11 being able to create Symlinks on FAT32 and exFAT, but I could be wrong? But it doesn't matter, the code as written is cross platform, it
13.
by brianwski 5y ago
> > Backblaze ships with 21 identical copies of the same executable > > This seems needlessly dismissive. I feel like they definitely know that you can execute the same binary multiple times. I'm the programmer at Backblaze
14.
by brianwski 5y ago
> ... 4 - 6 words ... very conservatively 160 characters is probably going to fit Gotcha. I'll file a Jira ticket to see if we can easily and quickly raise it to 200 characters (round number). I think we can handle that easily an
15.
by brianwski 5y ago
> Love his web page on dutch bikes in Amsterdam. Ha! That's my half second of viral fame right there. You have no idea how blindly I stumbled into making that webpage. I haven't ridden bicycles more than a handful of times sin
16.
by brianwski 5y ago
> Is there a reason there’s a short limit on how long my Backblaze password can be? The current limit is 50 characters. There are reasons we don't let it get super long like 2,000 characters but we could easily double or triple the
17.
by brianwski 5y ago
Hey Robbie- I am touched you saved my email and remembered me, and that at the time you didn't respond negatively to the message. Thank you for being a customer. The only thing I regret is that comment about version number of 2.3.1 an
18.
by brianwski 5y ago
Disclaimer: I work at Backblaze on the backup client. > it looks like two sperm fighting over the egg In 2017, this was proposed as one of several possible animations in the Backblaze client showing you are uploading files from your lapt
19.
by brianwski 5y ago
One interesting thing that Backblaze supports (that I don't think many people use) is that you can actually use any S3 API on any bucket, and any B2 API on the same bucket. Like every other call if you want. So if you HAPPEN to find s
20.
by brianwski 5y ago
> how does the presigned URL work? I thought it was this - https://www.backblaze.com/b2/docs/b2_get_upload_url.html If you want to use Amazon S3 APIs, you do not call ANYTHING that is documented on the Backblaz
21.
by brianwski 5y ago
Disclaimer: I work for Backblaze so I'm biased. > Have you tried backblaze b2 storage? Requires more work client-side... Backblaze recently released an S3 compatible API, so I'm hoping it is zero client-side work: https:/
22.
by brianwski 5y ago
Disclaimer: I work for Backblaze so I'm biased and you should keep me honest. :-) > Backblaze as I mentioned in another comment will be a bad idea due to the poor S3 compatible interface Backblaze released an S3 compatible API rece
23.
by brianwski 6y ago
> you refuse to accept mine and others’ arguments about PEK Not at all! I agree with you COMPLETELY. You want a zero knowledge backup product, Backblaze offers that and makes a large amount of money from it (millions of dollars annuall
24.
by brianwski 6y ago
Disclaimer: I work at Backblaze so I'm biased and you should keep me honest. > they probably haven't thought about it in such stark terms Backblaze takes security incredibly seriously, and I assure you we have thought about it
25.
by brianwski 6y ago
> this response by you reads as quite disingenuous It wasn't intended as such, I really meant it. I'd like to get to the bottom of this, understand what this person's true issue with Backblaze is. > these seem like ver
26.
by brianwski 6y ago
Disclaimer: I work at Backblaze. > one should stick to SSDs for sound I think you should stick to SSDs for performance reasons. :-) I can't go back to spinning drives for my desktop computers. But here is one idea for you... Back
27.
by brianwski 6y ago
> noticed that you are a fellow Beaver. Go Beavs! ;-) Ha! This is a silly novelty "Beaver Baseball Cap" I was given during my internship in 1988 at Hewlett-Packard in Corvallis: https://i.imgur.com/G0rPHGP.jpg
28.
by brianwski 6y ago
> Whether intentional or not, it's also great word-of-mouth advertising. Oh, this has really worked out for Backblaze and we know it. The first time we published our drive failure rates (I think January of 2014?) a few people said,
29.
by brianwski 6y ago
> I would expect an automatic process - disable and remove failed drive completely from a tome, add SOME free reserve drive at SOME rack in the datacenter to the tome We have spec'ed this EXACT project a couple different ways but h
30.
by brianwski 6y ago
Disclaimer: I work at Backblaze. > as much as I hate it I'm following Backblaze around and posting incorrect information about them I get the impression Backblaze did something to upset you. Can you let me know what it is so I can

More ›