I don't think we should be relying on people's opinions for this topic. Instead read the Backblaze blog with real data and analysis which they record and post quarterly.
Latest post https://www.backblaze.com/blog/2018-hard-drive-failure-rates/
Video Surveillance Hard Drive Failure Statistics 2018
Published Nov 02, 2018 11:05 AM
Hard drive failures can be significant service problems but how common of an issue are they in video surveillance? How long do drives last when constantly being written to?
150+ integrators answered this:
Video Surveillance Recording: How many years until a hard drive fails? What reasons for drive failure do you see most often?
In this report, we share our findings from surveying integrators, providing new data on hard drive failure statistics in video surveillance, and what factors integrators say most often causes drive failures.
5 ***** ** ******
****** **** ** *********** ********* **** drives **** ** * ***** ** longer, **% ** ***** ********* ****** lasting ****** * *****, *** ** many ** ** *****. **** *% mentioned ******** ** ***** * *****.
*** ****** ********* *** *** *** drives ****** **** **** ** ************* problems, ***** ****** ******, *** ******** continuous ***** **** **** *** **** of *** **** *****.
***** *********** *** ******* *** ******* were ****** ********* ** ******* ****** ********* **** ****:
Heat *** ************* ****** ***** ********
*** **** ****** ******* ********* *** drive ******** *** **** ** ************* factors **** **** ** **** *******. However, **** ** *** ****-******* ******** claimed * **** ***** **** ** 5 ***** ** ****, ***** ** beyond *** * ** *** *-**** warranty ** **** *************, *** ***** also ** ********** ** ****** **** and ****:
- "* ***** ** **. ** ** not **** * ***** ****** ** drives ****, *** **** **** ** be ** ********* **** **** **** temperature ******* ** ***** ******"
- "* ******** ** **** **** *+ years. *** **** ****** ***** ** find **** ****** ****-****** ** ** the ******** *****'* **** ****** *********** to *** ******** ** ******** ** or ******* *** ***** *********"
- "* ***** ** ** *** ***** number **** *** ***** ******** ***** full **** ***** ***********. **** ****** start ******* ** *** *** ** two ****** *** **** *** **** replacement. **** ** *** ******* *****, if ******* *********** **** ***** **-** for **** ** **** ** ** hold **** ****** *** ******** *** coming. ** **** ** **** *** servers ** **** *********** ***** ** preferably *** **** ********** ****** ***** life ****."
- "***** ****** **** ******* ***** * to * *****. *** **** ****** is ******* *********** *** ******* *******. We **** ******* ** *********** ************ running *** **** **** * ***** without *******."
- "******* * *****. ****** ** ********* rooms **** ******* ******** *** **** their ****** *********** - *.*. ****. Second ***** ** ********** **** *** tear."
- "*-* *****. **** ****** **** **** due ** ***********. **** *** **** the ** *******."
- "* ***** ** **. **** ******* occur ** ***** *** *** ************."
- "*-*+ *****. **** *** **** *** the **** ****** *******."
- "* ***** *** ** *********** (**** and ****)"
- "* ** *** ****** ********. *+ if ******** **********."
- "*+ ***** ******** *** ** **** of ***** ***********."
- "*-* ***. *** ** ******** *** and ************ ***********."
- "* *****. **** ** *** *** the *****."
- "**** ***** **** ** ****** *** systems ** ***** *.* *****, ***** ~4. **** *** ******** ***** (**** one) *** *** ****."
- "* - * **** ** *** normal. ******** *** ********* *** ** poor ******** ** *********, **** ** maintenance *** ****."
** ******* ******* ***** *** ************ *****, ** ****** ********* *********** *** cooling **********.
Normal **** ********
******* ****** ******** *** ******* **** and **** ** *** ****** ***** many ***** ** ******** **** *******, often ****** *+ ***** ** **** without *******:
- "******** **** *-* *****. ****** **** the ******** ******* ****** **** ** fail **** ****."
- "* *****+ ** *******, *** ******* seems ** ** ************ ****** *** just **** *** ****."
- "******* ****** **** **** **** ****. As * **** ** ***** ***** 5 *****, *** *** ****** ******* your **** ** * ***** *********/********* environment *** ***********."
- "********* ** *** **** ****** ***** failing ** *** * **** **** on ******* * ***** ***. ******* due ** *** ******* ***** ** impossible ** *** **** **** ** always ***** *******."
- "*** *** ****** **** ******** ** 1 ***** **** *** *** ** 24/7. ***** * *** ********* *** startups *** **** **** ***** ** fail. *** ***** ** ****** ***** i **** ** * ****** ** still ******* ***** ****, ** * think ***** ** ***** ****** ** normal ** ******* *** **** ****."
- "**** ***** ***** ** **** ***** 3 *****. ** ***** * ***** we ***** **** ******, ***** **** the **** ***** ** ***** ** crash. ****** **** * ******* ** lifespan ****"
- "* ** * ***** ***** ** be *** ****, ******** ** **** many **** ****** **** ** **** that. ***** ****** ** *** ******* indicator ** *******, *** ** ** have ****** **** **** ****."
- "*** ****, * *****, *** ***."
- "*-* *****. ***** ******** ****"
- "** **** *********** **** ***** *-* years ** **** ** ****** **** with ****** ******."
- "********* * **** ***** **** **** under ********* *** ***** ************* * years."
- "*-* ***** **** ********** *** **********."
- "* ** ** ***** ******* ** the *****, ** *** *** ********"
- "*** ***** *+ ***** ****** ** see ******* *** ** **** ***** they **** ****** ** **** ** less. ***** ** ** ****** ****** for ******* ****** *** ***** *** reached *** ** ****. "
Power ****** ******* ***** ********
*********** ******** ******** ******* ** ***** issues **** **** ******, **** ********* increased ***** **** **** ******* *** running *** ** ******* ****** ***/** UPS:
- "** ******* * ***** *** ***** majority ** ****** **** **** **** 5 ***** **** ****** *** **** than * ***** **** **** ******* in **********. **'* **/** ** *** drive ***** **** *** **** ***** a ***** ***."
- "* ***** *** *-* *****. **** often *** ****** ** **** ******* such ** ******."
- "*+ ***. ***** **** **** *** more ************ (*********** ** ***) **** tended ** **** ****** ******* ***** than ***** *** ***** *** ****** off"
- "******* ** * *****. ******** ********, NO *** *** ****** **** *****-*** and ********."
- "* ***** ***** ******* - ******* without ******* ****** **** ***** *** blocks / ******* ** *** ******"
- "* ***** *** *** ** * big *****. ***'* *** * ***** UPS. **** *** ****** *** ** heavy ***, ***** ***** ************ *** cause *********** **** ***** ******."
- "*-* *****, *****. *** **** ******, power ******."
- "* ***** ** *****. ******* ******** happen *** ** ***** *******."
*** ********** ****** ** ****** ******* backup *********, *** *** ******* ****** ***** *** ************ *****.
Servers ******** ****** **** ****** ****
**** **** *% ** ********* ***** that ********** ******* *** ****** *********** cycles ********* **** ***** ***** ** hard ***** *******. * *** *********** also ********* ************ *********** ** ******:
- "** ******* *******/******* *** ****** ****** before ****** ****. ******* ** *** failures ****** *** **** *** ** manufacturing ******"
- "* **** **** **** ****** **** last **** **** ** *****, *** generally ** *** ********** ********* **** require ******** ***** *-* *****."
- "*-* ***** ***** ** ** ****** average ** **** ******. *-* ***** on ***** ******. ** ********* *********** at *-* ***** ** ******** ********"
- "****** *** ***** ** ******* ****** up ********** * ********* *********** ** 75 ******* ** *** ***** ***. That ***** ** * ***** ** 3 ***** "
** ** ******* ********
******* *** ** ********* **** ***** Integrators ******** **** **** **** ** or ****** ***** ***** ******** ***** they ****** ***** ***** *** ********:
- "********* ** **** **** **** **** for * *****, *** ** **** not *** * ****** ***** **** at *** ** *** ******* ** have ********* (*** ** *** ****** have **** **** *** ** ****** though ** **** ** *** **********). I ** ********** ****** ******** ** fail ****, *** ** **** ***** have *** *** **** ******. "
- "* **** *** *** * ****** drive ***** * ******* ** ********. 6 *****"
- "* **** **** *** *** ******* in * ***** *** ** *** a *********** **"
- "*'* *** ****** **** ******* **** the ****** ****** ***** * ******* installing **** ******** *** ***** **** out"
- "* ***** ** ********, ** *** failures ***. "
- "** **** **** *** ** ******* last **** ** * ******* ********* 5 ***** *** ** ******* *******. It *** * ******** ***** **** for ***** *********. ***** **** ****, no ******** ** ***."
Comments (10)
UI
Undisclosed Integrator #1
Nov 02, 2018
Sean Patton
Nov 02, 2018Thanks for the feedback #1, however, those stats are from a data center application, while we are surveying integrators specifically in video surveillance which is much more applicable to IPVM. Also as a data center, they mention they are also upgrading constantly as drive sizes increase:
As noted, at the end of Q3 that we had 584 fewer drives, but over 40 petabytes more storage space. We replaced 3TB, 4TB, and even a handful of 6TB drives with 3,600 new 12TB drives using the very same data center infrastructure
SD
Shannon Davis
Nov 02, 2018Backblaze has great facts in their story but that is what I will call a utopia for hard drives. Hard drives in a data center aren't real word security system conditions. Unfortunately NVR's can't always be in a data center environment. Not as many recorders are being installed under the dusty, dirty pop infested front security desks as were in days past. These days NVR's get installed in much better conditions but often it is just a closet converted to a data room/lan.
I will agree the statistics are really good they provide and worth noting. For instance they replaced 3TB drives with 12TB drives. Cost wise this makes sense. In a data center environment the equipment they use is much easier to install the larger drives. Either the raid controllers in the system can adapt to the larger drives or updating the firmware so larger drives can be installed. This isn't always the case with NVR's out in the field.
U
Undisclosed #2
Nov 02, 2018[2018] percentages...were nearly identical to the IPVM survey responses from 2016...
2018 has 36% less drive failures in the first two years, which seems significant.
U
Undisclosed #3
Nov 02, 2018We can drink at work, no one really has to set any boundaries and to my knowledge hasn't been a problem. You'll see the occasional group in the afternoon indulging, or someone enjoying a beer at the end of a long day. We have a beer fridge and many people have a bottle of liquor on their desk. Someone usually makes a liquor store run before company meetings.
UE
Undisclosed End User #4
Nov 02, 2018to my knowledge hasn't been a problem
Except for the occasional post in the wrong thread ;)
U
Undisclosed #3
Nov 05, 2018JB
Jamie Bienenfeld
Nov 04, 2018I think it should be noted for the record (because a couple people have asked) that this was not posted by any York Employees.
U
Undisclosed #2
Nov 04, 2018...this was not posted by any York Employees.
I admit the first thing I thought after reading U3’s confession, was naturally “This must be a York employee”.
Thanks for clearing that up!
UM
Undisclosed Manufacturer #5
Nov 05, 2018HDD failure is an interesting topic.
There are some factors that come into play for any HDD:
The quality of the chassis
Workload
Handling of the HDD at installation (you would be shocked to see how clumsy some very large companies are on this.
The environment including, humidity, temp, and even pollution.
I would not rely on Backblaze for this on surveillance class HDDs.