Solved

Failover Backup Web Server

Posted on 2013-11-07
3
253 Views
Last Modified: 2013-11-11
Hi All

We have a Web Server that hosts various websites, and we are currently building a Disaster Recovery site for Failover.

My Question is if we ever need to failover to the Disaster site which would have a different IP Address, is there some way that you can have two A records pointing to WWW that if one does not respond then it would try the other, Similar to using two MX Records

John
0
Comment
Question by:pepps11976
  • 2
3 Comments
 
LVL 35

Expert Comment

by:Kimputer
ID: 39629939
A browser does not know anything about preferences of a DNS host record.
So situation with the DNS record as you described
A:
both servers are online, one server not synced with the other.
Client: sometimes get old website, sometimes gets new website
B:
only main server online, backup not online.
Client: sometimes gets a time out problem, sometimes gets the main site
C:
main server knocked out, backup online
Client: sometimes gets a time out problem, sometimes gets the backup server

If you keep the DNS record with only the main server:
A:
main server problem, backup server online. DNS record update to point to new IP.
Client will get timeout problems, unless the DNS is propagated properly in a timely fashion
B:
main server problem backup server online with the IP of the main server
Client will have the backup server the moment you plug in the cable (or changed the IP number), if needed, change IP or unplug the cable from main server, if not a network failure, but a software failure.

So as you can see, I prefer the last method. When main server goes down, change the IP numbers so the backup server will have the original main server's IP.
0
 

Author Comment

by:pepps11976
ID: 39629994
I forgot to mention each server is at a different site, so although I would be able to give backup server internal ip the same, the external will be different

john
0
 
LVL 35

Accepted Solution

by:
Kimputer earned 500 total points
ID: 39630320
Whooops, then prepare your DNS entry for a really short TTL, like 300 (5 minutes). When the failure happens, you will have about a 5 minute outage AFTER you change your DNS.
So, notice failure, DNS edit IP, 5 minutes later requests will arrive at the backup server
0

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

You might have come across a situation when you have Exchange 2013 server in two different sites (Production and DR). After adding the Database copy in ECP console it displays Database copy status unknown for the DR exchange server. Issue is strange…
Resolve DNS query failed errors for Exchange
This tutorial will give a short introduction and overview of Backup Exec 2012 and how to navigate and perform basic functions. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as conne…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

911 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

23 Experts available now in Live!

Get 1:1 Help Now