You dodged the bullet. But Now I want to talk about BACKUP.
RAID is Not Backup. RAID merely extends the time to repair after a drive failure so that a disk failure does not always become a data disaster.
RAID does not protect you at all from human error, crazy software, and "just because" errors. You need a separate, disk based second copy of every file you want to see again tomorrow. And you need a rigorous way to be certain those backups get updated with changes files from time to time.
This needs to be a rigorous schedule based on factors that depend on your company. It needs to be frequent enough so that having to reconstruct the original files will never be so large an undertaking that it would be ruinous for to your company. (e.g., loss of all the memos you wrote this month might take only a few days to re-create. Loss of last week's Video edits would take a full week and more to re-create, and so the backup interval on those would need to be more frequent.
The other thing you need to protect your company against is natural disaster, such as earthquake or fire at your premises. This brings in the notion of A, B, C backups, where the oldest are brought in, about to be re-written, the newest are stored away from the computer, (at the other end of the building), and the last are stored off-site, at least on the other side of town.
Your files are likely so large that one drive cannot hold the entirety. That's OK, because built-in Apple RAID software supports "concatenated RAID" (which is not really RAID at all) but allows you to paste several large disks together and treat them as if they were one Volume. The only downside is that all the component drives must be mounted at once, so you will need some multi-drive enclosures.
If all your retirement money is tied up in the company, not doing this could leave you homeless instead of ready to go on vacation when you need to retire.
