Hi, Quoting Manel Gimeno Zaragozá <magiza83@xxxxxxxxxxx>:
Hello,I'm trying to implement a master-replica cyrus environment and I'm getting some issue that I'm not able to resolve. The scenario is the following:Everything is working fine between Master & Replica until Replica goes down (maintenance or whatever). Once is down, in master there are still connections and modification. If I bring up Replica the changes made during the "blackout" are no fully transmitted to it. Some of the are transmitted, but not all.Which is the best way to resincronize the missing parts to Replica?I was wordering to rsync imap folders (/var/spool/imap & /var/lib/imap), and It works fine in my test environment, but in produccion it could be GB to sincronize and I think this is not optimum. Other option was "sync_client -l -u <all_user>" but I'm guessing that in production I will have the same problem due to the amount of data to sincronize.
If you have configured sync_log: 1 cyrus will keek an actionlog for rolling replication. While "sync_client -r" is not running, or unable to connect to the sync_server this file keeps track of what has to be synced. Once sync_client connects to the server it will catch up. -------------------------------------------------------------------------------- M.Menge Tel.: (49) 7071/29-70316 Universität Tübingen Fax.: (49) 7071/29-5912Zentrum für Datenverarbeitung mail: michael.menge@xxxxxxxxxxxxxxxxxxxx
Wächterstraße 76 72074 Tübingen
Attachment:
smime.p7s
Description: S/MIME Signatur
---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
