[Solved] Migrating coudpanel to new Server with local Database
Im in the process to migrate our cloudpanel installation from Windows Server 2012 r2 to Windows Server 2022.
We’re currently using a locally installed SQL-Express instance for cloudpanel.
For the new server we will also install a local SQL-Express 2017 instance for cloud panel to use.
So, according to this post: Migrating Cloud Panel to new server – Support – Know More IT Forum
I would do the following:
1. Install IIS and SQL-Express instance on the new server
2. Install the same version of cloudpanel, as on the old server, point it to the new sql instance and let it create a new database
3. Since we have a new SQL Server, I would drop the new database on the new server and then backup the databse on the old server, transfer it to the new server end restore it there
Would this be the correct procedure, or would you recommend a different approach?
In the end, the CloudPanel Migration as described in Jacobs first answer to this question, has worked.
The Problems we had after shutting down the old domain controller were solved, by removing the Global Catalog (GC) role from the old domain controller.
Thanks for the feedback and the information.
Since the new database instance is on the same server as cloudpanel, the databse connection in the settings.xml, was allready pointing to the correct database.
Everything seems to be working.
However, I noticed, that the new settings.xml only contains the database connection, while the old one contains a lot more, is this expected?
I have one problem, last week, before I migrated cloudpanel to its new server, I installed a new domain controller, moved all FSMO Roles to the this new DC, and changed the configuration in cloudpanel configuration to use the new DC.
After that, everything seemed to work as expected, and so, today I migrated cloud panel to its new server.
Now, when I log on to the new CP server and go to any customers users and click on any of these users, I received an error, that the old DC isn’t operational (see the attached screenshot), which is true, as the old DC is currently shut down.
Note i blurred the FQDNof the DC on the Screenshot, but it’s defentively the old DC it’s refering to.
That’s exactly, what I did last week, and the new DC is correctly configured there, any other suggestions?
When I start the old DC, everything starts working again,
There’s not mutch in the event logs, what I don’t get is, why is the old DC mentioned in the error message?
I would expect, that the error would mention the new DC, which is configured in cloudpanel.
I tried to set cloudpanel back to the old DC, rebooting the cloudpanel Server and then set it back to the new DC, but that didn’t help either.
Email sent 🙂