I see the only option I have is to use filesystem sync and not rsync.
Frankly I'd rather use rsync and not play with GEOM (I'm on FreeBSD) on
servers right now.
The problem as I've said is not sync itself but rather Dovecot's way of
treating files. You can test it yourself: go to your our cur/ dir, and
copy any message to new/ dir, and then login to the mailbox with IMAP
client. As soon as these messages are identical I'd expect Dovecot to
remove one of it but Dovecot simple rename second message file so you'll
see two identical messages in your INBOX in mail client.
That's what is strange for me. I can fight it on IMAP level (compare
messages and find duplicates) but this way won't look nice.
Your,
Alexander
11.01.2010 16:25, Anton Dollmaier пишет:
Hi,
The idea was to have two identical (well, nearly identical) servers with
the same software and data on them, and while the first do its job as
SMTP and POP3/IMAP4 server, the second server just get copy of first's
current state (that is, copy user db and mail spool). In case of
something wrong with 1st server I'll just put its IP on second one and
will go on.
Use Heartbeat and DRBD for replication - all mail is synched between the
servers.
If first crashes, heartbeat runs "second" as new server for the users.
As dovecot on "second" is only started if "first" is down, there are no
issues about inconsistencies.
best regards,
Anton
