I updated my sonarqube to 2026.1.0 from 2025.1.4 but due to some issues I rollback to 2025.1.4 again , during rollback we restored dump of 2025.1.4 in db and restarted the service.
But when service up it is showing version 2025.1.4 but when i tried to setup license key ,server ID is showing changed and unable to set license key ,also it is not containing any old data.along with that we also observed that it is moved to MQR mode which we never used earlier,we were using standard mode only.Also we observed that even though data is present at database it is not showing any data (project,users etc) in application.
Could you please assist here . Its little urgent . @ganncamp
Ok I can have look on the DB connection but why it is enabled the MQR mode ? in our infra also we have not made any kind of configuration also as per documentation of sonarqube standard mode is the default mode .
Also As i checked it has connected to H2 database not sure how ? as we havnt changed anything at infra level.I can see sonar.mv.db file in one of the directory of the container.
Because that’s the default in a brand new instance with no history. (I.E. this is another symptom that you’re not pointed at the DB you think you’re pointed at.)
H2 is the default, embedded database provided for initial trials. SonarQube falls back to this when it no external DB is configured.
To “rollback”, you would need to restore the DB backup you made before the upgrade. However, since you never actually “upgraded” your DB (because you didn’t point the updated version to it) then this should simply be a matter of starting the old version back up.
Take a close look at your JDBC configurations in both instances.
Thanks for the information.This issue has been resolved , it was issue with one of the env variables which was changed during upgrade to 2026. and when we rollbacked again it was not taking the new variable as docker image of 2025.* version was using old env var.After changing the var we redeployed and it worked.