Portal Home > Knowledgebase > Articles Database > Changing reseller hosting
Changing reseller hosting
| Posted by jrottman1, 02-08-2007, 09:25 AM |
| Hey,
Whats the most graceful way to switch reseller hosting if you have clients that you are currently hosting. I would like to swich to another host that offers reseller hosting, but I do not want to disturb, or at least have minimal disturbance to my hosted clients. Thanks for your help!
Jason
|
| Posted by rv_irl, 02-08-2007, 09:32 AM |
| It depends on what control panel you are using..
Example on cPanel/WHM would be to simply migrate all accounts either by direct WHM to WHM or by uploading cpanel backups to the remote host and restoring them. Before the migration completes, change the nameserver IP's so when all files are fully transferred, it reduces propagation time..
However due to propagation, it is recommended that busy dynamic sites such as forums are temporarily closed as some users could be directed to the new server and some to the old (resulting in posts "disappearing")...
|
| Posted by jrottman1, 02-08-2007, 09:53 AM |
| The propogation is what I'm concerned about. The only kind of hosting that I do is I host a customer relations management application for different clients. This application is constantly making database calls. I dont really want to to close it because then the support desk would be closed for the clients I host for, this I can not have happen.
|
| Posted by rv_irl, 02-08-2007, 10:10 AM |
| It is possible, but will be difficult.. You should contact the host you are moving to and see what solutions they have in place to assist in this migration..
|
| Posted by aodat2, 02-08-2007, 10:28 AM |
| Well... I did it once before I think.
It's kinda complicated yet at the same time requires a very good relationship with the losing host. Haha...
1. Transfer the data over to the new host. At the same time, change the NameServers to reduce propogation time.
2. Tell your losing host that you would like to change the "A" records and "MX" records so that it is pointing to the new server instead of the OLD server.
That's usually how I reduce downtime but sometimes it doesn't work as a lot of the losing host would NEVER do that unless they are really nice. If you get them to do that, all traffic to the old host will automatically be directed to the new server as the records show that they are on a different IP.
Hope this helps. Actually, hope I explained it correctly.
|
| Posted by BrettB, 02-08-2007, 10:51 AM |
| Some hosts will enable the feature to edit the DNS zones yourself, in which case you wouldn't even have to contact the previous host to have them change the records. This method is effective in reducing the propagation time (any is only limited by how soon you can get the data transferred and the zones updated).
Good luck migrating your clients!
|
| Posted by Shaw Networks, 02-08-2007, 02:23 PM |
| Most hosts will transfer your websites for you from your old server to their new server. To ensure no downtime, don't switch your websites' nameservers over to the new pair until all of the accounts have been successfully restored.
|
| Posted by icecreams, 02-08-2007, 03:13 PM |
| What I suggest is to do this during the night say after midnight. Transfer the files to the new account and once you have done that point your dns nameservers to the new account.
Doing it this way you shouldn't experience any down time. It would be a good idea to inform your clients of the move as well.
|
| Posted by Nnyan, 02-08-2007, 06:43 PM |
| I had to switch over a hosted application a few times and even though DNS prop is pretty darn quick nowadays there is still some lag.
As stated in previous posts:
1. schedule (as best you can) the DNS transfer for the time of least use.
2. Migrate everything over to the new server (prior to DNS transfer) and validate that everything is working (I do this even if I have to later update data files).
3. Give your users a method (IP instead of name, custom host files or modding the dns records) of reaching the application during transition.
4. Notify users of potential downtime.
|
| Posted by Swelly, 02-08-2007, 07:40 PM |
| Perfect example. Also registars will allow you to create multple nameservers or have multple nameserver. Just add your new nameservers and still keep the old ones until the new ones propagate.
PS: Now I am cross-eyed.
|
| Posted by kentcounty, 02-08-2007, 08:49 PM |
| Does it really work?
I was looking at doing something like this for a reseller account I switched. So I would simply switched the domain A record IP for the new one in dns zones?
|
| Posted by Website Rob, 02-08-2007, 10:55 PM |
| One of the most helpful areas for this is to make you are using Personalized Nameservers -- with the old Hoster and the new. By having your Clients use your Nameserver, there are no DNS changes on their end. For yourself, you simply update your Nameserver IPs after the files have been transferred.
Scheduling the file transfer in the off-hours, early morning usually, means you have a good chance of the file transfer -and- the updating of Nameserver IPs, all being done and propagating by daylight.
No matter what you do, always make sure to advise your Clients when changing Hosters. Even if they don't have anything to do, they should still be aware of what is going on.
|
Add to Favourites 
Print this Article
Also Read
