Manos was very thorough at explaining the difference between imaging and RAID configuration.
I'll take a moment to address the RAID-specific options available to you.
RAID exists in two approachs:
Software RAID. Software RAID leans on the operating system to pull the strings. It will impose a tax on your CPU. This is fairly minimal in modern PCs. It's widely available on many modern motherboards. See the motherboard specifications for details. In particular, the Intel Core2 Duo/Quad, i5, and i7 compatible motherboards have a chip series called the ICHxr where 'x' is 7 through 10. Any of these chips support a fantastic RAID solution called Intel Matrix RAID. More on this later.
Hardware RAID. Hardware RAID utilizes a dedicated piece of equipment to handle the mirroring. It will not utilize your CPU any more than a lone disk would. Hardware RAID typically supports more RAID configurations. More on this later. However, hardware RAID can become very expensive.
Which one is for me? For the consumer market, this is almost invariably going to be Software RAID. Cost is the main reason, here: Software RAID imposes a smaller startup cost and may be a smaller recovery cost in the event of hardware failure.
What if I replace my Motherboard? My CPU? The CPU will have no bearing on either software or hardware RAID solutions. In event of software RAID using the onboard controller (such as ICH10r), as long as you perform a like-4-like exchange, it'll be problem-free. Also, the ICH series chips are backwards compatible. Downgrading to an ICH7r later will allow you to keep your RAID intact.
Under the hood. Keep in mind that the RAID controller disguises itself as a hard disk: In otherwords, the operating system doesn't see 2 disks configured in such and such way... It sees a single hard disk; what happens under the hood is soley up to the RAID controller.
Types of RAID. Under the hood, the RAID controller may be configured in to a variety of types, called levels. Different levels offer a blend of performance and data-safety. I'll briefly cover the levels available to most software solutions, and why you might want them.
RAID 0: Striping array. Files are sliced up in to smaller chunks and divided amongst the disks in the array, reducing the amount of mechanical work required. +Read/Write performance. Can survive 0 disk losses before information is lost.
RAID 1: Mirroring Array. Files are duplicated amongst disks in the array, increasing mechanical work but giving "real-time" data-safety. -Read/Write performance. Can surive n-1 disk losses, where 'n' is the number of disks in the array.
RAID 5: Striping with distributed parity. Like RAID 0, files are split for performance gains. In addition, special parity data is spread across all the disks in the array which allows recovery in the event of a single disk failure. Requires no less than three disks. +Read/Write performance. Can survive 1 disk loss with severe performance penalties until the disk is replaced.
RAID 10/01: Combines RAID 0 with RAID 1 for the best of both worlds. Downside? Requires at least four disks. Can survive a single disk loss without any appreciable performance penalty prior to replacement. A second loss will result in data loss.
Intel Matrix RAID. I'll cover this briefly. Matrix RAID is available on any motherboard which has an ICH7r, 8r, 9r, or 10r chipset. Most motherboards which socket the Core2 Duo, Core2 Quad, i5, or i7 CPUs will have one of these chipsets.
Matrix RAID is different from other software RAIDs in the fact that it is no longer mandatory to use an entire disk volume in a RAID. Instead, you may use only a portion, pre-defined, for a particular RAID.
Why is this important? Say you have 2x 1.0TB disks. You may take the first 50 GB of each and place them in RAID 0 for a fast operating system and use the remaining ~900 GB in RAID 1 for data safety.
Unless you're a real performance hound, this is probably not going to make much of an impact for you. Keep it simple and stick to entire disk volumes.
RAID is not a backup.– quack quixote Dec 9 '09 at 15:08RAID is not a backup!! – quack quixote Dec 11 '09 at 9:13