Best way to change host and minimize downtime?

dunkin · 2006-02-18, 11:30 AM

Hey gang,
I am moving to a new host after 3 years with the same company. They were sold and now support sucks ass.
What is the best way to move domains and minimize downtime? I am thinking that making the new server the third and forth choice for the domains and waiting the customary 24-48 hours for propagation, upload the files to the new server and then remove the original server after that.
Any suggestions?
Thanks,
Dunkin

T Pat · 2006-02-18, 11:36 AM

Quote:

Originally Posted by dunkin

Hey gang,
I am moving to a new host after 3 years with the same company. They were sold and now support sucks ass.
What is the best way to move domains and minimize downtime? I am thinking that making the new server the third and forth choice for the domains and waiting the customary 24-48 hours for propagation, upload the files to the new server and then remove the original server after that.
Any suggestions?
Thanks,
Dunkin

That's easy Dunkin, Just contact Sparky give him your information and let him move everthing for you

KG Gary · 2006-02-18, 12:15 PM

Quote:

Originally Posted by T Pat

That's easy Dunkin, Just contact Sparky give him your information and let him move everthing for you

Got to agree with that.
I've only been with them for a few months and I'm very impressed at the service, and particularly the support.
I've been pestering them a lot lately with my newbie questions and they've been superb.

MrYum · 2006-02-18, 02:28 PM

Yup, I don't host with Sparky...but all I've ever heard is good stuff the services he provides

Speaks volumes about a host when you NEVER hear anything bad.

Always best to get everything moved to the new host at least 48-72 hours before the old server goes offline. You can use the new IP to look at your sites on the new server and check for errors. That said, there will always be some little things to fix up once dns propagates...so make sure you're available for those critical hours to do some tidying up

tigermom · 2006-02-18, 04:00 PM

If it's a simple static site, it shouldn't be much of a problem, just have the old server still serving the site for 48-72 hours after you change the dns, like Mr Yum suggested. That way users who are still directed to the old server are able to see the site.

If it's a dynamic site with forums and such, then it's a little bit more complicated but perfectly doable. My admin transferred my largest site today with huge forums (over 15k registered users and lots of active posting). There was zero downtime in the process.

SirMoby · 2006-02-19, 10:20 AM

A good host will handle most of the move for you. One thing that they should also have you do is use a temporary hosts file and surf your new sites before they make changes to the actual domains. This should all take place at least 3 days before hand.

Working with your new host is the best way to go.

Matt Collins · 2006-02-19, 10:48 AM

A good host will help you move your content from the old host and if the old host is worth a shit, he'ss cooperate with your move also.

That's how you can tell the good guys from the bad guys.

Matt

keyDet · 2006-02-19, 11:34 AM

Yup, downtime during a change of hosts is unacceptable, it is not such a difficult process for a host.

In a nutshell, upload your site to the new server, check it out, then, if you have access to DNS zone modification, change the IP of the domain(s) to point to the new server instead of the old. Your old nameservers will then send traffic to the new server. This way traffic will go to the new server immediately, unless you have the old domain cached (which usually never lasts longer than an hour or so). Then switch nameservers, and dump the old server after about 2 days or so.

There will be no downtime if you do it this way.

SexycityBrian · 2006-02-20, 09:32 AM

the best way is to change the ttl for you dns records to 5 minutes and wait 72 hours. Move your data to the new host. change the dns information to the new host (ip) in 5 minutes you are moved. Now if you cant do this then. Get the new host to set up the dns records for you with the current ip and set the ttl to 5 minutes once everything is moved have the new host change the dns records and again in 5 minutes you will have resloved to the new host

SexycityBrian · 2006-02-20, 09:34 AM

Quote:

Originally Posted by SexycityBrian

the best way is to change the ttl for you dns records to 5 minutes and wait 72 hours. Move your data to the new host. change the dns information to the new host (ip) in 5 minutes you are moved. Now if you cant do this then. Get the new host to set up the dns records for you with the current ip and set the ttl to 5 minutes once everything is moved have the new host change the dns records and again in 5 minutes you will have resloved to the new host

I left out an important step. After the new host sets up the dns record with the 5 minute ttl change to there dns servers and wait 72 hours before you move the data and change the ip

Lenny · 2006-02-21, 01:45 AM

Jeez there's some complicated answers in here.

