Migration from single server (Postgresql) to flexible server without downtime, and to understand if it is possible to do so without changing the server id. Also methods of migration that would allow for this, such as blue/green or other patterns that would allow us to cutover
what have you tried so far to achieve this:
I have migrated in our non-prod environment using the single server to flexible server and then just changed the jdbcurl but this is when i was notified that there was a change to connecrtion string and that the serverid would change.
So was wondering standing up to PG servers attached to separate SQ pods, performing the datamigration but and requesting the updated licenses as i would have the and new serverids at the point and people could continue to run on the existing single server but wasn’t sure if subsequent data migrations would change the server id again and there negate this as a possible method without downtime.
Would also like to understnd how long it takes to turnaround on a lciense file if this methods or no others exists to limit or prevent down time.
Further to my above question, do we know if the data migration from single server to flexible server can be repeated several times (to keep it updated) without affecting the server ID? If so, there is a possibility that I could have a new front end pointed at the backend and if the data mgiration does not change the server id I will have the two required server ids to request a new license while also keeping my developers working and their code being analyzed.
if not, how do we prevent an outage to the sonarqube platform, while moving to a new backend server. I have to move to a new server since the PG server is on Azure and is a single server and is being deprecated in favour of the flexible server. This is the reason by the migration, and trying to do so in a manner that keeps the platform running.
Thank you. I wasn’t sure if it was just the JDBC as the sonar licensing page refers to IP address, connection string and DNS for the database so wasn’t sure if the other items would cause the license to be invalidated, which is part of what I’m trying to understand.
We are already looking into Enterprise because there is a break even point from a cost perspective once you get large enough so, that is something else for us to consider as well.