BTRFS doesn't quite fit the traditional RAID model even though most of its terms are handled that way.
With BTRFS you specify a separate "raid level" for metadata (directories and checksums) as well as file data. By default, BTRFS runs with "RAID1" (two copies) metadata and "RAID0" (one copy) file data - even on one disk (the two copies of metadata are stored separately on the same disk). If you add another disk and rebalance, the redundant metadata copy will be moved to another disk.
Since you're concerned with redundancy, you're going to want to use at least RAID1 mode for both the filesystem and metadata. This will ensure that two copies of your data exist across your various drives for redundancy, and you get a bit of speedup on reads as only one device (whichever is least-busy) must be read with checksums in the metadata used instead of parity for integrity checking.
If you have at least 4 devices, you can enable "RAID10" mode which behaves similarly -- data is split into two stripes, and each stripe is mirrored onto two disks.
If you're set on getting exactly what you asked for, and don't mind adding another layer, you can get there with LVM. Use LVM to build a striped volume across the smaller disks, and then build a BTRFS mirrored filesystem on top of that and the larger disk... This would yield pretty unpredictable performance though, as writes would be limited by the speed of the larger disk, and reads would be erratic depending on whether BTRFS chose to read from the LVM set or the larger disk.
If you set read priority to the LVM volume, I think you could avoid the large drive causing problems with read speed. I'm pretty sure that I read about that somewhere, though I could be making it up. As far as metadata, could I be sure that all the metadata was on both logical drives? – Ben – 2015-10-07T16:03:09.320
I'm not sure on priority. As for metadata, yes... Setting it to RAID1 (the default) would ensure redundancy. – BowlesCR – 2015-10-07T16:05:44.600