Roland Pope wrote: > > From: "Birger Toedtmann" <[EMAIL PROTECTED]> > > Second (esp. if you cannot afford the hardware described above) you may > > set up the heartbeat package from www.linux-ha.org. It is very easy to > > create failover mechnisms with heartbeat, but there is still the problem > > of data synchronisation (heartbeat does not deal with that). I myself use > > heartbeat together with rsync, which is surely unidirectional but can be > > turned into somewhat "bidirectional" in combination with heartbeat: The > > "active" machine will permanently send its data to the backup machine > > (simple as that: I use a cronjob that tests whether we are active or not). > > Upon failfailover, the situation will reverse, which leaves data intact > > and up-to-date. However, note that rsync is slow, if you have lots of > > data, you should definitely think over the first alternative. > > > Birger, > > I am looking at implementing something like this at present. Would you be > able to provide a summary of what you had to do, and maybe any scripts you > had to build to get this to work? > > Thanks > Roland Pope
I'm planning an starting implementing a redundant mail system in 6 months (maybe a year) so it's still only in the ideas fase. One thing I wanted to test was using coda as storage and let coda's replication take care of the mail storage synchronization. If cyrus was one single threaded application there could be problems with file lock and caches, but since cyrus is a combination of several daemons that already are aware that the files get updated externally -- it may just work 8-) -- Med venlig hilsen / Kind regards Hack Kampbjørn
