× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. February 2008

Re: Mirroring Systems

On Feb 10, 2008 8:17 PM, Ken Sims <mdrg7319@xxxxxxxxxxx> wrote:
One issue, our disaster recovery system is in a completely different
location from our main system (as it should be), several hundred miles
away, and so it's on a different subnet (192.168.251.0/24 versus
192.168.10.0/24). So it would involve more than just having the
disaster recovery system use the main system's IP address. The
packets would never get routed to that subnet.

There are many ways to do this. The simplest solution is to use DNS
with a low TTL, but of course that has several drawbacks.

Using a seperate subnet for the cluster is the solution usually
implemented, and routing changed dynamically. If that is not possible,
policy routing, NAT are other ways to achieve the same result.

It would be possible to have the disaster recovery center be on the
same subnet as the main data center, but it wouldn't be easy.

I wouldn't use that approach either.


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.