Home > Raid > RAID 5 vs RAID 1

RAID 5 vs RAID 1

September 21st, 2009

Raid 5 VS Raid 1 What if your computer memory system crashes, and you don’t have any backup of your data stored elsewhere? Crashing of the hard drive puts one in a difficult situation. The RAID (redundant array of independent disks) data storage system is designed in such a way that data recovery is possible even if storage devices fail. The RAID disks (tape disks or magnetic disks) are so arranged that it allows maximum redundancy (mirroring or repetition). Some RAID architectures are designed for faster read operation, some for faster write operation, while some are designed for both faster read and write operations. Hence, we not only need to understand RAID 5 vs RAID 1 comparison, but each level of RAID needs to be understood. Following are a few points on RAID 5 vs RAID 1 comparison.

RAID 1 Explained
The RAID level 1 architecture uses the concept of mirroring. This means that errors and failures of all disks can be accommodated in the disk array, except one. However, there can be maximum two disks only. RAID 1 is designed for faster read operations than write. RAID 1 recovery is only possible when one of the two disks have failed. While using any modern multi-threaded operating system (Windows or Linux), RAID 1 array gives better performance for split seeks, that is, access of same memory location by two different users. There needs to be a RAID 1 controller for each disk in this array for best performance.

RAID 5 Explained
In the architecture of RAID 5 disks, the array is so arranged that failure of one disk can be kept hidden. If the second disk fails before the replacement of the first, then there cannot be any data recovery. The maximum number of disks that can be accommodated in the architecture are three, out of which one is kept as a backup. When the first disk fails, the backup disk springs into action and data recovery is possible. In RAID 5, a failed disk needs to be replaced as early as possible. RAID 5 performance suffers whenever there is a read-modify-write operation.

Recovery in RAID Disks
RAID 5 as well as RAID 1 have one common assumption. Every failure is independent of the other. However, this is not completely true. Due to the mechanical nature of the storage disk, failure of one disk may mechanically be dependent on the other. There are techniques such as, parity resynchronization or stale sub-disk recovery, where recovery is possible but these are restricted to specific scenarios. Data loss due to software reasons (a virus or accidental deletion) is however a different issue. The data recovery techniques used in RAID disks and recovery through data recovery softwares are not directly related.

Advantages of RAID 1

  • Redundancy of the data is hundred percent.
  • Data need not be rebuilt in case of a single disk failure.
  • Even though there are two disks in the array, the rate at which data gets transferred is that of a single disk.
  • Very easy to understand and implement.

Advantages of RAID 5

  • RAID 5 has an inbuilt load balancing mechanism.
  • RAID 5 is ideally suited for database applications which are heavily read oriented.
  • Applications that perform random read operations work well on RAID 5.
  • High fault tolerance typically requires additional disk space. RAID 5 is highly efficient in that scenario.

The seven levels in RAID have been developed gradually over a period of time. Different arrays are suited for different situations. The above RAID 5 vs RAID 1 comparison may be helpful in understanding these disk array structures.

Categories: Raid Tags: , ,
  1. wand
    October 6th, 2009 at 21:43 | #1

    I believe 3 drives is the minimum Raid-5 configuration, not maximum.

Comments are closed.
/1.1 302 Found Connection: close Date: Mon, 06 Feb 2012 19:47:22 GMT Server: Microsoft-IIS/6.0 X-UA-Compatible: IE=EmulateIE7 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Location: /404.html?aspxerrorpath=/getcode.aspx Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 162 Object moved

Object moved to here.