Hi, I have a multiserver setup and a few websites which are using a lot of space. I would like to move one of the sites to another server, is this possible to be automated that when I change the server in ISPConfig all is migrated automatically or do I need to do this manually?
You'll have to do that manually. the easiest way is probably to create the site again on the new server, as you can have the same domain twice unless they are on the same server, and then move over the content of the site. I'm working on a way to move sites between servers, but that's not ready yet.
As you have a multiserver setup i assume you have dedicated server for the databases. You don't have to worry about the database or database user for that webspace at all.
You asked about the database user and this can be re-used, so no need to create another one. The database must be created on the new server of course, but you can re-use the same user. MySQL port does not need to be open as MySQL users are always local to the database anyway.
i've done this with a lot of sites recently.. lower the ttl on any A/AAAA records that will end up changing.. (to at most 600) give that time to propagate. make sure the user account has rights to use the new server.... add the new webserver to the users limits template both webserver and db section. update the server_id field for that website (also any aliasdomains, subdomains, vhostaliasdomains, or vhostsubdomains), db, ftp user, ssh user etc.. as applicable in the web_domain, web_database, ftp_user, shell_user, tables in the dbispconfig database on the master.. (also possibly web_folder, web_folder_user tables if webdav is configured. resync the necessary services on the new server in the ispconfig gui.. rsync the contents of /web (or any other folder if another docroot outside of web is used) export the database on the old server, import it into the new server. edit your local hosts file to point the domain to the new server and test.. (shouldn't be any problem.. but test it first anyway) if all's ok.. disable the site on the old server to ensure no new changes.. a2dissite for apache.. or delete the symlink in sites-enabled and restart apache or nginx. rsync the /web folder from the old server to the new server again. export the database on the old server, import it into the new server again. update the relevant dns records to point to the new server. re-apply the letsencrypt certificate (if used). check everything's working as expected.. maybe give it some time to ensure no new problems appear.. once happy.. clean the site off the old server. this should ensure no interruption to the site's hosting of more than 10 minutes, but it's usually nowhere near than long.
