Need Seemless Move to Dedicated Server

luckyroadking · #1 03-15-2009, 01:11 PM

I have a social network which is growing and I want to move from my HG shared account to a HG dedicated server (before it gets too big and my members notice performance drop).

I know when you change servers and dns it takes a while to propagate and some users see the old server and some the new for a short period of time. This would be a problem on my social network because user entered content would wind up in both databases.

How can I make a "clean break"... where from the time I go live on the new server, no users will hit the old server?

Any advise is appreciated as always.

GvilleRick · #2 03-15-2009, 01:45 PM

I don't know that it is possible to make it where no users hit the old server since some may have ISPs that cache IP addresses or pages, etc. You could ask support if they could modify the DNS Zone on your domain to have a short TTL time before you move the account. Then I would consider disabling the database and having a page saying that you are moving to a new server to improve performance. Move everything and change the DNS so that if folks see the new server they will be able to post, etc. but if they see the old server it will have the "Moving...." message.

gwyneth · #3 03-15-2009, 01:50 PM

You're already doing the most important thing--planning and preparation.

While there are several theoretical methods for a seamless transition, you may want to consult HG support about your options because a lot will depend on which apps you run.

quietFinn · #4 03-15-2009, 02:22 PM

In your site's root folder (public_html) make a subdirectory named moving.site
In that folder make a file index.html, saying something like "We are moving our site, please come back later".

You can test it using url: http://YourSite.com/moving.site/

When HG starts to move your site you make a .htaccess file in your site's root folder:

Code:

RedirectMatch .* http://YourSite.com/moving.site/
Options -Includes -Indexes -ExecCGI

What GvilleRick said about the TTL value in your domain's DNS zone is a good to do.

luckyroadking · #5 03-15-2009, 11:35 PM

Thanks everyone for the input. Sounds like I can't get true seemless, but at least I am doing it early enough in the sites growth that it won't effect all that many users.

striddy · #6 03-15-2009, 11:42 PM

Quote:

Originally Posted by luckyroadking

Thanks everyone for the input. Sounds like I can't get true seemless, but at least I am doing it early enough in the sites growth that it won't effect all that many users.

As GvilleRick and quietFinn mentioned, have HG reduce the TTL on the zone to 60 a week prior to the changeover. Then it should be almost seamless. Don't forget to reset the TTL once the changeover has been made.

ronniead · #7 04-02-2009, 10:46 PM

Hi,

I'm in a similar situation. I was thinking of having my old site, redirect to the new website by IP address. That way as soon as they go to the old site, it will automatically substitute the domain name with the IP address of the site...once the propegation of dns hits, then it will be business as usual.

I'm not sure if it's a good idea or not, and exactly how to implement it. So if anyone has ideas...would love to hear them!?