CSync2 daemon must be running on both the the servers, preferably as (x)inetd daemon; csync2 daemon does not identify itself as a master or slave, it just runs. What qualifies a particular setup a master or slave is the csync2*.cfg files which specify on a per "group" basis whether that particular node should have as a master or a slave for that group of files like :<br>
<br>group default {<br><blockquote style="margin:0 0 0 40px;border:none;padding:0px">host <a href="http://master.server.name">master.server.name</a>;<br>host (<a href="http://slave.server.name">slave.server.name</a>);<br>
include xyz;<br>exclude abc;<br>auto left;#since we want master to overwrite changes on slaves in case of a conflict, change this to other auto-setting if needed. </blockquote>}<br><br>In addition to the above, csync2 requires that a (scheduled via cron or similar) trigger ( csync2 -x ) instruct the csync2 daemon (on the presumed master side) to identify the changed files out of those configured to be replicated and then sync those with the peer (slave) servers. In case of master-master setup, the cron trigger should be present on all peers whereas in case of master-slave setup the cron trigger need to be present only on master server.<br>
<br>I hope this helps,<br><br>Regards,<br>Samba<br><br><br><div class="gmail_quote">On Thu, Jun 7, 2012 at 11:00 PM, Gary E. Miller <span dir="ltr"><<a href="mailto:gem@rellim.com" target="_blank">gem@rellim.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Yo All!<br>
<br>
Newbie here. I have a number of data moving tasks now being handled<br>
by rsync and rsnapshot, but those solutions are not able to scale to<br>
my problems. Thus I am giving csync2 a shot.<br>
<br>
I am runnning version 1.34 with two gentoo patches. Not sure what the<br>
patches do. If anything I ask has been previously discussed here,<br>
or elsewhere, then feel free to just point me to that.<br>
<br>
Currently I am running a master with geographically dispersed slaves.<br>
The slaves are runnning in daemon mode. The master is run from a<br>
simple shell script:<br>
while true; do csync2 -x; sleep 5m; done<br>
<br>
I checked the doc, but I can see no description of what the master would<br>
do if I run it in daemon mode. Does it just look at the hint table?<br>
Does it loop continuously? Can I buy a clue?<br>
<br>
Sometimes the net connection to the remote hiccups, and csync2 seems<br>
to exit with a write error. Is there a retry mechanism, or do I just<br>
need to keep re-running csync2?<br>
<br>
I created the csync databases on master and slave this way:<br>
csync2 -cIr /<br>
<br>
Then jumped in to the above update loop. I am worried that some of<br>
the files were not in sync before beginning, or may have been corrupted.<br>
Is there a way to have csync2 do a scrubbing? Like the way an ECC<br>
RAM controller slowly reads all RAM in the background to be sure all<br>
the bits are working. I could see csync2 randomly testing X number of<br>
files to be sure the master and slave checksums match.<br>
<br>
Otherwise I may have to run an rsync every once in a while, but then I<br>
am back to my problems with rsync being a bit flakey over the internet.<br>
<br>
A doc typo at the start of the last paragraph of 3.4.5:<br>
<br>
Usually the action is only triggered on the targed hosts,<br>
<br>
I assume targed should be targeted.<br>
<br>
And anything else a newbie should know about csync2?<br>
<br>
TIA.<br>
<br>
RGDS<br>
GARY<br>
---------------------------------------------------------------------------<br>
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97701<br>
<a href="mailto:gem@rellim.com">gem@rellim.com</a> Tel:<a href="tel:%2B1%28541%29382-8588" value="+15413828588">+1(541)382-8588</a><br>
<br>_______________________________________________<br>
Csync2 mailing list<br>
<a href="mailto:Csync2@lists.linbit.com">Csync2@lists.linbit.com</a><br>
<a href="http://lists.linbit.com/mailman/listinfo/csync2" target="_blank">http://lists.linbit.com/mailman/listinfo/csync2</a><br>
<br></blockquote></div><br>