How to avoid downtime ?

[Alphawolf]

Yeah- I just did this not long ago.

I think the best way is to FTP your stuff off the old server (unless you are 100% your local files are good) then upload to the new server via IP address.

Test sites off the IP. Make sure all your stuff is in proper directories, etc...

Then change the DNS at your registrar.

I had a weird issue where some of my local folders were in upper case and when I uploaded to the new server some folks bots like Cleo's found the site 404 due to case.

BTW, hit up Sly with PhatServers on ICQ for a good deal. 147-479-144

Dedicated and managed. Ask him if he has any older servers hanging around.

Webair is very high profile on the boards and therefore seem to have some very happy people and some pissed off people. I've never seen pissed off people at phatservers.

[GeorgeTH]

Originally Posted by Alphawolf

I had a weird issue where some of my local folders were in upper case and when I uploaded[...]

BTW, hit up Sly with PhatServers on ICQ for a good deal. 147-479-144

Dedicated and managed. Ask him if he has any older servers hanging around.

Never NAME anything in upper case - saves the trouble...

I case phatservers has not currently "any older servers hanging around" there might be one coming up... Mike, their tech, told me I should maybe get a newer machine since my webstats are hanging too often...

[tiny]

I've always had good success using the numeric ip or IP address to make sure everything works then changing the dns.
Of course thats what everyone else said I think.Dammit I think its time to start drinking so I can think straight haha

[contraband]

The way I do it is:

1. Upload everything to your new host

The next steps assume you use windows, I'm sure there are analogous steps for other OS'es but I'll neglect them for shortness

2. Open C:\WINDOWS\system32\drivers\etc\HOSTS with a text file
Add an entry like this:

1.2.3.4 yourDomainName.com

where 1.2.3.4 is your new host's IP

What this does is tells windows to resolve yourDomainName.com to 1.2.3.4 for the life of that entry. This allows you to test your new host like it was on the actual domain.

3. Go to yourDomainName.com and test that everything is working fine. Now you can remove the entry you added in step 2
4. Change your nameservers to your new host, BUT don't cancel your old hosting account just yet. Wait at least 2 days before cancelling it.
5. That's it, if all went well, you should experience no downtime at all.

If you're wondering about the technicalities of it, the reason is because while your DNS is propogating (big word for being updated around the internet), you're leaving the old IP intact, as well as the new IP, so even if some people's DNS records aren't updated, they still won't notice a thing because they'll be going to your old host.

I hope that helps