<html><head><base href="x-msg://124/"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">You might want to ask on the <a href="http://UUASC.org">UUASC.org</a> and SFVLUG list, as well as here. <div><br></div><div><br></div><div>This is a fairly advanced topic, and any advice you receive you should take with a hefty grain of salt. </div><div><br></div><div>Some folks who have this experience might not be willing to share it for free. :) We can be bought though (usually after meeting dinner is sufficient, at least for me). </div><div><br></div><div>I've worked on multi site applications (<a href="http://evite.com">evite.com</a>, several e-commerce disney properties such as <a href="http://disneyworld.com">disneyworld.com</a> etc) and the only thing I can say with confidence is "it depends". One would need far more data on your setup then you have provided here. </div><div><br></div><div>Do you have your own address space? What kind of links between the data centers? What sort of routing? What sort of load balancers? Is the provider the same one in two different locations? </div><div><br></div><div>etc.... </div><div><br></div><div><br></div><div><div><div>On Dec 15, 2009, at 3:54 PM, Edgar Garrobo wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div lang="EN-US" link="blue" vlink="purple"><div class="Section1"><div style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; ">I'm on a project where we're hosting an application which has a web interface and a Citrix service interface. I've set up two co-location sites, one in Irvine, CA and one in Chicago, Il, for redundancy and to distribute the user load. I'm wondering what the LUG's opinions on the best way to hose a multi-location website? Both sites have separate public IP addresses but identical equipment and the data is replicated between sites at block level by the NetApp storage devices. Ideally a user would be able to go to<span class="Apple-converted-space"> </span><a href="http://www.mydomain.com" style="color: blue; text-decoration: underline; ">www.mydomain.com</a><span class="Apple-converted-space"> </span>and hit whichever site's web server responds first and if one location was to go down, the users wouldn't notice since they would be automatically connected to the other site without having to use a different URL.<o:p></o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; ">Any suggestions on the ideal setup for such a scenario?<o:p></o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; ">Thanks,<o:p></o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; ">Edgar<o:p></o:p></div></div></div></span></blockquote></div><br></div></body></html>