<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><DIV><DIV>On Jul 14, 2006, at 7:41 PM, Hugh Esco wrote:</DIV><BLOCKQUOTE type="cite"><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">We're looking at rsync and such for static content.<SPAN class="Apple-converted-space"> </SPAN>But</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">I'm curious what strategies others might be pursuing for</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">syncing two or more servers which are hosting mirrored</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">content on dynamic platforms which are subject to local</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">manipulation between changes.</DIV></BLOCKQUOTE><BR></DIV><DIV>MySQL has built-in database replication, and it's relatively easy to set up. You can set it up in a multi-master configuration, which allows both locations to update content in their copy.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>We've been doing this for hot realtime backups, and are beginning to work with this configuration as multi-master on Drupal sites. We had to replace the db_next_id function to use auto increment instead of table locks, but otherwise, it seems to be working out.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><BR class="khtml-block-placeholder"></DIV><BR><DIV> <DIV>Allie Micka</DIV><DIV>pajunas interactive, inc.</DIV><DIV><A href="http://www.pajunas.com">http://www.pajunas.com</A></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>scalable web hosting and open source strategies</DIV><P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Courier New" size="3" style="font: 12.0px Courier New"></FONT></P> </DIV><BR></BODY></HTML>