Problem recover replica

[Manel Gimeno Zaragozá]

Hello,

I've noticed that the "missing changes" are due to some of the actions done during the "blackout" are processed un "/var/lib/imap/sync" log and named modified to log-PID.
It seems that rsync_client have not noticed that Replica is down and it process some of them. Once it notice that replica is down continue login in "log" file. When Replica comes back, sync_client process the changes from "log" without problems, but we have miss some changes.

Is there any configuratio to avoid this situation?

Regards.

Manel Gimeno Zaragoza
magiza83 at hotmail.com


From: magiza83 at hotmail.com
To: info-cyrus at lists.andrew.cmu.edu
Subject: Problem recover replica
Date: Thu, 2 Feb 2012 13:11:24 +0100







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.

On the other hand, I have also doubts about how "sync_client -r" and "sync_server" are initiated. In my test machines I should run manually them each time I start cyrus-imapd, I though that it could be automatic one I start the service cyrus-imapd, but it is not.

Thanks & Regards.

Manel Gimeno Zaragoza
magiza83 at hotmail.com
 		 	   		  

----
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.andrew.cmu.edu/pipermail/info-cyrus/attachments/20120202/fbbd93f4/attachment-0001.html