ISPConfig 3.3 master migration

Hi,

I have a multi-server installation of 3 servers managed by ISPConfig 3.3.0p1:

• 1 server 'Web 1' where ISPConfig master is installed,
• 1 'Mail' server with ISPConfig slave
• 1 new server 'Web 2' with ISPConfig slave

Now that almost everything is transferred from Web1 server to Web2 server, I need to get rid of the web server 1, but first I need to get ISPConfig master to move from Web server 1 to Web server 2.

So what is the best method to do this?

 

Ok, but I have no choice, I need to find a solution to do that. Certainly by intervening directly in the database to change the server id, while taking maximum care to not break everything.

 

is this just to replace the old server with a newer, more powerful server?
or are you trying to switch to a newer version of the OS as well?


is everything that was on web1 still there? or have you removed it?
if everything can still run on web1, i'd go back to doing that, and then remove the web2 server from ispconfig.
then use ispcopy to copy the web1 installation to the new server.
then get rid of web1 and either set the hostname and ip's on the new server to be whatever web1 had and just go from there.
or update the slave config, and dns, to use the hostname / ip's of the new server

 

Yes it is to replace old server by a more powerful new server.
OS are different, Debian 11 for old server, and 12 for the new server.
In the end, all services on the web1 server will be migrated on the web2 server. There were a hundred of web sites on the web1, I've already moved one by one to the web2, This work has been completed.
It remains only ISPConfig itself and I'm not going to keep this server only for this, I need to find a solution to get rid of it.

 

Hello,

I'm reviving my thread because the situation has progressed since my last message.
To date, I have transferred absolutely all services provided by the main server Web1 to the new one Web2. There is nothing left on the Web1 server except the ISPConfig web interface and its database.

I have a few questions:

• Can you confirm that each ISPConfig slave server has its own database server (mariadb) with a partial copy of the database required to run ISPConfig located on the main server ?
• Do you think I can move the main ISPConfig database currently located on the Web1 server to the Web2 server, while modifying the server IDs in the 'server' table (deleting 1, then replacing 3 with 1) as well as all references to these IDs (server_id) in all other tables ?
• If so, how can I be sure I haven't forgotten any references ? Is the 'server_id' column name standardized within ISPConfig, or should I expect to look for others ?
• There must also be some configuration files to modify, but which ones ?

 

each slave server has it's own dbispconfig database, which only contains the data relevant to that server.
only the master server dbispconfig database contains all the data for all servers.

moving the dbispconfig database from web1 to web2, i guess it can be done.
i think you'll need to change more than just server_id references.
stuff in server services, server config, additional php versions etc all link through in various ways.. it's gonna be messy.
and /usr/local/ispconfig/server/lib/config.inc.php will need editing on every server.

if you can't, or won't leave the web1 server in place, i still think the safest method is to get everything on web2 back onto web1 and then wipe web2, create a new clean install of a standalone isconfig on web2 and then use ispcopy to copy the web1 server to web2

@till might be able to advise better about copying over the master database and then editing bits of it.
i just think the risk of ending up with an unusable system is too high to continue with that method

 

Thank you. I hear you, but this involves hundreds of hours of work already done in one direction, involving dozens of clients; it's no longer feasible to redo this work in reverse.
In the worst case, I would rent another less robust server, solely for the ISPConfig web interface and its databases, and I would move Web1 to this other server according to your advice using ispcopy.
In the meantime, I'm giving myself a chance to understand all the subtleties and pitfalls to avoid in my proposed procedure.
I remind you that Web2 server is already configured identically to Web1 (services, firewall, PHP versions, etc.) and that nothing is now handled by Web1. Unless I'm mistaken, I therefore don't see any cross-references other than the server IDs. Stuff in server services, server config, additional php versions, etc..., all are already ported to Web2.

 

Hello,
While waiting for a possible contribution from @till , I think about the solution to move my ISPConfig from Web1 to a new cheap VPS server with the ISPCopy tools, according to your advice.
But by quickly reading the documentation I see that there are restrictions for ISPConfig Migration Tool, indeed it is not said that it supports the 3.3 version of ISPConfig, (https://www.ispconfig.org/add-ons/ispconfig-migration-tol/). On the other hand, it is not specified for ISPCopy.
Knowing that all my servers have ISPConfig 3.3.0p1, should I worry?
Finally, last question for today, how do you advise me to do it, between ISPConfig Migration Tool and ISPCopy?

 

Hello everyone,
Would there be a charitable soul to answer my various questions?
In particular, if @till could take the time to look at this issue again, that would be great.
Thanks in advance

 

When getting new hardware, I have installed ISPConfig on the new host machines and used ISPConfig Migration tool to copy all data from old setup to new. This has worked and is not very complicated.
I would say you have created a very complicated situation in trying to do the migration in another way. You could still use the Migration Tool if you can get new host or hosts, and move the setup to there. You could then add web2 to this new setup as extra server if it would otherwise remain unused.