A lot of time this year (as well as a fair bit of money) has gone on system redundancy and data backups. Setting up FS based data was easy thanks to a couple of new hard drives and a bit of RAID goodness. MySQL however, has always caused a bit of an issue.
MySQL AB, came up with 2 forms of data backup and redundancy. The first one we tried was MySQL cluster. Even though this is now included in the main distributions of MySQL server, Cluster itself seems to be years off having a usable product(especially for Not For Profit projects such as FreeSide), however, it has an excellent base to move on from and has many advantages. Unfortunately it requires too much hardware and cannot support some of the packages we use as they are not compatible with the NDB engine at the time of writing.
The second is replication, basically a copy of all databases from one Master server to a slave server. This may sound no better that simple copy and paste, however, there is a lot more depth than that which is beyond the scope of this post. As an added incentive (as with cluster) it will be possible to use this secondary system as service redundency for MySQL so downtime at any one MySQL failure should be minimal and recoverable.