It's really simple....tell the new host to move everything and call you when they're done....then change the DNS at the registrar.

DONE

2006-02-18, 11:30 AM	#1
dunkin Just because I don't care doesn't mean I don't understand! Join Date: Feb 2004 Posts: 92	Best way to change host and minimize downtime? Hey gang, I am moving to a new host after 3 years with the same company. They were sold and now support sucks ass. What is the best way to move domains and minimize downtime? I am thinking that making the new server the third and forth choice for the domains and waiting the customary 24-48 hours for propagation, upload the files to the new server and then remove the original server after that. Any suggestions? Thanks, Dunkin __________________ Dunkins World - Accepting gallery submits & link trades.

2006-02-18, 02:28 PM	#4
MrYum Arghhhh...submit yer sites ya ruddy swabs! Join Date: May 2004 Location: Sunny Florida! Posts: 5,108	Yup, I don't host with Sparky...but all I've ever heard is good stuff the services he provides Speaks volumes about a host when you NEVER hear anything bad. Always best to get everything moved to the new host at least 48-72 hours before the old server goes offline. You can use the new IP to look at your sites on the new server and check for errors. That said, there will always be some little things to fix up once dns propagates...so make sure you're available for those critical hours to do some tidying up __________________ Porno Flixxx Submissions SOTI Site Submissions Free Porn Resource Submissions Last edited by MrYum; 2006-02-18 at 02:31 PM..

2006-02-18, 04:00 PM	#5
tigermom You can now put whatever you want in this space :) Join Date: Dec 2005 Posts: 893	If it's a simple static site, it shouldn't be much of a problem, just have the old server still serving the site for 48-72 hours after you change the dns, like Mr Yum suggested. That way users who are still directed to the old server are able to see the site. If it's a dynamic site with forums and such, then it's a little bit more complicated but perfectly doable. My admin transferred my largest site today with huge forums (over 15k registered users and lots of active posting). There was zero downtime in the process. __________________ XLEF

2006-02-19, 10:48 AM	#7
Matt Collins Aw, Dad, you've done a lot of great things, but you're a very old man, and old people are useless Join Date: Jun 2005 Posts: 24	A good host will help you move your content from the old host and if the old host is worth a shit, he'ss cooperate with your move also. That's how you can tell the good guys from the bad guys. Matt __________________ www.revsharehosting.com ICQ: 254-829-586

2006-02-19, 11:34 AM	#8
keyDet If something goes wrong at the plant, blame the guy who can't speak English Join Date: Mar 2004 Posts: 36	Yup, downtime during a change of hosts is unacceptable, it is not such a difficult process for a host. In a nutshell, upload your site to the new server, check it out, then, if you have access to DNS zone modification, change the IP of the domain(s) to point to the new server instead of the old. Your old nameservers will then send traffic to the new server. This way traffic will go to the new server immediately, unless you have the old domain cached (which usually never lasts longer than an hour or so). Then switch nameservers, and dump the old server after about 2 days or so. There will be no downtime if you do it this way. __________________ Paravirtualization & Hosting since 2008

2006-02-19, 10:20 AM	#6
SirMoby Jim? I heard he's a dirty pornographer. Join Date: Aug 2003 Location: Washington, DC Posts: 2,706	A good host will handle most of the move for you. One thing that they should also have you do is use a temporary hosts file and surf your new sites before they make changes to the actual domains. This should all take place at least 3 days before hand. Working with your new host is the best way to go.

2006-02-20, 09:32 AM	#9
SexycityBrian If something goes wrong at the plant, blame the guy who can't speak English Join Date: Apr 2005 Posts: 38	the best way is to change the ttl for you dns records to 5 minutes and wait 72 hours. Move your data to the new host. change the dns information to the new host (ip) in 5 minutes you are moved. Now if you cant do this then. Get the new host to set up the dns records for you with the current ip and set the ttl to 5 minutes once everything is moved have the new host change the dns records and again in 5 minutes you will have resloved to the new host

2006-02-21, 01:45 AM	#11
Lenny Aw, Dad, you've done a lot of great things, but you're a very old man, and old people are useless Join Date: Mar 2005 Posts: 26	Jeez there's some complicated answers in here. It's really simple....tell the new host to move everything and call you when they're done....then change the DNS at the registrar. DONE