Avoiding long downtime

[shepherd]

What is the best way to avoid site downtime as a result of moving your site from one server to another? A DNS change takes propagation time.

[infinitomagazine]

Re: Avoiding long downtime

Well a good host provider has good servers and in this case dns resolving issues just takes 2 hours - 4 hours

[Kdoubt]

Re: Avoiding long downtime

10 minutes or less here :

You could always set a ns3 & ns4, then disengage ns1 & ns2 so that ns3 & ns4 pick up (on your new host).

Just make sure your site is on your new host so when it switches, your site shows.

I've never had to try this because our dns/domains resolve so quickly, so there could be a margin of error

[The Hosting Team]

Re: Avoiding long downtime

If you set up your site on your new host and then change your DNS, there should be no downtime at all. (If you have a dynamic site, where users post, etc., then you do need to shut down the old one and then turn on the new one, so that you don't get data integrity problems.)

[harakiri]

Re: Avoiding long downtime

You need a transition scheme. Transfer first your files to your new webhost. If your site is already resolving to your new host, switch off your old host.

[inworx]

Re: Avoiding long downtime

Simply, move your siles from old server to new one and when you've done that, change the IPs in the ns to the new server's IPs. It will give you ZERO downtime

[The Hosting Team]

Re: Avoiding long downtime

Wait several days after you're done before cancelling the old accounts, so you don't miss any traffic.

[boebi]

Re: Avoiding long downtime

Just copy over all the files, databases, emails, domains (also domains), whatever
And change the nameservers. It should bring 0 downtime, if the nameservers changed, it will go to your new host, if they didnt, they go to your old (where you still didnt delete everything).

Ofcourse it can result in lost content, or posts if its a forum