I've finally completed a whole RAID 1 backup cycle with Snow Leopard and I can reliably report on how it works.
The process, when performed reliably, is essentially unchanged from earlier versions of Mac OS X. [Details added 3/4/11].
Specifically, you must never attach an old software RAID 1 drive to the working RAID 1 set. If the set was missing a drive ("degraded") before you attach the drive, it will treat the new drive as part of the set. THIS IS BAD.
You must always erase a drive's partition header completely before adding it back in to a RAID set. Otherwise it's misidentified as being an up-to-date part of the RAID 1 set even though it may not have been updated in months.
I had thought that changes made to RAID handling in Snow Leopard might have fixed this problem. Nope.
I use the RAID 1 mechanism to keep a working, off-site backup of my Mac Pro system. The Pro contains three hard drives:
The two RAID drives appear to the system as a single drive. I use the drive primarily to keep Time Machine backups. I also store a few special, very large files on the RAID, too. These include virtual machine images and my Aperture photo library. Those types of files aren't handled efficiently by Time Machine. I have a separate directory on the RAID system to hold such things.
In this arrangement, if any single drive fails, I can easily recover:
The risk remains that I might lose the whole system, like through fire or theft. To avoid this I rely on an off-site backup.
The off-site backup is also a RAID drive. Every few weeks, I swap out one of the RAID drives, and replace it with a blank hard drive. Then I tell the RAID software to rebuild the RAID 1 pair. This copies everything from the existing drive to the new one. Meanwhile I place the swapped-out drive in a safe off-site location.
Each time I perform this swap, I update the off-site backup with the latest set of files saved by Time Machine. It also contains the latest copy of my virtual machines and of my Aperture library.
Here is how the process works. Assume that the Mac Pro currently contains two RAID 1 drives we'll call X and Y. I used drive Z as the off-site backup. I will swap out Drive X and swap in Drive Z.
This is all especially convenient with a Mac Pro because the drives easily pop in or out on simple brackets. The drives slide in and attach directly to SATA connectors.
We have to use DISKPART because the Mac is too stupid to recognize an out-of-date RAID drive. Our Drive Z is usually going to be an older drive pulled out of the same RAID set. If we simply reattach it to the Mac, the RAID software will add it back to the RAID set. Don't be misled by the dire warnings of DiskUtil that you can't possibly add a "demoted" drive back into a running set. It has happened to me and it's Bad.
The only way to avoid this is to erase the partition information. DiskUtil can't do this because it treats the drive as a valid RAID set member.
Thus, we have to connect the drive to a completely different system. To be honest I haven't tried connecting it to a different Mac to erase the partition information. I'm skeptical of success, given the difficulties I've had already.
Here is how we use DISKPART:
We can safely attach the drive to the Mac once the partition data is cleaned off.
If you plug the Z drive into a machine with a lot of other drives, Be Very Careful. It is too, too easy to run DISKPART on the wrong drive. Double check the drive's size, label (if any), and method of connection to ensure you erase the correct drive.
If you run DISKPART on the wrong drive, you're reduced to using file recovery tools to get back the contents of the erased drive. I've been there and it's not a nice place to go.