Date: Mon, 26 Sep 2011 11:29:17 -0700 From: Chuck Swiger <cswiger@mac.com> To: Martin Wilke <miwi@freebsd.org>, James Shupe <jshupe@osre.org> Cc: freebsd-net Net <freebsd-net@freebsd.org> Subject: Re: Data centers failure proof with CARP. Message-ID: <69A27071-39FF-4AFA-8E06-05ECA1E8DD2C@mac.com> In-Reply-To: <A89AD932-9C2E-4B95-B9C3-FF526752A205@FreeBSD.org> References: <CAHGGWY60WPe72q3SOYiysaqFt6e%2BQBq=jVuJWryJsubo3ngqgg@mail.gmail.com> <1317017255.2706.5.camel@jshupe-2530p.osre.org> <A89AD932-9C2E-4B95-B9C3-FF526752A205@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi-- On Sep 26, 2011, at 9:53 AM, Martin Wilke wrote: > Any other Idea what we can do to get a failover between both servers? Multi datacenter failover is *hard*. You have to evaluate which parts are static systems-- ie, display the same web images from all DCs, provide a current UTC timestamp from NTP, or whatever-- and which parts are transactional: ie, people's email, or placing orders on an online store, etc. Failover of static systems is relatively easier, as they don't need to change from one DC to another, and you can just use short DNS TTLs or outsource to a content distribution network like the various CDN / cloud providers (Akamai, Amazon, Level3, Azure, whatever). Failover of the transactional portion requires extensive effort to understand the transactional model-- are you active/standby, with write-through to the primary and cacheable read-back elsewhere, with a planned transition in the event of failure of the active to promote a standby to active; or are multiple DCs active with some form of load-balancing in place to distribute transactions (geolocation by client IP towards closer DCs, perhaps), etc. And you also have to consider what happens after a failure, and how you reintegrate DCs once a failure is resolved and reassemble your transactional data to be coherent. Regards, -- -Chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?69A27071-39FF-4AFA-8E06-05ECA1E8DD2C>