Dieter Plaetinck <dieter@xxxxxxxxxxxx> writes: > You could use Mysql replication (master-slave). I have some experience > working with replication setups, so I can help you if you want. In the > event the master goes down you can use your slave as read-only copy or > even do writes on it, but then you'll need to push the changes back to > the original master when it comes back up. In the latter case, you > could also do master-master replication and not use your master at all > (unless the other one goes down). If everyone is on a fast enough network, I've always liked the master-master MySQL cluster setup, but I don't think I've used it over long-haul links. I believe that if you do have a MySQL cluster in one location, you can use that as a master for master-slave replication to a terciary. btw, I can kick in a Xen VPS or two, if you are ok with a 10Mbps cap. I'll have quite a bit of excess ram/cpu after this weekend.
