I'd personally recommend taking a full cPanel backup and then copy the tarballs over to the new server and then restore them. That way is more stable and reliable that using the account transfer procedure. Using rsync is a very bad idea unless you want to have to create a lot of things by hand on the new server first and then have to fix file ownerships - which is neither reliable or a stable way to do it.
How to?
Make a full backup of an account from it's cpanel to a local folder then upload into the new server... but... do I have to create first an new account on the new server with the same domain name?.... and then upload to the new account... and from the new account process to restore the backup file..?
Make a full backup of an account from it's cpanel to a local folder then upload into the new server... but... do I have to create first an new account on the new server with the same domain name?.... and then upload to the new account... and from the new account process to restore the backup file..?
Just copy all backup tarballs from your backup directory (/backup/cpbackup/daily weekly or monthly, as fresh as you want) to the new server using SCP command, then configure backups on the new server, create a directory at /backup/cpbackup/ANY_FOLDER and put your tarballs there. Last step, run "Restore Multiple Backups" and restore all backups from the folder you created... , that's all, after the restore process all account should be recreated and completely restored in the new server
Transfer account will be best as it will fetch latest file/database updates. What I do is start a transfer of multiple accounts and watch the progress. When each account is trasfered and created successfuly on the new server, I immediately change dns so that it points to the new server. (you can either change name servers at the domain or change the ip-s in your old servers's dns server). You could also reduce one day beforehand the dns refresh of your current server, so that old ip-s dont get cached for a long time in dns servers around the internet.
I would suppose that this way is as quick as the backups method because they both involve the same operations like dups, gzipping, etc.
I would suppose that this way is as quick as the backups method because they both involve the same operations like dups, gzipping, etc.
No, backup restore is not a bad idea, it's generally regarded as the best way to move accounts.binaer said:
The transfer procedure is fine if you have small sites to move, but anything that is quite large could result in network timeouts and the forums are littered with such problems.
Help
I have the tar full backup that has everything in it from my site, php stuff to mysql stuff.
How do I put it onto my new server and make it as if it was my old one?
P.S. I no longer have the old server, I have servral of the tars though. I don't know where to find servral functions you mention, such as "run "Restore Multiple Backups""
help, thanks!
I have the tar full backup that has everything in it from my site, php stuff to mysql stuff.
How do I put it onto my new server and make it as if it was my old one?
P.S. I no longer have the old server, I have servral of the tars though. I don't know where to find servral functions you mention, such as "run "Restore Multiple Backups""
help, thanks!
incase i want to transfer 300+ websites (about 10GB of disk space), what if i open whm from shell? so i ssh to my new server then open whm using text based browser like 'links'.chirpy said:
does it will help reducing the networks timeouts problem?
AFAIK, that won't work, and if it did, it wouldn't make any difference as the same mechanism is still being used. Backup and restore is still the most reliable method to use.
