Backblaze blog reliability5/16/2023 ![]() For example, if a drive is installed on July 1st and fails on August 31st, it adds 62 drive days and 1 drive failure to the overall results. ![]() A Drive Day is only recorded if the drive is present in the system. This is one of the reasons we compute the Annualized Failure Rate using “Drive Days”. This is usually based on the idea that drives entering or leaving during the cumulative period skew the results because they are not there for the entire period. Some people question the usefulness of the cumulative Annualized Failure Rate. The annual failure rate of 2% across all drive families is excellent.īackblaze offers the following explanation for how it calculates its annualized failure rates. As the 8TB drives get more use these figures should settle down. Most of the drives have minimal failure rates, though there are a few cases where the gap between the low and high confidence interval is particularly large (these seem to indicate cases where Backblaze has either only recently deployed drives or has had a small number of failures in a small pool). ![]() For those of you curious about how much data Backblaze stores in total, the company has released a chart showing its own capacity growth rate over the past four years.Įarly reliability data on the new drives is good, without much sign of a bathtub curve (an early period of time during which drives initially fail). ![]() The company migrated an estimated 6.5PB of data from a set of Storage Pods built with 2TB HGST hard drives to a set of Seagate 8TB drives, quadrupling the amount of storage available per-pod. While SSDs have made marked inroads into the hard drive market thanks to a rapidly diminishing cost-per-bit, hard drives still reign supreme as the most cost-effective method of storing data.īackblaze kicked off its 8TB migration by deploying more than 2,700 Seagate HDDs. Backblaze has released its quarterly details on hard drive reliability, including new information on its initial deployment of 8TB hard drives. ![]()
0 Comments
Leave a Reply. |