<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
> On Thu, Feb 02, 2012 at 01:11:24PM +0100, Manel Gimeno Zaragozá wrote:<br>> <br>> What version?<br>
<br>
<pre>I'm running Cyrus 2.4.13.</pre>
> <br>> > 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.<br>> > <br>> > Which is the best way to resincronize the missing parts to Replica? <br>> <br>> sync_client -r -f $file for each file in the conf/sync/ directory.<br>
<br>
<pre>I've been trying sync_client -r -f log-PID and it works. All the missing changes are applied <br>without problem, I should do some script that controls this files and apply them.<br>anyway the log-PID is not deleted when its processed. I guess we should control the processed log-PIDs manually and move or delete them, am i right?</pre>
<br>> <br>> > 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.<br>> <br>> No, that's awful. Don't do that.<br>> <br>>
> 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.<br>> <br>> It's not too bad. We run it occasionally if we suspect things have<br>> got confused for other reasons.<br>
> <br>> > 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.<br>> <br>> I have attached the script that we run. It has lots of hooks into<br>> our own systems of course.<br>> <br>> I would LIKE to make something more generic that's part of Cyrus<br>> itself, rather than having external tooling. Of course, our external<br>> tooling is a bit special-cased as well. But at least having a basic<br>> "keep trying to replicate all the records" would be good.<br>> <br>> Bron.<br>
<br>
Thanks for the response.<br>
<br>
Manel.<br><br>Manel Gimeno Zaragoza<br>magiza83@hotmail.com<br><br><br> </div></body>
</html>