New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Move a WHM from one server to another - any simple guide/best practice?
Hello, I'm pretty new with WHM/Cpanel (or used cpanel a lot before, but not WHM).
We have a server with a couple of hundred sites in WHM/Cpanel. I want to just setup a new clean CentOS 6.9 installation, and just move all accounts from the old server to the new.
I'm used with Virtualmin, and there it's really simple to just move all sites from one server to another. How easy is this with WHM? And will all of quotas, packages etc also be easy transferred?
What is best practice around this? I'm sure you guys are moving WHM's between servers on daily basis? 
Comments
https://documentation.cpanel.net/display/ALD/Transfer+Tool Does this help?
You can use transfer tool?
So, since the hardware and OS will be the same on the new server, this tool do all the job?
Yes make sure php and mysql versions are also same.
Ok, but will all server (WHM) settings also be transferred? We have different plans with different quota settings, or do we need to create all plans on the new server?
You can copy the packages, it's in the documentation here
https://documentation.cpanel.net/display/ALD/Transfer+Tool#TransferTool-Howtocopypackages
As I remamber everything will be trasferred.
So just to be clear, I setup the new server, make sure Mysql and PHP versions is the same as the old server. Then install WHM/Cpanel using a default key, then use the transfer tool, and then use the old license key on the new server?
Just install whm and other plugins to avoid error and the use transfer tool, then you just need update your license ip from your license reseller
You could split nameservers as well, NS1 to one server, NS2 to the other, and then have it suspend on old as they migrate. Helps a bit when you have a shit-ton of domains.
We have taken over the server, so don't know if we know where the license is from.
But, if we just use the same IP (both internal and external) on the new server as soon as we have transferred the sites, it will not be any issue with the license?
Ok, but the new server will be in the same DC and Vmware server as the old, and we will use the same IP's as before.
Uh, how many domains you talking about? You're gonna have some fun if you're trying to keep the same IPs as well.
It would be more beneficial to find where the license is from, whether you can get access to the licensing account, whether it was included with your server take over or whether you need to purchase your own.
Around 200 - so the transfer tool changes IP's on the domains when we transfer? But maybe I'm wrong, but it should be possible to setup a server with different internal IP's but both servers have the same external IP? We have no plan to change the external IP.
It's the same company, same owner, but different people working there. And the old employees was not good at documenting things. But most likely we can find the information.
I don't understand the logic in this. You're using the same VMware server? What are you looking to accomplish? Why the need?
The old server has lots of disk and partitions, and we don't have full control over the installation, firewall etc etc. So in stead of using lots of time to clean up, we just want to setup a new server and move everything from the old to the new.
But we are using the same VxRail in our own DC.
Here's a copy from an internal reference log we made for a recent migration. Lots of things to remember, and I'm sure there's more things we did that we never had a chance to write down - you just need to make sure you get the new server 100% production ready and tested before deploying anything onto it. If you use the Transfer Tool and have custom Cloudlinux LVE settings, I don't believe those transfer over - so you should double check them.
I went from el5 to el7 using the cPanel bulk migration tool, it was super easy, just make sure the versions (at least major) match up on both servers for php/apache/sql etc you can then upgrade everything post migration.