How should I migrate multiserver setup using the migration tool?

Discussion in 'General' started by DarkoD, Aug 27, 2019.

  1. DarkoD

    DarkoD New Member

    Hi all,
    I have been tasked with migrating an ISPConfig3 multiserver setup to new VMs. Hoping that it would simplify the process we also got the Migration Toolkit.
    Unfortunately the website offers instructions only for single server migration and I feel key info is missing for multi server setups. So I wanted to ask for advice here to avoid messing up things.
    The setup is the following:
    Master node with only the ISPConfig CP on it. No other roles.
    Slave node for web, lets say web1. It has the web, file and db server roles.
    Slave node for mail, mail1. It has only the mail role.
    2x Slave node for DNS, ns1 and ns2. Only the dns role.

    I started with the VM of lowest importance, the ns2. The migration tool instructions say you need ISPConfig on the new VM, so according to that I installed it in single server mode. I did NOT install bind9, which was probably my mistake, but the instructions say you need to add software only if using the ispcopy tool, not the migration tool. After that the ./migrate seemed to run correctly. However I saw no zone files in /etc/bind, maybe because bind9 was not fully installed like I said.
    Also I didn't know what to do to "point" it to the master. I tried uninstall.php and then install.php. It showed up in ISPConfig but no zone files yet. I tried Resync but maybe I didn't select correctly the checkboxes because it didn't help.
    At this point I ran out of patience so I simply destroyed the new VM and started with blank VM, installed ISPConfig (no migration) and added it to the multi setup. So you can say I have ns2 migrated now, but it was in a "dirty" way. I didn't actually migrate anything, just destroyed one node and added a new one.

    I was able to get away with this because it was ns2, but the other nodes I need to migrate, one way or the other.

    Can someone please give me the steps how to migrate multi setup with the migration tool? Or without it if there is a better, recommended way? I have googled around and have seen some advice for migrations by copying files, but not sure what is best to do now because I also have the licensed migration tool.
    And how complicated is the master migration gonna be? That scares me a little, especially after the issues I had with the simple ns2 node.

    Thanks a lot in advance.
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    You mix up Migration Tool and ISPCopy here. For the Migration Tool, you must have a fully working ISPConfig system on the new server's). For ISPCopy, you don't. But do not mix ISPCopy and Migrate Tool, using ISPCopy first and then the Migrate Tool is not a good choice and will probably produce a mess. Either use the Migration Tool or ISPCopy to do your Migration, but not both. To Migrate a multiserver setup to a new multiserver setup, the migration tool is the right choice.

    The steps to migrate a multi server setup to a new multi server setup are basically the same that you use for a single server, so you can use this guide for it:

    Your new setup is currently messed up, reinstall it to ensure that you get a working setup.

    The steps are:

    1) Install a new ISPConfig Multiserver setup (Operating system, services, and ISPConfig) in the way you want it.
    2) Run the Migration Tool on each node of the old server (except of ns2 if ns2 is a mirror). When the Tool asks for the connection to the new ispconfig system, enter the details of the new master server, the tool will then show you a list of slave servers where you can select to which slave node the data shall be migrated.

    If your master server runs just the ISPConfig Interface and no websites, mail accounts or dns records, then you can skip running the tool on the master.
  3. DarkoD

    DarkoD New Member

    Hello Till,
    Thanks for the reply. I never used the ISPCopy, I was just trying to give as much info as possible and make a comparison but it created a confusion it seems. Also it looks to me like I misunderstood how the two tools work and which one needs to have the services installed before hand and which doesn't.

    Anyway, according to you the correct way for the migration is to do completely new setup:
    Master with ISPConfig to act only as control panel
    Slave nodes for web+db, mail and 2x dns

    In the new setup I do not put any data at all, right? I just install and leave it blank.

    Then using the Migration Tool I enter details of new master and it allows node selection. You see, this information is very important and because there is no manual for multi server migration there is no where to read it.
    I use this to migrate each node and no need to migrate the master because it is holding only the CP.
    For the mail node migration, is it best practice to stop postfix service first? To avoid mail coming in during the migration/copy of data.

    Can I create the new nodes with newer OS, does the Migration Tool require the OS to be identical? Old nodes are running ubuntu 16.04 and if it is supported by the migration, I would install the new servers with 18.04.

  4. till

    till Super Moderator Staff Member ISPConfig Developer


    The tool allows you to resync data (see last chapter of the tutorial). I would proceed like this:

    Migrate the email server node, test it, when you are satisfied with the result, stop postfix and run a resync, then switch the Ip or domains over to the new server.

    Yes, you can even use a different OS when the Migration tool is used.
  5. DarkoD

    DarkoD New Member

    Now the process is much clearer. Thanks a lot, appreciate it.


Share This Page