Love the Migration Toolkit!

Discussion in 'Tips/Tricks/Mods' started by TonyG, Apr 29, 2025.

  1. TonyG

    TonyG Active Member

    I've just completed migration from 3.2.2 to 3.2.12. There wasn't a single issue with the toolkit. It performed flawlessly. For this operation that's Extremely important of course. Thank you ISPConfig team (including FOSS contributors) !!!!!!!!!!!!

    Just being social here, sharing the experience, no issues or tech details...

    Tip1: Use the Migration Toolkit occasionally to rehost and keep your environment clean.
    Now I can retire a server that had file system corruption that couldn't be repaired even with inode surgery. The related issues kept me from doing some normal operations and that got very painful. The new system with the same hardware and Ubuntu 20 updated to 22 is much faster. I look forward to more updates in OS, PHP, and soon ISPConfig v3.3.

    Tip2 for those who can use it: I've simplified the environment here considerably. Do it when you can.
    We moved out all locally hosted Postfix/Dovecot processing to the third party Mythic Beasts. And because we're hosting email there (probably servers soon too) we get secondary DNS for only $10/year. With no need for MX2+NS2 I eliminated a secondary server that did nothing else of value. As much as I enjoy working with email servers (Nerd:D) I do not enjoy the pain that comes with it, including RSpamD, RoundCube, and Sieve. Mythic Beasts runs Exim. Migrating was fairly trivial.
    Because of these simplifications, I was able to turn off local Mail and secondary DNS here, so only needed to migrate one ISPConfig system. It was a great experience and I'm happy to be done with it.

    DNS was the only challenge, though Migration Toolkit did its part perfectly. I didn't manage IP address changes correctly and needed to manually set the AXFR/NOTIFY and a few other minor details.
    The new server has a dedicated IP is outside of the prior subnet with floating IPs. I'm still running the old server with the old ISPConfig - DNS is off and there are no more public changes. So I had to change the ISPConfig server's IP and hostname, plus related external NS info. I'm enjoying external access to the old server without changing its name or IP so that I can slowly port over required scripts and other non-ISPConfig stuff.

    My environment is small compared to that of most other people here, but I still need tools that I can trust. I'm glad I found ISPConfig 5 years ago, glad I used the Migration Toolkit, and I'm happy with continue moving forward with you guys.

    Thanks!
     
    till likes this.

Share This Page