The Proper And Wrong Way To Recover RAID Arrays

Have a RAID server difficulty and need to recover that RAID system as quickly as possible? When seeking RAID data recovery, the choices are very simple. You can choose to go the smart, correct way, and you can choose the hassle and high cost of moving in the wrong direction. The correct way seems like it would be the easy, clear choice, as it slashes general downtime and cuts costs. Still, many people choose the wrong way when they need to recover RAID systems, and it costs not only money, but critical files. This article should help you decide.

How Critical Is Your Lost Data?

When looking to recover RAID arrays in the instance where more than a single drive has failed, the key to how to handle it is in the data itself. Are you using a RAID 0 array because it helps your system perform better when you’re playing Call Of Duty? Better to consider simply rebuilding the RAID array from scratch. RAID repair rarely comes cheap, as it is such a specialized job that many hard drive recovery shops actually do not provide it. So if your machine doesn’t really have anything absolutely key to your life, it may be best to just bite the bullet, purchase some new hard drives and start again.

The other example scenario is that the failed RAID you’re working with is running an Oracle database used by your company’s sales people thousands of times per day. Or running a CRM system that is crucial when communicating with your customers. Situations like these are hand built for professional RAID recovery shops because you simply cannot afford a “we’ll see what happens” solution. If your company’s very business operations are slowed dramatically because of a failed system, do not bother attempting to recover the server yourself. It is time to call in a professional.

Quick Turnaround Wins The Day

Each minute may seem like hours when a mission critical RAID server has gone kaput. And in fact, when you multiply the number of stationary workers by those minutes, it may actually be hours. It’s never that hard to find a data recovery shop on the web, of course, but if your recovery is ultra-important, consider web searches for “immediate RAID data recovery” or “overnight RAID recovery”. The industry does have a common term for express-type services, which is often known as “expedited”. However, a tiny percentage of companies actually offer emergency repair services that can have your fixed server back in your hands within a single day or less. While the cost of these “ultra-expedited” services are higher than standard, it may be worth it if your system is killing productivity for the organization as a whole.

A List Of Do Not’s For RAID Recovery

There are specific things IT administrators will try before contacting a repair shop which may help not only the repair, but may actually fix the issue. Here are just a few of them:

Randomizing RAID Drive Order – If you have a double hard drive drive loss in your array, or even a single one, ensure you keep the array as is. Moving drives around the enclosure can actually enable your controller to destroy data permanently. Keep things as they were, and all will be good.

Do a Connections-Check – Although it is the most obvious, and easy technique out there, many people do not bother to check for hardware connection strength to make sure everything is correctly placed. Although it doesn’t happen very often, paying to ship out a mission critical server only to discover a cable was improperly connected is the most embarrassing thing to happen to a tech. Don’t make that mistake!

CHKDSK, The Enemy Within – Yes, Windows has a simple disk checker called CHKDSK that is there to help you find errors. Problem here is that CHKDSK was NOT created for RAID servers or multiple hard drive setups. Save yourself some hassle and permanent overwrites by avoiding it altogether!

No matter your server issue, professional hardware requires professional help when hard drives fail. Remember this the next time you attempt to recover RAID arrays.

Leave a Comment

Previous post:

Next post: