cPanel Migration with minimal downtime

binarycubes

Registered
Jun 1, 2009
1
0
51
I am trying to migrate from one cpanel server to another without having the clients change their nameservers at their registrar. I do have full control of both the old and new server. Is there some way I can achieve that with minimal downtime?
 

jasonhk

Well-Known Member
Nov 11, 2005
48
0
156
Lower the TTL's and use cPanels express transfer option. Assuming both servers will be online at the time of the move, there actually won't be any "downtime" you might have some users pointing at the old server and some at the new, so the issue here is just mail and database syncing.
 

cPanelDavidG

Technical Product Specialist
Nov 29, 2006
11,212
13
313
Houston, TX
cPanel Access Level
Root Administrator
If both servers are running the latest 11.24, there shouldn't be any noticeable downtime as the express transfer option points the DNS from the old server to the new server to minimize downtime incurred by DNS propagation.
 

PlatinumServerM

Well-Known Member
PartnerNOC
Jul 10, 2005
400
3
168
New Jersey, USA
cPanel Access Level
Root Administrator
As long as the old server stays up until the migration/propagation is done, there should not be any downtime at all. The sites should seemlessly propagate to the new server with no interruption.
 

electric

Well-Known Member
Nov 5, 2001
789
10
318
Don't forget that your customer's will need to re-register their private nameservers (if they have any) to use the IPs from the new server...
 

Spiral

BANNED
Jun 24, 2005
2,018
8
193
I am trying to migrate from one cpanel server to another without having the clients change their nameservers at their registrar. I do have full control of both the old and new server. Is there some way I can achieve that with minimal downtime?
Though the actual transfer is pretty much instantaneous, some users
may still try to access the old server because of DNS route caching
either in their own local computers or more commonly from their ISPs
but those issues should resolve themselves in a few days.

Regarding nameservers, I would recommend your making it mandatory
for your clients to host their DNS through your servers.

We made that change a number of years ago for the exact reason
as what you are now trying to do as it often becomes a major nightmare
headache when you got to migrate a server (or a large group of servers
as is the case usually) to a new IP address pool, trying to get everyone
to update their DNS settings properly, and most not knowing what they
are doing adding to the problems. Then you have to deal with all the
support tickets and the "my site is down" complaints and it becomes
a major headache that is easily minimized and avoidable if you just
controlled the DNS servers that your client's use for their domains.

With your clients using your DNS servers, you would only need to duplicate
the DNS between the old and new servers and simply update the
IP addresses for the authoritative DNS servers on your own domain
and all your clients would simultaneously get those updates for all
their domains at all their registrars without having to touch
anything at all. This only leaves just resellers to deal with alone.

Anyway, don't know your exact configuration ... just a thought.