Hi,
We are looking for the best practices for the migration we are trying to migrate from 7.9.1 to 10.8.1 and from Zip to Docker. our main concern is Server ID and the actions that might affect it Since we are limited to request once to re-issue the license.
Thanks
SonarQube Server / Developer Edition 7.9.6
Zip
Trying to install a new server (Currently is 10.8.1) on Docker and import old data to the new server
Installed the new server on docker and contacted contact@sonarqube.com but some questions not answered
We are looking for the best practices for migrating DBs while we don’t know it affects on Server ID or not, if we request for a new License any action after that can affects the server ID? Like importing the data or changing the server name.
Basically, don’t change your JDBC URL and you should be good.
Keep in mind that you need to hit all the intervening LTA versions, so: 8.9, 9.9, and then go ahead and finish the work by ending with the now-current LTA: 2025.1, released last week.
On the platform side, I would get the database migrated through to 2025.1 before tackling the zip-to-Docker portion of this. Only change one variable at a time.
Hi,
I appreciate your response. From what I understand, most cases affecting the Server ID are database-related.
So, if we need to change the server’s IP address or name (OS or web console), it will not affect the Server ID or license, correct?
FYI, we are replacing the server but will keep the same URL, DNS name, and possibly the IP address. Will that be okay?
This would help us avoid making numerous changes on the Jenkins side, as we need both servers to be active to keep our production (CI/CD) running while configuring the new server until the final switch.
Thanks
I think i can answer your question when it comes to licensing.
Based on my experience, your current license will get invalidated if you changed your database name to a new one. Like for example in my case, I usually create a new database name inside the DB server that’s provisioned for my Sonarqube everytime I do an upgrade. After creating, I shutdown Sonarqube service and dump it’s current db contents to my VM and afterwards import the contents into the newly created DB name. Since my newly created DB name has a content already, i’m going to point the new version of Sonarqube to the newly created DB, the reason being is that in case I need to go back to my previous version of Sonarqube, there’s something that I can go back to. Once I started the new version of Sonarqube with the new db name, the new version will convert and read all of my data from the previous Sonar version and make it “readily available”. Granted that the instance starts up, go to Administration > Configuration > License Manager and you will see there that it will prompt you for a new license. The newer binaries / installer of Sonarqube will give you at least 5-7 days of temporary access to the newly instance that you shared, that’s enough time for you to ask for a license from contact@sonarsource.com
For your current scenario, I think what you need to establish is if you can jump from 7.9.6 to the latest 10.8.1. That is one long of a jump.
For your question again " ** We are looking for the best practices for migrating DBs while we don’t know it affects on Server ID or not, if we request for a new License any action after that can affects the server ID?* Like importing the data or changing the server name."
In my experience, it affects the Server ID which will ask you to provide a new license IF you change your DB name. If you didn’t change your DB name, there shouldn’t be any issues.