[115039] in North American Network Operators' Group
Re: Facility wide DR/Continuity
daemon@ATHENA.MIT.EDU (Bill Woodcock)
Wed Jun 3 13:48:01 2009
Date: Wed, 3 Jun 2009 10:47:13 -0700 (PDT)
From: Bill Woodcock <woody@pch.net>
To: Drew Weaver <drew.weaver@thenap.com>
In-Reply-To: <F3318834F1F89D46857972DD4B411D700FC91A85@EXCHANGE.thenap.com>
Cc: "'nanog@nanog.org'" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Wed, 3 Jun 2009, Drew Weaver wrote:
> Should the additional sites be connected to the primary site
> (and/or the Internet directly)?
Yes, because any out-of-band synchronization method between the servers at
the production site and the servers at the DR site is likely to be more
difficult to manage. You could do UUCP over a serial line, but...
> What is the best way to handle the routing? Obviously two devices
> cannot occupy the same IP address at the same time, so how do you
> provide that instant 'cut-over'?
This is one of the only instances in which I like NATs. Set up a NAT
between the two sites to do static 1-to-1 mapping of each site into a
different range for the other, so that the DR servers have the same IP
addresses as their production masters, but have a different IP address to
synchronize with.
-Bill
