[115017] in North American Network Operators' Group
Facility wide DR/Continuity
daemon@ATHENA.MIT.EDU (Drew Weaver)
Wed Jun 3 08:09:51 2009
From: Drew Weaver <drew.weaver@thenap.com>
To: "'nanog@nanog.org'" <nanog@nanog.org>
Date: Wed, 3 Jun 2009 05:09:33 -0700
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Hi All,
I'm attempting to devise a method which will provide continuous operation o=
f certain resources in the event of a disaster at a single facility.
The types of resources that need to be available in the event of a disaster=
are ecommerce applications and other business critical resources.
Some of the questions I keep running into are:
Should the additional sites be connected to the primary sit=
e (and/or the Internet directly)?
What is the best way to handle the routing? Obviously two d=
evices cannot occupy the same IP address at the same time, so how do you pr=
ovide that instant 'cut-over'? I could see using application balancers to d=
o this but then what if the application balancers fail, etc?
Any advice from folks on list or off who have done similar work is greatly =
appreciated.
Thanks,
-Drew
