Computer Science Labs
Need Help?

Call: 0871 2316806
or Email Us

RAID Recovery:

8 Disk RAID 10 Server

Undertaking System Restoration and Data Recovery from a failed RAID server system is a complex process and requires a high level of expertise and experienced technicians.

Technical Expertise.

Our technicians have over 10 years experience in System Restoration and Data Recovery from failed RAID configured servers. We have also undertaken dedicated research and development to enable a fast efficient and successful implementation of our Emergency Support Service. Computer Science Labs developes and maintains its own in-house unique RAID recovery software; Our RAID 520 suite, enables us to maintain an outstanding Server and NAS Recovery Rate better than 90% !

Service call

Our Customers.

Computer Science Labs is THE preferred Data Recovery provider of many household name companies, international corporations, computer manufacturers and vendors that demand a highly professional and reliable partner service.


We recover data from all major operating systems including:- Windows NT Server, Windows 2000 Server, Windows 2003 Server, Windows 2008 Server,Windows Small Business Server(SBS), Windows Exchange Server, Windows SQL Server,MAC OS X Server, UNIX and Linux Servers.

Emergency Support Service:

Computer Science Labs is "THE" industry leader when it comes to Emergency Data Recovery and Emergency System Restoration from failed Business Server and NAS systems with inaccesible or faulty hard disk drives and hardware"

With over 12 years experience in RAID configured Servers and NAS systems repair,recovery and restoration we can deliver "life-saving" results, even when certain unsuccessful remedial attempts have occurred before we were called.

We recover data from failed RAID Servers, SAN., and NAS., with a high degree of success.

Technical assistance offered by the RAID system manufacturer can be far worse than merely frustrating, it can be altogether dangerous to the "life" of your data. Manufacturers will often assume that your data is backed up and that its loss from the operational system is not an issue They really have no reason to be trained in the preservation of your data.

With pressures from all directions in your own environment, added to the complexities of RAID 5; RAID 6; RAID 10, mistakes, confusion and troubles can be difficult to avoid.

RAID Recovery Process:

