SSD vs. HDD – The Missing Considerations

Rate this item
(0 votes)

Recently, there has been a lot written about Solid State Drives (SSDs) and their role in enterprise storage. These articles include several comparisons of solid state drives and mechanical drives in RAID arrays for enterprise applications. While most of these articles address several very key areas of comparison (cost, performance, capacity, power, cooling, reliability), they often neglect to consider data recovery and data destruction/asset disposal.  In the first part of this three-part series, I will examine data loss and recovery. In the second part, I will examine asset disposal, and in the third article, I will discuss steps that can be taken to minimize the risks.

Let’s tackle data recovery first. To understand how your choice of storage can affect the recoverability of data in the event something happens to your storage (and your backups), we need to take a closer look at how the data from a RAID array is written to the media.

With solid state disks, the data passes through the RAID controller to the individual SSDs that make up the array. As the data reaches the individual drives, it is passed to another specialized controller called a wear-leveling controller. The wear-leveling controller then determines to which NAND chip and block inside that chip the data is electronically written. The location of the data on the NAND chips changes constantly to help protect the NAND chips from wearing out.

With mechanical disks, the data is passed from the RAID controller to the individual disks. The data is then magnetically written by the read/write head to the platters in the drives as bits. It is important to note that the data is written in a very specific pattern on the platters. Specific bits of data are stored in consistent locations. As an example, when block 10 is written to the platter, barring any defects, the block stays in the same location on the disk platters. The data can then be read from the platter by going back to the same location on the platter and reading the magnetic orientation of the bit stored there. When changes are made to the data, the orientation of the bit may change, but its location on the platter does not change.

In short, the major differences between the media types are:

  1. Electronic vs. magnetic writes
  2. Static vs. dynamic storage locations

Most established data recovery specialists have had years to perfect their data recovery techniques for mechanical drives and some have very sophisticated methods for dealing with RAID controllers. Parts can be replaced and media damage can be overcome to get access to the raw data (basically creating an image of the data on the physical disk). Once the raw data is recovered, software can be used to virtualize the RAID controller. The data recovery specialist can virtually reassemble the array, then the logical volume can be rebuilt, errors can be corrected and the data can be recovered. Another difference to note is that individual disk failures on mechanical drives are often predictable and data loss can be prevented or minimized.

SSD is a newer technology and very few data recovery specialists have the ability to handle the RAID and the SSD layers in order to put the data together in the event of a failure. In some cases, parts can be replaced to overcome failures. To overcome media damage, however, the NAND chips often need to be removed and imaged independently. This requires specialized tools and software and usually a significant investment in R&D, as data is stored in a different way on each drive. The raw data bits then need to be reassembled into a usable format, which is much more challenging than simply imaging the disk by overcoming physical/electrical issues or media corruption like you would find in mechanical drives. Once that is complete, the RAID is then reassembled, the logical volume is rebuilt, any damage is repaired and then the data is recovered. Individual disk failures are often unpredictable and special care needs to be taken to prevent data loss.

In conclusion, when evaluating solid state against traditional hard disks, make sure to take into consideration the possibility of data loss and the need for data recovery. It could mean the difference between meeting the requirements for enterprise applications and disaster. For recovery information about specific RAID controllers or specific drives and their recoverability before you purchase them, contact your local data recovery specialist.

Data Recovery Expert

Viktor S., Ph.D. (Electrical/Computer Engineering), was hired by DataRecoup, the international data recovery corporation, in 2012. Promoted to Engineering Senior Manager in 2010 and then to his current position, as C.I.O. of DataRecoup, in 2014. Responsible for the management of critical, high-priority RAID data recovery cases and the application of his expert, comprehensive knowledge in database data retrieval. He is also responsible for planning and implementing SEO/SEM and other internet-based marketing strategies. Currently, Viktor S., Ph.D., is focusing on the further development and expansion of DataRecoup’s major internet marketing campaign for their already successful proprietary software application “Data Recovery for Windows” (an application which he developed).


  • Comment Link Beth Saturday, 13 January 2018 19:02 posted by Beth

    My brother recommended I would possibly like this web site.
    He was once totally right. This publish truly made my day.
    You cann't imagine simply how much time I had spent for this info!
    Thank you!

  • Comment Link Mia Friday, 12 January 2018 16:39 posted by Mia

    I really like your blog.. very nice colors & theme.
    Did you make this website yourself or did you hire someone to do it for you?
    Plz answer back as I'm looking to create my own blog
    and would like to find out where u got this from.

    appreciate it

  • Comment Link Aundrea Friday, 12 January 2018 00:21 posted by Aundrea

    Hey there! I know this is kinda off topic however I'd figured I'd ask.
    Would you be interested in exchanging links or maybe guest writing a blog post or vice-versa?

    My site covers a lot of the same topics as yours and I feel we could greatly benefit from each other.
    If you happen to be interested feel free to send me an e-mail.
    I look forward to hearing from you! Wonderful blog by the way!

  • Comment Link Alissa Friday, 05 January 2018 14:23 posted by Alissa

    I think the admin of this web site is truly working hard
    in favor of his web page, because here every material is quality
    based stuff.

  • Comment Link Darin Friday, 05 January 2018 05:58 posted by Darin

    hello!,I really like your writing very much!
    proportion we keep up a correspondence more about your post on AOL?
    I require an expert in this space to unravel my problem.
    May be that is you! Looking forward to look you.

  • Comment Link Lynette Sunday, 31 December 2017 08:13 posted by Lynette

    Fine way of explaining, and pleasant post to take facts
    about my presentation subject matter, which i am going to
    convey in institution of higher education.

  • Comment Link Norberto Monday, 27 November 2017 05:07 posted by Norberto

    I am actually grateful to the holder of this web site who has
    shared this impressive article at at this time.

  • Comment Link Brianna Monday, 13 November 2017 21:10 posted by Brianna

    To safeguard family members from damage?

  • Comment Link Joey Monday, 13 November 2017 06:04 posted by Joey

    I'm amazed, I must say. Rarely do I encounter a blog that's
    both equally educative and amusing, and let me tell you, you have hit
    the nail on the head. The issue is something that not enough
    folks are speaking intelligently about. I'm very happy that I found this in my
    hunt for something regarding this.

  • Comment Link Stephany Friday, 03 November 2017 21:16 posted by Stephany

    Hello Dear, are you genuinely visiting this
    site daily, if so afterward you will without doubt obtain good experience.

Leave a comment

Make sure you enter the (*) required information where indicated. HTML code is not allowed.