Here's the problem - my home studio has this constant background noise of the 2TB hard drive, so I've decided to move things around a little. I hadn't really noticed, but I've started recording ta 48KHz, 24 bit, with a Rode NT1-A and it just picks up this noise when you have sensible gain levels on the mic.
Further to that a little speed test surprised me - it showed that my trusty Iomega RAID drive is only doing about 30Mb/s write speed. That's ok for recording, but the new drive (USB3 in a USB2 slot as the Mac doesn't have USB3) is writing at over 100Mb/s. Hmm.
So it feels like I should do this the other way round. Have the relatively quiet, fast drive as my recording drive and the slow noisy one as backup. That's the easy part. How do I get the noisy machine out of my studio?
The answer is to put it on the network, connected to a hub upstairs (where I already have a hub for the PS3 and so on). That's easier said than done, given that it's formatted with HFS+ and reformatting in something a NAS will understand will almost certainly lose some information. I need to use HFS+ or something that supports everything HFS+ supports, such as the Linux ext4 format.
I researched ways of putting a non-NAS drive on the net, and there are solutions, but they all seem a bit of a compromise for the £0 I want to spend doing it.
The answer?
I have moved my Raspberry PI upstairs (powered off the telly - currently - I'd best deal with that), and will connect the Iomega to this thing, formatted as ext4. I can then use rsync over ssh to pull the files from the iMac that I want to backup (I could do a push, I suppose but I'm also pulling some stuff from offsite servers so it keeps all the rsync jobs in one crontab if I pull).
Perfect - I can't use Time Machine, but rsync is great.
Rsync
For those that have not used it rsync is a command line utility in just about every unix - OSX included - which syncs two file trees. These trees can be local or on a variety of different network endpoints, including ssh - perfect for my needs. When run with the -a flag (archive) it preserves file permissions and symlinks and so on.
The really great thing about rsync is it only copies files that it needs to, and in fact only copies "parts" of files that it needs to - brilliant for syncing large files. There's no version history, but I don't really care about that. I just need my files somewhere safe.
Crontab
The cron table is an ages old mechanism for unix machines to run the equivalent of Windows scheduled tasks. The table consists of an interval specification and the command to run. It's fairly straightforward.
It's true that data throughput speeds on a Pi aren't that great, as the network interface is on the same bus as the USB, but again, it doesn't really matter.
The final part of this is to run rsync in the crontab, and use the 'nice' command to lower it's execution priority. I will then set it to run overnight, so it doesn't try to read files while I'm recording.
I'm still copying files to my new fast drive (and will be for hours yet - about 15 hours to copy 2TB it seems). Once that's done I need to move the Iomega drive up next to the Pi, and implement the rsync - then I can leave it to it.
This means that little £30 pi is running a webserver, sshd endpoint for me to do secure tunnelling into my network from outside, dhcp for my network (because the virgin superhub is crap at it) and now is in charge of my backups. Genius!