Comments on: IT Professional and The Amazing Powers of Incompleteness http://itprofessional-mastermind.com/blog/success-stories/it-professional-and-the-amazing-powers-of-incompleteness/ From the Trenches - IT Courses | IT Career Tips Sun, 19 Jun 2011 18:21:11 +0000 hourly 1 http://wordpress.org/?v= By: Glenn West http://itprofessional-mastermind.com/blog/success-stories/it-professional-and-the-amazing-powers-of-incompleteness/comment-page-1/#comment-25 Glenn West Fri, 05 Jun 2009 10:40:07 +0000 http://itprofessional-mastermind.com/blog/?p=64#comment-25 I agree. Having a forensics background. That data can be recovered. In the case you have stated, something as simple as replacing the circuit board of the drive may recover all the data. I would put a new "set" of disks in the RAID, taken the set. And had a disk repair company repair the disk. If you got a week, I'm sure you could have recovered most if not all the data. Since the problem was more electrical in nature. Second, your data could have walked out the door. Even a few sectors could give a hacker information that could be valuable. Replacing the circuit board on a failed drive doent even require high teck lab. Just the willingness to "break" apart a good drive of like model. I agree. Having a forensics background. That data can be recovered. In the case you have stated, something as simple as replacing the circuit board of the drive may recover all the data. I would put a new “set” of disks in the RAID, taken the set. And had a disk repair company repair the disk. If you got a week, I’m sure you could have recovered most if not all the data. Since the problem was more electrical in nature. Second, your data could have walked out the door. Even a few sectors could give a hacker information that could be valuable.

Replacing the circuit board on a failed drive doent even require high teck lab. Just the willingness to “break” apart a good drive of like model.

]]> By: JackFlash http://itprofessional-mastermind.com/blog/success-stories/it-professional-and-the-amazing-powers-of-incompleteness/comment-page-1/#comment-21 JackFlash Sun, 24 May 2009 14:16:50 +0000 http://itprofessional-mastermind.com/blog/?p=64#comment-21 Juhana, my friend, Always good to look at issues with like-minded IT PROs as you... Indeed I forgot to mention that one has to get rid of the data on bad disks, even when they are a total waste... I always either pay for keeping the failed disk on site and de-comissioning it using our own procedures (disk cruncher...). I also resolve complex situations by digging into the question - "What is the right problem we should be solving now". Yours, Jack. Juhana, my friend,

Always good to look at issues with like-minded IT PROs
as you…

Indeed I forgot to mention that one has to get rid of
the data on bad disks, even when they are a total waste…

I always either pay for keeping the failed disk on site
and de-comissioning it using our own procedures
(disk cruncher…).

I also resolve complex situations by digging into
the question – “What is the right problem we should
be solving now”.

Yours,

Jack.

]]> By: Juhana Siren http://itprofessional-mastermind.com/blog/success-stories/it-professional-and-the-amazing-powers-of-incompleteness/comment-page-1/#comment-19 Juhana Siren Sun, 24 May 2009 11:21:05 +0000 http://itprofessional-mastermind.com/blog/?p=64#comment-19 You are definitely on the right track here. In my opinion, the question is about recognizing the real problem or problems. I see two principal problems here. First, there is the issue of data protection. A disk, by its very purpose, contains data; when a disk fails, for whatever reason, that data doesn't cease to exist, and it can be recovered by whoever has the means to do it. There are failure modes where the data is intact and can be very easily recovered. So, broken disks must be treated just like any data: you either store them properly or dispose of them properly. The other problem is that of potentially unreliable backups: you may want to keep the failed disks as a last resort in case the backups turn out unreadable. Solving the first problem provides a solution to the second as well. As to your original subject, knowing how far to go with a solution is a skill in and of itself. We've all had our share of recurring problems that won't go away without a clean install, and nobody wants to create new ones. Then again, it's a waste of effort to fix something that isn't a problem. That's why it's so crucial to ask "What is the problem?" Juhana Siren - consultant - Apertas Solutions Oy You are definitely on the right track here. In my opinion, the question is about recognizing the real problem or problems. I see two principal problems here. First, there is the issue of data protection. A disk, by its very purpose, contains data; when a disk fails, for whatever reason, that data doesn’t cease to exist, and it can be recovered by whoever has the means to do it. There are failure modes where the data is intact and can be very easily recovered. So, broken disks must be treated just like any data: you either store them properly or dispose of them properly.

The other problem is that of potentially unreliable backups: you may want to keep the failed disks as a last resort in case the backups turn out unreadable.

Solving the first problem provides a solution to the second as well.

As to your original subject, knowing how far to go with a solution is a skill in and of itself. We’ve all had our share of recurring problems that won’t go away without a clean install, and nobody wants to create new ones. Then again, it’s a waste of effort to fix something that isn’t a problem. That’s why it’s so crucial to ask “What is the problem?”

Juhana Siren – consultant – Apertas Solutions Oy

]]>