Hi. What is the best scenario to move working site (~2 TB of messages) to stronger hardware? Want to avoid unavailability of services. Should I involve ISPConfig Migration Toolkit or any other way (e.g. multiserver)? Is there somewhere HowTo/FAQ available?
Maildata? Are we talking a hardware server or is this a VM? To move from a standalone setup into another one or from single node to multiserver the migration toolkit will be your best bet. // BTW, i think this is the wrong section in the forum for such an question. Maybe someone from the team can move it
Ok so depending on your needs you can either go for a single node setup again or use a multiserver setup. If you opt for a multiserver setup there are a few more things to consider and plan out. I would virtualize the system in this process too so you don't run into hardware limitations again. Easier said then done, as this depends on what options you have available. You should ask yourself a few questions: -> Do you host on bare metal or virtual machines? -> Do you need redundancy? -> Do you need seperated Geo Locations? -> If you opt for redundancy how does it work in cases of an failure? -> Do you plan to use the same IP adresse for the host as before? -> Do you plan to use the same DNS names for the new system(s)? Depending on what you require there are a lot of things to consider
I was thinking about going to multi server installation but I think I will try to move the installation to new, single node server and maybe than buy a new machine and move to multiserver for redudancy - cause the existing server is very old. We already rent bare metal server and will stay on it as VM gives us nothing - the configuration on this machine is not expandable. Also the server is quite powerful so probably we will not hit the limits soon. We use it only for email service as websites were moved earlier to separate VMs. New server will have new IP.
I would then plan out the new setup directly as a multinode setup otherwise you will have to migrate from the new single node later once again. That's Ok. I was just asking because there are some alot of comapanies that run there on virtualization clusters. In that case you need to think about how the migration will happen as you need to change the MX records of all domains that are served by your server. It's not "hard" to do this, but you need to plan things out for your own setup too make sure a migration goes as smooth as possible
Thank you, this is very valuable information for me. I am aware of MXs... I was installing ISPConfig long ago so probably will go for the "dry run" to check out multiserver installation and Migration Toolkit as I'm not familiar with it.
1. Follow the tutorial for your preferred multi-server set up. 2. Run the migration toolkit. (dry-run is your friend until everything is ready) 3. Point your DNS entries to the new server(s). 4. Re-sync with the migration toolkit to grab any mail that delivered to the old server before DNS propagated. (./migrate --syncjobs --only=mail) If you have a dynamic website, go ahead and sync databases too. You can sync web if you have to bring over uploads. Whichever changes you may have encountered, synjobs is your friend. 5. Enjoy your favorite beverage. You earned it. Take the time to read the help doc for the migration toolkit. It pays to familiarize yourself with all of its capabilities. It takes a lot of stress out of the process.
if you're going to keep the new server on different ip's to the source server, (using same subdomains), then set the TTL on the A/AAAA records to 600 (shorter is better, but a lot of dns servers seem to ignore the ttl change if set shorter than this) a few days before you try to make the new server live. ispcopy.. copy the whole installation to another server as is.. you can re-run it multiple times, so you can do a test run, spend time checking everything is ok and working as expected, then run again to get any new db/file changes from the source server. once the time taken to re-run ispcopy is short enough that you're happy with the total downtime to switch, then put the live server into maintenance mode, re-run ispcopy, and then change the dns to point to the new server, or shutdown the old server and change the ip's on the new server to re-use the old servers ip's. (obviously do this in such a way that you don't totally lose access to the new server)
