We don't think that comparison of tools given by the vendors vs competitors is a good business practice. However, since YEC compares DeepSpar Disk Imager (DDI) with their own products on their web-site (
http://www.yec-usa.com/products/faqs/de ... aq.html#a4) stating that "the DeepSpar offers a few extra features for 2 or 3 times the price of the King Demi" (without mentioning exactly what features they are talking about), we would like to clarify here what some of those features are. Here is what they say on the web-site at the time of this post (just in case they change anything later):
Quote:
How does the King Demi match up to the DeepSpar?
The Deepspar offers a few extra features for 2 or 3 times the price of the King Demi. End result is usually the same because data extraction methods are very similar. Aside from the price difference the Deepspar requires a dedicated workstation while the King Demi does not. The King Demi works as a stand-alone unit with optional PC connection via USB. While connected to the King Demi by USB, the workstation can be used for other tasks. Please inquire for details.
First thing to mention is that the price difference is under 2 times and not "2 or 3".
Now, before going over the features we would like to say that to compare any imaging tools you have to go through the issues that need to be handled during a data recovery imaging process and then check how each tool addresses those issues. So, the following is based on the most critical issues of data recovery imaging.
1) The drive is degrading under intensive reading and may fail during the imaging process.To address this issue the DDI identifies and skips problematic areas of the drive during an initial pass, while retrieving good areas only. As soon as the first pass is done you can take the image drive and check whether the files you are looking for belong to those retrieved areas (which is often the case and so there is no need to dig into skipped bad areas spending days in trying to recover sectors you don't need). If some user data is located in the skipped areas you can move the image drive back to imaging and execute extra passes that are geared to "more digging" imaging algorithms while retrieving only those sectors that were previously skipped. This is done automatically, since the DDI has a map of each sector status and so it knows exactly which sectors were read successfully, therefore it never tries to retrieve sectors that were copied before. This means that you can stop the imaging process at any time, modify the imaging parameters, and continue the imaging process. The Ninja doesn't have this capability, therefore you have to manually instruct it what area needs to be imaged and it will read that entire area ignoring the fact that some of the sectors in this area were previously retrieved. An extra drawback of this approach is that if the drive degraded while imaging then previously retrieved sectors may be overwritten with corrupted data.
2) Imaging can take a long time and results are unknown until it’s done. You may be spending days or even weeks imaging the drive and at the end of this process you may realize that no useful data has been imaged, e.g. most of retrieved sectors have corrupted data or no data at all.The DDI is a visual, fully interactive imaging environment. You see exactly what's happening during the imaging process: what type of sector errors you get, how long it takes to read any block/sector, whether a sector layout has any patterns which help identify the physical nature of issues, such as media scratches, and more. You also see exactly what kind of data is being imaged by: 1) viewing retrieved hex data on-the-fly, which can be used to identify unused space (zero values), and 2) watching for real time counters of imaged files of known types (such as pictures or Microsoft Office files) and file system elements (such as MBR, Boot Sectors and MFT records/indexes). So, you have a very clear idea of the imaging process, which gives you ability to control imaging on-the-fly. For example, you can jump over certain areas you are not interested in without stopping the imaging process or you can stop imaging, fine tune your imaging algorithm, and then continue. This is a completely different environment compared to the Ninja, which doesn't provide you with such details about the imaging process and so you can't control imaging the way you need to. This clearly results in longer imaging times and less data recovered.
3) Different drives have different read instability issues and so one imaging algorithm may work well on one drive, but fail on the other.The DDI has not only various imaging parameters, i.e. read commands to use, sectors to process, data transfer mode to apply, Read Sector Timeout and such, but it also lets you create your own algorithm using Event-Action definitions. You can specify exactly how you want to process sectors with particular problems. For example, you may specify to skip bad sectors with IDNF or ABRT errors, but process sectors with UNC errors by a different command, e.g. Read Ignoring ECC (Read Long). Or you can instruct the DDI to reset the drive and jump over certain number of sectors if it gets a specified number of consecutive sectors with no data retrieved. By using such Event-Action definitions you can customize imaging algorithm as much as you need to handle particular problems of the drive so that you can get more data in less time. The Ninja does not let the user customize the imaging algorithm in such ways therefore you just have to rely on its hardcoded algorithm and hope for the best…
4) Different heads of the drive have different reading ability and some heads may even be so weak that they can't read most of the data from their disk platter.The DDI has the functionality to test individual heads and to image data using specific heads so that you can identify which heads are weak and unselect them during an initial imaging pass. As soon as all sectors that belong to the good heads are copied, you can image data from weak heads. This lets you: 1) diagnose weak/failed heads, and 2) read all good data off the drive first so that it will not fail on you due to intensive reading process caused by accessing data on weak heads. The Ninja doesn't have heads related functionality.
And lastly, regarding the fact that the DDI requires a dedicated workstation. The only purpose of the PC is to make imaging process visual and interactive. You can not achieve this by using a dedicated device with a small display and a few buttons. Also, our DDI supply package now includes a motherboard and CPU. Considering the fact that the system is actually booting from the DDI, the only things you need to add to the workstation is a case, any DDR2 stick of RAM, PSU, keyboard, and an inexpensive monitor. In addition, each DDI package includes life time free software updates. Our clients who bought this product three years ago still have access to exactly the same features as anyone buying the unit nowadays and we didn’t charge a single cent for this, while YEC do charge their clients for updates that are released more than one year since the purchase.
Anyhow, without going into sales points, and just to summarize the technology - the DeepSpar Disk Imager is a visual, interactive, multi pass imaging environment with drive vendor specific capabilities, such as imaging by heads and disk preconfiguration, while the Ninja is a single pass dedicated imaging device with some embedded data recovery functions.
P.S. You can find more information about Data Recovery Disk Imaging issues and techniques in the following whitepaper: "Disk Imaging: A Vital Step in Data Recovery" (
http://www.deepspar.com/pdf/DeepSparDis ... paper3.pdf).
Sincerely,
DeepSpar Data Recovery Systems