Moving to a new server with database upgrade

Hi, 

we plan to move our TeamCity 2025.07 Server and Worker virtual machines (Windows Server) to another data center and updated operating system (Windows Server 2025). Currently TeamCity uses a Postgresql 10.1.-3 database on the same machine as the TeamCity server.

I am wondering if we should upgrade to the current Postgresql 17.5-3 during this process. Meaning to install Postgresql 17.5-3 and TeamCity 2025.07 on the new server an restore a backup of the old server.

Would you recommend this upgrade? And how should it be done in a safe way?

Kind Regards,
Ralph

0
7 comments

Hi Ralph,

TeamCity 2025.07 supports PostgreSQL 9.6 or later (Supported Databases), so there shouldn't be any problem with the upgrade to the mentioned version. 

Please note that it is not recommended to have the external database running on the same machine as the TeamCity server:
https://www.jetbrains.com/help/teamcity/system-requirements.html#Estimating+External+Database+Capacity

The migration to a different version of PostgreSQL can be done using the maintaindb script included with TeamCity On-Premise, using one of the mentioned approaches in this section of the documentation: Migrating to External Database.

You can follow the following steps if you want to use the backup and restore method:

  1. Prepare your new PostgreSQL database according to Set Up External Database - PostgreSQL
  2. Stop your TeamCity server service and make a backup using the command line method
  3. Restore your backup to the new database, following Restoring TeamCity Database Only
  4. Configure the <teamcity data directory>/config/database.properties file for the new database (Database Properties File)
  5. Start the TeamCity server service and confirm the new database is being used in teamcity-server.log

 

0

Hi Guilherme,

thanks for your detailed and helpful response. I will try that. 

We have been running the DB and the TeamCity Server on the same machine for about 8 years now without any problems. We are a team of about 10 developers running nightly builds when changes are detected and manually triggered builds only when needed.

Kind regards,
Ralph

0
Hi Ralph,
For your workload it is not problematic to have DB and TeamCity on the same machine, so we understand you don't really need to make any changes here. Please let us know how the database upgrade goes and if you need any further assistance from our side.

Regards,

Guilherme
0

Hi Guilherme,

we are just in the migration process facing a serious problem.

The new PostgreSQL server uses “scram-sha-256” password encryption and after restoring the Teamcity backup TeamCity can't connect to the DB. I think it still uses "md5". Our out PostgreSQL server used “md5”.
How can I solve this?

Regards,
Ralph

0

Meanwhile we have manged to configure PostgreSQL to use “md5” authentication and got TeamCity Server working.

Interesting still is, how PostgreSQL DB access for TeamCity can be configured to authenticate using "scram-sha-256".

Regards,
Ralph

0

Hi Ralph!

Did you upgrade theJDBC driver as well? The "Authentication type 10 is not supported" seems to come from a mismatch in the algorithm used to encrypt the password in PostgreSQL and the one the JDBC driver uses to connect to the database. In any case, we are glad you found a solution for it.
 
Please check also the following section of our documentation on PostgreSQL configuration, it might be useful for you if you have not seen it yet:
https://www.jetbrains.com/help/teamcity/how-to.html#Configure+Newly+Installed+PostgreSQL+Server

 

Thanks,

Guilherme

0

Yes, I downloaded version 42.7.7 (11 June 2025) from https://jdbc.postgresql.org/. For now it works.

Thanks,
Ralph

0

Please sign in to leave a comment.