Changing Servers - Redirect to new IP = No Downtime?

Question

I am changing servers of my website. The IP of old server cannot be moved to the new one. To have no downtime I am planing to do the following, please someone confirm it will work:

1. Setup the new server and listen on the new IP
2. Old server redirect all traffic to the new IP
3. Change DNS records to point to the new IP

My logic tells me that when I redirect to the new IP from my old box, the user will not see the domain name in the browser but will see the new IP. Is there a way to redirect to the new IP and send along the HOSTNAME with it so that the user will see the domain name in the browser?

Im doing this because the site is in constant use and simply changing DNS settings won't do as database won't be synced between the new and old servers during propagation.

Answer 1

Here's the method that worked for me:

1. Sync the files and databases with the new server.
2. Perform a re-sync just before cut-off.
3. Change the DNS to point to the new server.
4. Forward the request coming to the old ip to the new server until DNS propagation completes.

Here's how I would do the step 4:

We will configure IPTables on a Linux server to redirect all the traffic coming on port 80, (which is the default web server port), to a server with the IP 122.164.34.240. The first step is to set your Linux box to allow this kind of forwarding to take place. Open a terminal window, log in as root user and run the following command:

# echo 1 >/proc/sys/net/ipv4/ip_forward

The next step is to tell IPTables to redirect the traffic to the new server:

# iptables -t nat -A PREROUTING -p tcp --dport 80 -j DNAT --to-destination 122.164.34.240

Here’s where the IPTables magic happens. With the third and final step, we tell IPTables to rewrite the origin of connections to the new server’s port 80 to appear to come from the old server.

# iptables -t nat -A POSTROUTING -p tcp -d 122.164.34.240 --dport 80 -j MASQUERADE

The final step is required because if we don’t tell the web server of the new server that the connections are coming from the client machines, it would think that they are originating from the old server.

You may want to repeat this for the databases and email server port as well.

Answer 2

You can also look into adding multiple A-records. For example, Google uses this, check their nslookup output:

Name:       google.com
Addresses:  209.85.148.101
            209.85.148.102
            209.85.148.113
            209.85.148.138
            209.85.148.100
            209.85.148.139

If you add multiple A-records to a domain, visitors will receive multiple IP's and try them in that order. If one fails, the client moves to the next one to try.

Setup the new IP as an extra A-record 24 hours up front, start new server, shutdown the old, remove IP.

Answer 3

Another option is to use a VIP (virtual IP). So, your steps will be:

1. Setup the new server and listen on the new IP.
2. Add a VIP to the old server.
3. Change DNS records to point to the VIP IP. Till now all traffic will still be sent to the old server but using the VIP.
4. When ready to go, move the VIP to the new server.
5. Optionally, you can change the DNS to the new server IP and remove the VIP (after some time) from DNS.

Answer 4

Ok, since you mentioned about Database replication, you have to do the following.

1. Setup replication between databases in the two servers.
2. During cutover, make the new server's DB as the primary and the old server as readonly.
3. Point the Application's Database Connection String to the New server on both old and new server. If your site uses Sessions, make sure session is persisted in DB.
4. Change the IP address in DNS to the new server.
5. Keep running both the servers for atleast 48 hrs.

Answer 5

1. Setup the new server and listen on the new IP
2. Then configure transparent redirection. On old server install rinetd.

In rinetd.conf:

OLD_SERVER_IP 80 NEW_SERVER_IP 80

3. Change DNS records to point to the new IP

Answer 6

you can use HA-Proxy in front your web servers, when one of them is going to maintenance mode secondary server will take over.

Answer 7

Your list of what to do looks quite sensible.

As an example, assuming you use apache, when you do something like this in apache on the old server:

redirect permanent / http://newserver.example.com

The user will see the new domain in the browser when they browse to the old site. In this case the redirect also is permanent for as long as the browser is running.

So as long as you implement some kind of redirect in your web server in addition to your other changes you should be fine.