Skip to main content

Migration cPanel accounts on new hardware keeping same IP

Comments

12 comments

  • cPRex Jurassic Moderator

    Hey hey!  This plan sounds good to me!  The Transfer Tool will change the IP address inside the DNS zones as part of the migration, so they will have the IP address of the new machine.  You'll likely want to disable the Live Transfer feature (https://support.cpanel.net/hc/en-us/articles/360051837674-How-to-disable-the-Live-Transfer-feature-in-Transfer-Tool) so traffic isn't proxied to the new machine.

    for step 7, after you have confirmed this work is indeed possible from your hosting provider and have adjusted the networking configuration, you can use the IP migration wizard to update the IPs on the system:

    https://support.cpanel.net/hc/en-us/articles/12168248438039-How-to-use-IP-Migration-Wizard

     

    0
  • Internet

    Hello,

    cPRex thank you!
    What about service version on the old server? We upgraded Mysql to version 8.
    Easy Apache on source server is Apache 2.4, PHP 7.2, PHP 7.3, PHP 7.4, PHP 8.0, PHP 8.1, PHP 8.2, and PHP 8.3 and on new server is Apache 2.4, PHP 8.1, and PHP 8.2.
    Is there any other service on old server that we must check version for it?
    What about DNS Only server during process of migration? Will old DNS Only be up until the moment when we should set again  IP adress of old DNS Only server on new DNS Only?

    How we could test websites after we finished Transfer Tool? With new DNS ip address in zones?
    Before shutdown old server we must delete the DNS clusters in WHM’s DNS Cluster interface (WHM » Home » Clusters » DNS Cluster)? Is this correct?
    Then we will shutdown old server.
    Change the target server main IP address to the source server IP address.
    Check the IP addresses of the transferred accounts.
    Check and update each account’s IP address with WHM’s IP Migration Wizard interface (WHM » Home » IP Functions » IP Migration Wizard).
    Configure your target server’s DNS zone files.
    In WHM’s Basic WebHost Manager Setup interface (WHM » Home » Server Configuration » Basic WebHost Manager Setup), select the same hostname, shared IP address, and nameservers that your source server uses. The system will configure the DNS zone files of restored accounts on the target server with those settings.
    Add the target server to the DNS cluster.
    We must configure DNS Cluster with new API token (different than on old cPanel&WHM and DNS Only cluster). Is this ok?

    Best regards,
    Elizabeta

    0
  • cPRex Jurassic Moderator

    The PHP versions you choose to install are completely up to you.  You can find a chart showing the versions of PHP available on various operating systems here:

    https://support.cpanel.net/hc/en-us/articles/4412144152855-What-versions-of-PHP-does-cPanel-support

    The DNSOnly server will be live until you turn it off, as that really isn't related to the migration.

    We outline two different options for testing your websites after the data migration is complete at this link:

    https://docs.cpanel.net/knowledge-base/technical-support-services/cpanel-migration-services-and-guides/#test-your-websites-after-you-migrate

    You don't really need to do anything with the DNS Cluster machines so I wouldn't worry about those at all.

    0
  • Internet

    Hello,

    Thank you for your answer!

    We installed cPanel & WHM on new target server .
    To transfer accounts/configurations between cPanel servers, we  used the transfer tool and transfer process finished successfully.
    Before we started Transfer Tool we deleted DNS Cluster on old server.
    Then we did next steps:
    1.Shutdown old server 
    2.Changed the new server main IP address to the old server IP address
    3.Run the /scripts/mainipcheck command to add the IP address to the /var/cpanel/mainip file.
    4.Run the /scripts/fixetchosts command to add the IP address and hostname of your server to the /etc/hosts file

    5.Checked the IP addresses of the transferred accounts
    When you transfer your accounts to the target server, the system may set the accounts’ IP addresses to the target server’s original main IP address. Check and update each account’s IP address with WHM’s IP Migration Wizard interface (WHM » Home » IP Functions » IP Migration Wizard).

    6.Configured our target server’s DNS zone files
    In WHM’s Basic WebHost Manager Setup interface  , select the same hostname, shared IP address, and nameservers that your source server uses. The system will configure the DNS zone files of restored accounts on the target server with those settings.

    To change hostname  we edited  WHM » Home » Networking Setup->Change Hostname?
    To change Nameservers we edited  Nameservers in WHM » Home » Server Configuration » Basic WebHost Manager Setup 

    But, now in dns zones of account there is both nameservers which is not ok.

    There should only be two current nameservers, not the old test ones that are currently authoritative.
    In (WHM » Home » Server Configuration » Basic WebHost Manager Setup) there are nameservers ns3.testwh.tel.net.ba and ns4.testwh.tel.net.ba.

    How to make only the authoritative dns nameservers to be placed in the zones (no test nameservers before migration) ??

    Thank you!

    Best regards,
    Elizabeta


    0
  • cPRex Jurassic Moderator

    I edited your post to remove the DNS names.

    There isn't a way to keep that from happening, but notice they are commented out.  You can always manually remove those comments if you want once you are done with the transfer work.

    0
  • Internet

    Hello,

    So, you suggested to us to manually change nameservers for each zone and instead old test nameservers put nameservers from migrating server?
    Is there any script for this? If there are many accounts (1000) on server which are transferred via Transfer Tool I must change nameserver for each zone?

    Best regards,
    Elizabeta

    0
  • cPRex Jurassic Moderator

    No, you wouldn't need to manually update anything.  If you look at the zone file you'll see the old lines start with a ";" which indicates they are commented out and only there for reference that the domain has been migrated, but that won't cause any problems with the DNS functions.

    0
  • Pippopluto

    Hi, sorry if I reopen this thread, but it is related to the same subject.

    Old server IP: xxxx

    New server IP: yyyy

    I have done the transfer of the accounts then changed the new server's IP address and assigned the old one (xxxx).

    All account zones still contain the previous new server IP (yyyy).

    I have my servers on aws. So cannot use the migration wizard (because of the NAT achitecture).

    Ran the multi account function "Change multiple site's IP address, but to no avail.

    I manually changed dns zone for my ns1 and ns2.

    ns1 was the old server -now the new one. ns2 a DNSONLY server.

    Having stopped the clustering before the transfer I have the correct zones on ns2 (previously the cluster architecture was ns1 synchronising to ns2 as "Standalone". 

    I tried reactivating the cluster with reverse architecture (ns2 synchronising to ns1 -now the new server), but haven't got ns2 zones copied to ns1.

    Any suggestion? Or shall I resolve to manually update all of the account's zones?

    Thanks,

    Roberto

    0
  • cPRex Jurassic Moderator

    Pippopluto - does the IP address show the correct IP in WHM >> List Accounts?  If not, you'll want to change it at the account level and not just in the DNS zones.

    0
  • Pippopluto

    Hi cPRex,

    thanks for getting back.

    Yes, in List Account the IP is correct: xxxx

    Zones still show yyyy on all records.

     

    0
  • cPRex Jurassic Moderator

    I think the only option in that case would be to manually update the zones.  We do have a script for that which may help you automate the process:

    https://api.docs.cpanel.net/openapi/cpanel/operation/DNS-swap_ip_in_zones/

    0
  • Pippopluto

    Ok, thanks for pointing me to the script. I'll have a look.

    All the bests.

    0

Please sign in to leave a comment.