Move sonar from Amazon Linux 2 to Amazon Linux 2023

SonarQube Server / Community Build
,
1

Must-share information (formatted with Markdown):

  • which versions are you using (SonarQube Server / Community Build, Scanner, Plugin, and any relevant extension)

    • SonarQube Developer Edition v2025.1 (102418)

  • how is SonarQube deployed

    • Deployed using zip installation method

  • what are you trying to achieve

    • Migrating current SonarQube installation from Amazon Linux 2 to Amazon Linux 2023
    • Need detailed guidance for this upgrade process. We went through documentation located at Other migration procedures | SonarQube Server Documentation but did not gave clarity on step-by-step upgrade procedure
    • Specific concern about Developer license compatibility after migration to new server

  • what have you tried so far to achieve this

    • Created a new Amazon Linux 2023 server
    • Installed PostgreSQL on the new server
    • Installed SonarQube using ZIP installation method
    • Pending tasks:
      • Take backup of PostgreSQL database from existing server
      • Restore database backup on new server
2

Hi,

To be clear, SonarQube Server and its database should ideally be on separate hosts. Thus, to “move” SonarQube, you would only install it on the new host and point it at the existing database.

If you really need to move the database as well, and that involves changing the JDBC URL, then you’ll need to get a new license key, although there is a grace period for that built in to current versions.

 
HTH,
Ann

3

Hi,
Currently we have both database and sonarqube server within the same host. Given the dimensions of usage we found that we could have both database and server within the same host. The problem we have is that Amazon Linux 2 is getting to end of life so we can’t have anything over there and we need to move it to Amazon Linux 2023. Isn’t there any guide on taking backup of the database and restore it on the new server? I saw that we can take the db dump and use it to restore in the new server. My request is more on official documentation that describes in detail these sort of migration. Regarding the license issue, we don’t want to affect the existing server during the migration process because with that, it would affect whole development team. We want to assure this migration with 0 impact to the development team.

4

Hi,

This guide would come from your DB vendor.

 
Ann