atYevP

11 ms·

91.
by atYevP 6y ago
Yev here -> of course we read it! It's a data-rich article about data failure! And the kudos is mutual - loved the post! :D
92.
by atYevP 6y ago
Yev from Backblaze here -> We work with the drive manufacturers and their distributors! One of the reasons we think it's important to state the drive model is so people know exactly what is getting deployed versus just using ___ 14T
93.
by atYevP 6y ago
Yev from Backblaze here -> rest assured that we do read what you're writing on these posts and they've spurred some internal process discussions. I believe the bugs you mentioned were cleared/fixed with version 7.0.0.439 w
94.
by atYevP 6y ago
Yev from Backblaze here -> sorry about that Thom - it's one of the things we're definitely working on hammering down. Right now we're growing quite a bit on our engineer and infrastructure teams and one of the projects we&
95.
by atYevP 6y ago
We do have some drives that we use as boot drives and for logging. We write about them a bit in the post - they're primarily SSDs, so not included in the overall mix of data drives!
96.
by atYevP 6y ago
Yev from Backblaze here -> We just started deploying more of them! We added almost 6k WDC drives in Q4 - so we're getting more of them in the fleet! They have a pretty low AFR - but haven't been deployed for too long, so they&#
97.
by atYevP 6y ago
No, that comment was edited after I had responded - we're not against status pages - they are on the roadmap, but unfortunately not implemented yet.
98.
by atYevP 6y ago
Well, hopefully there won't be a next time - but also, bothering me doesn't help debug or resolve the problem, our Ops/Tech team do that :D
99.
by atYevP 6y ago
Yev here - we're investing the S3-endpoint issue - apologies for delay in response here, it took them a bit of time to wake me up. *Edit -> we've identified the fix and are rolling it out, you should see S3-Endpoint service res
100.
by atYevP 6y ago
Yev here -> Hey there! We've just signed with a new program provider and hope to be rolling out the private program in early November with a public rollout to follow. For now though we ask folks to reach out to bounty@backblaze.com
101.
by atYevP 6y ago
Yev here -> I should add that we have a Q&A webinar going live tomorrow with Andy the author, you can join the Q&A here: https://www.brighttalk.com/webcast/14807/446738?utm_source=T... .
102.
by atYevP 6y ago
Yev here -> I LOVED the OkCupid blog posts. So much good stuff in there. <3
103.
by atYevP 6y ago
I have a great relationship with the Code42 folk - they're good people and do good work! Their Small Business service is a bit more expensive, but yes at that increased rate they've been able to provide service to a few more platf
104.
by atYevP 6y ago
Feelin' good!
105.
by atYevP 6y ago
Yev here -> Good question! The ops team may have a different theory, but I think it's when they die! We still have 15k 4TB HGST drives in our fleet that are crushing the game, and have been for years. That said, we'll eventuall
106.
by atYevP 6y ago
Yev -> Hey there! At the moment I don't believe we have any of those in our fleet (some MD and MG but no MN) so I don't have any data on them or how they'd function in our environment at the moment!
107.
by atYevP 6y ago
Yev -> that's really interesting. Do you want to publish your data and maybe we can compare notes ;-)
108.
by atYevP 6y ago
Yev -> Great question. The problem does lay with the abuse of the unlimited services. We've been offering our unlimited backup for 10+ years now and our only price increase was from $5 -> $6/month after 10 years of keeping t
109.
by atYevP 6y ago
Yev from Backblaze here -> Most of the comments have it. They tend to be more affordable and the failure rates aren't that much different from their counterparts. Since we account for failure with our software layer a small failure
110.
by atYevP 6y ago
Yev from Backblaze here -> no, any drives that come DOA wouldn't have made it past burn-in and into our fleet, so they aren't represented.
111.
by atYevP 6y ago
Yev from Backblaze here -> price plays a large factor in our purchasing decisions, but you'll notice if you look at the failure rates that they're not THAT much different across the manufacturers. For home usage, you're li
112.
by atYevP 6y ago
Yev from Backblaze here -> we do have SSDs in the fleet but they are primarily boot and data drives, so they're not really an apples:apples use-case. We're constantly looking for interesting news from our fleet though, so if th
113.
by atYevP 6y ago
Yev from Backblaze here -> what a fascinating question! You need storage to "generate" the data, and you need storage to "store" the data - so this is a fun thing to ponder!
114.
by atYevP 6y ago
Thanks for the kudos! We've been seeing a lot of talk about this today - I'm glad we can be there for folks now that they need us :D
115.
by atYevP 6y ago
Yev from Backblaze here -> We're definitely a good repository for all of that data. Happy to have you :)
116.
by atYevP 6y ago
Yev here -> It's less of an algorithm and more of a purchasing department with lots of spreadsheets that tie into the AFR data as a data point - but yes, it's possible we could automate it, but there's some factors that ou
117.
by atYevP 6y ago
Yev here -> Yes we want to mitigate large batch failures by adding some drive/vendor diversification, that's definitely part of the equation!
118.
by atYevP 6y ago
Yev here -> Thanks! We love producing them - they are a lot of fun!
119.
by atYevP 6y ago
Yev from Backblaze here -> Some of the responses down below are correct - it really does come down to price. We run a fairly lean ship and so the price per gigabyte is weighed pretty heavily when we make our purchasing decisions. We have
120.
by atYevP 6y ago
Yev from Backblaze here -> Yes, we tend to weigh heavily in favor of price and Seagate thus far as been affordable with performance that meets our requirements, so that's why you'll see those drives in higher numbers. We'r

More ›