Our RAID Data Recovery processes and technical expertise take the risk out of handling failure situations. Our Step-By-Step process features:

  • Immediate technical support.
  • Fixed cost: diagnosis, disk repair, config rebuild.
  • Point to Point secure courier
  • In-Lab hard disk repair.
  • Hard Disk Drive cloning.
  • Data recovery costs and timescales.
  • File system repair
  • File Listings
  • Data retrieval and storage.
  • In-Lab data testing (where possible).
  • Data restoration.
  • On Site Support on request.
  • We support you and your technical staff every step of the way !

    "If you have had a problem with your server and had to reload the OS. Computer Science Labs can restore using your backups or even a bare metal restore from an old drive. It doesn't matter if it has a control panel or not, we can get the job done and get you up and running as soon as possible!"

    Stuff that helps you find this page and the best possible support opportunity:

    What is a RAID Server?

    RAID is an acronym for Redundant Array of Inexpensive Disks. By combining a number of hard disk drives into a single unit, large amounts of data can be processed efficiently . This method offers fault tolerance (the ability of a system to continue to perform functions even when one or more hard disk drives have failed) and higher protection against data loss than a single hard drive.

    Need for RAID?

    RAID provides real-time data recovery when a hard drive fails, increasing system uptime and network availability while protecting against loss of data. Another advantage of the system is that multiple disks working together increase overall system performance.

    Any individual or company could benefit from having a RAID RECOVERY system in place.

    Different Levels of RAID.
    There are several different levels of RAID available. Each level offers various advantages in terms of data availability, cost and performance. Your best bet is to assess your needs in order to determine which level works best for you.

    Level 0:

    Striped Disk Array without Fault Tolerance: Provides data striping (spreading out blocks of each file across multiple disk drives) but no redundancy. This improves performance but does not deliver fault tolerance. If one drive fails then all data in the array is lost.

    Level 1:

    Mirroring and Duplexing: Provides disk mirroring. Level 1 provides twice the read transaction rate of single disks and the same write transaction rate as single disks.

    Level 5:

    Block Interleaved Distributed Parity: Provides data striping at the byte level and also stripe error correction information. This results in excellent performance and good fault tolerance. Level 5 is one of the most popular implementations of RAID.

    Level 6:

    Independent Data Disks with Double Parity: Provides block-level striping with parity data distributed across all disks.

    Level 0+1:

    A Mirror of Stripes: Not one of the original RAID levels, two RAID 0 stripes are created, and a RAID 1 mirror is created over them. Used for both replicating and sharing data among disks.

    Level 10:

    A Stripe of Mirrors: Not one of the original RAID levels, multiple RAID 1 mirrors are created, and a RAID 0 stripe is created over these.

    RAID S:

    EMC Corporation's proprietary striped parity RAID system used in its Symmetrix storage systems.

    RAID Rebuild and Recovery.

    RAID rebuilds re-create data on RAID arrays when disks fail. But how do RAID rebuilds work, what is pre-failure and post-failure replacement, which RAID levels rebuild the quickest and what's the best way of reducing RAID rebuild times?

    RAID systems protect data against a hard disk failure, allowing the array to copy data from the failed disk to a spare drive while it is being replaced.

    A physical drive failure such as a damaged platter or a broken or faulty printed circuit board should not be confused with a logical hard drive failure. Logical failures are caused by firmware, file system or data corruption and cannot be cured by the replacement of a disk drive.

    There are two main instances where a hard drive will be replaced in a RAID array:

    Pre-failure replacement
    Post-failure replacement

    Pre-failure replacement is when an array senses that the hard drive will fail shortly and marks it for replacement. If a hot spare is available, a block-for-block copy will be carried out from the old drive to the hot spare, which will become the active drive. For many arrays, an alert will be sent for the old drive to be replaced.

    Post-failure replacement takes place when the hard drive becomes faulty unexpectedly before a pre-failure replacement can take place. The data on the failed drive must be rebuilt from the parity data on the remaining active drives and written to a hot spare. Post-failure replacement takes considerably longer due to the calculations that must take place to rebuild the data. Pre-failure drive replacements are much quicker than post-failure replacements. Technically, they don't involve RAID rebuilds as the data is copied directly from the old drive to the new drive. To mitigate the risk of drive failures, you should always try to ensure that the RAID array you use is capable of pre-failure replacements.

    Once a post-failure replacement is necessary, the RAID rebuild time for a particular drive technology and speed is dependent on three factors:

    The size of the drives in the RAID set.
    The number of drives in the RAID set.
    The priority given on the array to rebuild activities.

    The size of the drives is a fairly obvious factor, as it will take a lot longer to replace the data on a 600 GB drive than it will on a 72 GB drive. The number of drives also affects the rebuild time as the array has to read from each remaining drive to determine the data to put on the replacement drive. A general rule is that the more drives there are in the RAID set, the longer the rebuild time will be. The priority of the rebuild process can be set against host I/O on most RAID arrays. The higher the priority given to the rebuild process, the faster it will be, although this will result in degraded host-access performance. There are a number of popular RAID levels and the rebuild times differ for each. Here are a few pointers when considering which RAID level to implement:

    RAID 0: Contrary to what you may expect, there is no redundancy in a RAID 0 environment. If a drive fails, your data will be inaccessible.

    RAID 1: This is a mirrored pair and has a fast rebuild as data is copied block for block from the source to the target.

    RAID 10: RAID 10's mirrored stripe sets rebuild at a pace similar to that of RAID 1.

    RAID 5: Single-parity RAID 5 takes longer than mirroring as data has to be read from each drive in the set, with rebuild times taking longer the more drives there are.

    RAID 6: RAID 6's double parity takes longer than RAID 5 to rebuild, although rebuild times are less of a consideration as two drives can fail without data loss.
      © Copyright Computer Science Labs (2019) Terms & Conditions Sitemap