<p>Unison is great for that. It is bi directional rsync that is multi threaded and can do compression.</p>
<p>Sent from my phone. Please excuse my brevity and typos.</p>
<div class="gmail_quote">On Oct 13, 2011 9:22 PM, "Jason Friedman" <<a href="mailto:jason@powerpull.net">jason@powerpull.net</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
We have two hosts, one in Denver and one in New York, that will serve<br>
as disaster-recovery hosts for each other. /etc, /bin, /opt etc. are<br>
already accounted for. Synchronization needs to occur daily. Change<br>
volume will be about 10Gb per day.<br>
<br>
Each host has a /data directory with "meshed" subdirectories. For<br>
example, in Denver we have:<br>
<br>
/data/A/B/file1<br>
/data/A/B/file2<br>
/data/A/D/file1<br>
/data/M/file1<br>
/data/M/N/file1<br>
<br>
In New York we have<br>
<br>
/data/A/C/file1<br>
/data/A/E/file1<br>
/data/A/E/file2<br>
/data/M/R/file1<br>
<br>
So, there is no actual conflict between any full path between the two<br>
machines. Using rsync or some other technology, what is the best way<br>
to synchronize the /data directory?<br>
<br>
To make things more tricky, imagine that on day one file<br>
/data/A/D/file1 is sent from Denver to New York. On day two that file<br>
is deleted from Denver, meaning on the next cycle that file needs to<br>
be deleted from New York, also.<br>
_______________________________________________<br>
clue mailing list: <a href="mailto:clue@cluedenver.org">clue@cluedenver.org</a><br>
For information, account preferences, or to unsubscribe see:<br>
<a href="http://cluedenver.org/mailman/listinfo/clue" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a><br>
</blockquote></div>