I will move my physical ISPConfig Server 1:1 to an VPS in an other location. So I install a new Debian 12 + ISPConfig following your Tutorial, buy the Migration Toolkit License and follow the Tutorial there. But the new server is in an other location with a new IPv4 and IPv6 address. Will it then work too. Also I the original server hast still to run until I have changed all my DNS, as it works a primary DNS for 7 Domains. Any hints what I have to pay attention? Regards Rainer
Yes, this will work. It's the standard case. What you describe is usually the case, so nothing special. What you should consider is if you want to use a new hostname for the new server so you get a SSL cert for it right away, or if you would like to re-use the old hostname, means you must use the IP address of the new server and let the Migration Tool connect to the Ip and not hostname, plus that you will have to create a SSL cert for the hostname later. In any case, take care to use the same Let's Encrypt client on the new system as you do on the old one.
I need a little more clarification! 1. My old server is several years old and the new one will have a later version of the LetsEncrypt client. As long as it's the same client, I assume this is OK? 2. I will re-use the old hostname to avoid users having to redo all their email accounts. when you say "... create an SSL cert later" won't LetsEncrypt create one using the new IP addresses as soon as the client is installed? 3. I assume that emails will start arriving at the new server as soon as the DNS change(s) are done. At which point is it best to do those changes. 4. How does one deal with emails that arrive at the old server after the migration is complete? As the hostnames will be the same on both servers, I can't just set MX priorities appropriately. Apologies for the handholding request but this is something I've never done before - I've always done it manually and it was always... stressful! I'm hoping that using the tool will be a lot less stressful
Yes, I referred to Certbot vs. acme.sh and not a specific version of these clients. LE will attempt it and will fail and ISPConfig will create a self-signed SSL cert instead. That#s why I said you must create it later to get a LE cert. Start with changing your DNS records to a low TTL. Then 1) Do the migration. 2) Shutdown postfix on old server. 3) Do resync using Migration tool and change DNS If mail servers can not reach your old postfix, they will typically retry for several hours or even days. There will o old email arrive as you shut down postfix.
1. finaly I decided to use the old name, less work sching DNS 2. I informed users there is now email while migration 3 I stopped and disabled postfix so no incoming mails lost, stopped dovecot too 4. I started the migration 4. when finished I compared old and new server if everythingwas transferd i stopped postfix and dovecot 5. I corrected all DNS entries as this is the primary DNS for all 7 domains 6. I changed the IO entries for primary domains at my registrar, had not to chance secondary DNS IO as it remains the same 7. waited and checked if new primary domain IP was known everywhere 8. checked entries in ISPConfig between old and new server. as noted above something was missing and I reentered it. 9 start postfix and dovecot mails worked like before, nothing lost
@till - Thanks very much for that clear and comprehensive reply. As always I'm now confident in going ahead with the moves.
