Migrating plan

[ricardo]

I going to change from a legacy vps to a HSPC vps.

But I need a good solution to minimize the migration problem:
- Downtime
- Lost mail's
- Repeat mail's
- Etc.

I can't wait the 24/48 hours !!


I'm looking to something like this:
- Change ns1 and ns2 at my registrar
- Traffic will continue (for 24/48) arriving to my old vps, for that reason I want to edit dns and point the A record to the new IP at the new vps

Support told me that this will not work, but I fell that there is a better solution that wait a maximum of 24/48 hours

[ikaruz]

Hi Ricardo
Do you have any control panel?
Because if you have cpanel for example, at WHM it's a migration tool for multiple accounts.
You may also cluster your dns servers on the new and the actual so any IP change will be done by the WHM when you move the account.
Again, if you have a cpanel, there is a lot of info at the cpanel forum regarding this.

But imagine you may achieve the same that cpanel does from the console with rsync and some linux/scripting knowledge

We have done this a few times with WHM/cpanel, if you do this at night, no one has to know that you moved accounts across servers.

[ricardo]

Hi Ricardo
Do you have any control panel?
Because if you have cpanel for example, at WHM it's a migration tool for multiple accounts.
I have cPanel on both vps (same version) and both at PowerVps.
Already transfer cPanel without problem (when my vps fail and I need to reinstall).
The only problem I have is the DNS propagation time.



You may also cluster your dns servers on the new and the actual so any IP change will be done by the WHM when you move the account.
Again, if you have a cpanel, there is a lot of info at the cpanel forum regarding this.
Could you please explain it better, this could correct the DNS propagation time ?


But imagine you may achieve the same that cpanel does from the console with rsync and some linux/scripting knowledge
My idea is to do the whm transfer and after that a rsync, but my knowledge is linux is very poor.


We have done this a few times with WHM/cpanel, if you do this at night, no one has to know that you moved accounts across servers.
Exactly that is what I want to do.

[ikaruz]

Thats easier :)

With the dns propagation, if you have the defaults, yo should have 4 hours for propagation. If that is not acceptable, you may go to the cpanel forum and look for some tools to do that bulk change.

If you cluster your DNS servers, the only thing you have to do is change the registration IP of the name server from the old one to the newone. For example, you have ns.yourdomain.com at old IP you ask your registrar to modify this value to the new one. This way you don't have to make any other change. Same for ns2......

This should be acceptable because this is propagation of an A record, not the nameserver record that last longer. (Even thought, if you kept both VPSs clustered, you shouldn't have problems with propagation, because you will have the same info at both dns server at both VPS)

And regarding the transfer tool, you only need the WHM tool. It's very easy if you have root access.

So, if you want a step by step, can be something like this.

1. Cluster your DNS servers and synchronize all records to the new server.
2. Change nameservers IPs at your registrar.
3. Move accounts across with "copy multiple accounts" from WHM
4. Verify that the account was moved fine
5. Delete the accounts from the old server but being careful that check the box that says "kept DNS zone record"

Thsi is the simple way to do it. With more knowledge you may add more steps, but this works fine, and it's very simple.

[BornOnline]

I pretty much followed this guide and setup DNS clustering during the migration...worked well.

http://forums.cpanel.net/showthread.php?t=18294