Configure Rsyn con each side to send the directories that originate on one side to the other. Rsync can delete files at the remote site that were deleted at the original.<br><br><div class="gmail_quote">On Thu, Oct 13, 2011 at 9:22 PM, Jason Friedman <span dir="ltr"><<a href="mailto:jason@powerpull.net">jason@powerpull.net</a>></span> wrote:<br>
<blockquote style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left-color: rgb(204, 204, 204); border-left-width: 1px; border-left-style: solid;" class="gmail_quote">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><br>