migration 3.1 to 3.2

Discussion in 'General' started by adeptt, Nov 16, 2020.

  1. adeptt

    adeptt New Member

    Hi, We currently have version 3.1 running but need to migrate to a new server. We have a couple of questions

    1. this migration how too is great but does it work with ispconfig 3.2? Is there a new help for migrating 3.1 to 3.2?

    2. We want to create the new server and run a different domain on it to test the email migration but would like the new server to run the old the domain once testing is complete. How do you change the main domain the new server is using to the source servers domain. DNS is easy to point to the new server but would like to know how to change the main domain the new server uses.

    thanks as always
  2. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    1: It works fine with 3.2. You can just update to 3.2 on your source and install 3.2 on your target.
    2: I would just use the current name, changing it can result in mistakes because the chance of missing something is big. You can easily add a test domain to ISPConfig and test around with that.
  3. ahrasis

    ahrasis Well-Known Member

    The tutorial for upgrading ISPConfig from 3.1 to 3.2 is here: https://www.howtoforge.com/updating-ispconfig-3-1-to-ispconfig-3-2/

    I would also advise the undo the installation based on LE4ISPC tutorial if you did use it on current server(s) as ISPConfig 3.2 uses LE hooks to create LE SSL certs for the server, create and renew ispserver.pem and restart all services secured by them upon renewal.

    In my view LE hooks are better that relying on incron though both are event based but the most important thing is, LE hooks come with ISPConfig 3.2.
  4. adeptt

    adeptt New Member

    Thanks for the information. Both these scenarios involved updating the source server to 3.2. We already attempted to do that and it bricked the server and needed to restore from a backup image. So we want to create a brand new server, install 3.2 then migrate the data from 3.1 to it. This would also limit downtime on the source server. Is there a document on how to do that or any other recommendations for our scenarios? Does the sync tools in the ispconfig gui work with 3.1 to 3.2. Thank you for any information.
  5. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    Use ISPConfig Migration Toolkit.

Share This Page