How to migrate ISPConfig main master server

Discussion in 'ISPConfig 3 Priority Support' started by Larry Rider, Aug 26, 2019.

  1. Larry Rider

    Larry Rider New Member HowtoForge Supporter

    My main mater server was hacked a week ago (it is on version 3.1.14p2 with debian 8.11).
    I have "cleaned" the server, but I would be more confortable with a new setup for the main master server.
    I have bought a license of the migration tool.
    But after reading all tech documents that I have found, I am not sure on how to proceed.
    Could you please explain the best way/approach for "migrating" this main master server to a new system?
    As you can imagine, the system is in production and downtime should be minimum.
  2. Croydon

    Croydon ISPConfig Developer ISPConfig Developer

    as you want to migrate the master server (probably) wanting to leave the slaves intact, you should use the ISPCopy tool that is part of the migration toolkit.
    To minimize the downtime I would recommend using the following approach:
    1. Make a first run of the ISPCopy tool
    2. prepare "haproxy" on the old server (stopped!) and set the config to forward all tcp packets on ports 80, 443, 25 etc. to the new server's ip
    3. run the ISPCopy tool in incremental mode
    4. run an ISPConfig update on the new server with reconfigure services "yes"
    5. make sure the new target is working as expected
    6. shut down all services on the old server (apache, postfix etc.), everything that might conflict with the configured tcp forwarding in haproxy
    7. run the incremental ISPCopy again
    8. directly after the tool finished start up haproxy on the old server
    9. run ISPConfig update on the new master with "reconfigure services" yes (was overwritten by ISPCopy)
    10. run ISPConfig update on all slave servers to enter the new master data (ip, mysql etc.) and choose to reconfigure master db access.
    If you have further questions please use the migration tool support form.

Share This Page