A Fresh Backup (existing data only): If you're installing and
configuring hardware RAID on a fresh system with no OS (your best
option), or are adding disks for a separate array, skip this.
Otherwise, back up your important data. Best practice is to have three
copies of your data: the original, a backup, and a backup of the
backup, preferably offsite.
If you have existing data that you want on the array, you'll need to
back it up, then restore it from a backup you make before creating
your array--a process that writes new data to your hard drives
regardless of what's there. This is not necessary with Windows
software RAID 0, however, it's far faster than letting Windows re-sync
(copy the data to) the mirror in the background.
Transferring an existing operating system is tricky, and with older
versions of Windows, sometimes impossible. See "Transferring Existing
Windows Installations to RAID" on the next page for instructions.
Windows Software RAID: Starting with Windows XP, Microsoft integrated
RAID functionality into its operating systems. What type depends on
the flavor of Windows:
Windows XP allows spanned volumes (one volume over two or more disks), aka JBOD.
Windows Vista Ultimate allows JBOD and RAID 1 striping.
Windows 7 Home allows JBOD and RAID 1 while Professional and Ultimate add RAID 0 mirroring. Windows 2000 Professional also has
JBOD, 0, and 1.
Windows Server operating systems from 2000 on have JBOD, 0, 1, plus support for RAID 5 distributed parity.
Windows RAID offers several advantages. You can create arrays from
within Window Drive manager so there's no BIOS to configure. It's also
more flexible with mirrors, allowing you to create them from existing
volumes containing data, as well as delete either half of a mirror
with the other remaining intact. You can mirror individual partitions,
including partitions from different drives onto a single drive.
The disadvantages are that other operating systems, such as the Linux
used on repair discs, can't see Windows software RAID partitions which
use Microsoft's dynamic disk technology. Also, maintenance performed
by Windows when it feels it's needed, which can occur any time there's
a configuration change, hurts performance while in progress. Restoring
mirrors isn't as dead simple as it is with a hardware solution either.
Though you'll see a lot of talk about hardware RAID being faster, this
discussion predates modern CPUs which can easily handle the overhead.
Windows RAID is actually quite fast.
1I am not aware of a process of creating a RAID volume that preserves the content of any RAID member. Usually, you backup, create volume, restore. – Der Hochstapler – 2012-05-23T17:41:49.347
+1 - It's not what I want to hear, but what I thought. – neolace – 2012-05-23T17:45:13.730
1I belive with a software-based RAID you wont need to, but with a hardware RAID I don't know but I also don't think so it is a requirement. But as I'm not sure about that and I don't find refferences, I would reccomend you to read the manual of the desired solution. By the way, interesting question, +1 – Diogo – 2012-05-23T17:45:46.720
You do understand that adding another HDD in a RAID1 setup won't increase the amount of space you have correct? – Ramhound – 2012-05-23T17:47:32.977
@Diogo: Software RAID is a great point! Maybe you could create a new RAID volume with mdadm with a single member disk. Then add an additional RAID member.
– Der Hochstapler – 2012-05-23T17:48:17.077Thank you for all the help, I will mark @Diogo's answer as he was first. – neolace – 2012-05-23T18:05:11.010
I'll also buy another 1TB and try the hardware route with 2 empty drives. – neolace – 2012-05-23T18:07:18.650