Studying for the A+, Network+ or Security+ exams? Get over 2,600 pages of FREE study guides at CertiGuide.com!|
Join the PC homebuilding revolution! Read the all-new, FREE 200-page online guide: How to Build Your Own PC!
NOTE: Using robot software to mass-download the site degrades the server and is prohibited. See here for more.
Find The PC Guide helpful? Please consider a donation to The PC Guide Tip Jar. Visa/MC/Paypal accepted.
|Take a virtual vacation any time at DesktopScenes.com - view my art photos online for FREE in either Flash or HTML!|
Tired of the boss? Ever wanted to be an independent freelancer? Not sure how to get started?
The all-new Online Freelancing Guide can help. Tons of useful info, and it's free! Join the online freelancing revolution today.
[ The PC Guide | Systems and Components Reference Guide | Hard Disk Drives | Hard Disk Performance, Quality and Reliability | Redundant Arrays of Inexpensive Disks (RAID) | RAID Concepts and Issues | General RAID Concepts ]
Physical and Logical Arrays and Drives
The fundamental structure of RAID is the array. An array is a collection of drives that is configured, formatted and managed in a particular way. The number of drives in the array, and the way that data is split between them, is what determines the RAID level, the capacity of the array, and its overall performance and data protection characteristics. Deciding what types of arrays to set up, and how to configure them, is the first thing you do when setting up a RAID implementation.
Understanding arrays and drives can get awfully confusing because high-end RAID systems allow for such complexity in how they are arranged. To get a better handle on this, let's look at the "hierarchy" in which data in a RAID system is organized:
Notice how we start with drives, go to arrays, and then end up back talking about drives. Isn't that nice and confusing? :^) This occurs so that the array management is "hidden" from the operating system. (Under software RAID a special part of the operating system does this management, hiding the arrays from the rest of the software.) The really confusing thing is that the terms above, which are similar-sounding enough, are often used loosely. Since most RAID setups consist of one physical array made into one logical array made into one logical drive, the term "logical array" is sometimes used interchangeably with "physical array" or "logical drive". Ugh.
As you can see, better RAID controllers give you all the "rope" you need to hang yourself when it comes to defining arrays. How many logical arrays and drives you should define depends entirely on the RAID level(s) you are going to be used. But in general, when defining arrays and drives, you should always keep in mind the "KISS" rule--keep it simple. For most reasonably simple applications, creating a single logical array for each physical array is the best way to go. If you need multiple logical arrays for special applications, using separate physical arrays for them may make management simpler than having two arrays sharing physical arrays and therefore, sharing physical drives.