Migrating to new Server and Database

We are in the planning process of moving our on-prem TeamCity Server and external on-prem MSSQL TeamCity database to Azure.  I have read a similar post and read the documentation.

I would just like some input on the migration order.  It appears moving the database before the server is the suggested route? 

Also, are there any benefits of using the maintaindb utility to migrate the database, over restoring a db backup on the new database server?

0
7 comments

Hi, are you also planning to move your TeamCity Data Directory and Artifact Storage to Azure?

0

Yes.  We will be migrating everything.

0

Eric Borchardt We currently house our artifacts on the server's disk.  We are planning on replicating the data directory and home directory to the new host in Azure.

Is there an opinion on the database migration?  Maintaindb utility vs restoring from a MSSQL backup?

0

I would just like some input on the migration order.  It appears moving the database before the server is the suggested route? 

I'm not sure where you're seeing this as the suggested order, but it is important that both the data directory and database are kept in sync and need to be migrated at the same time. Both of these items must be migrated prior to starting your new TeamCity instance in order to ensure a successful transfer. Please see our suggested steps here: Create a Copy of TeamCity Server with All Data

Is there an opinion on the database migration?  Maintaindb utility vs restoring from a MSSQL backup?

Since it sounds like you're planning a manual migration of the data directory, it really makes no difference whether you use the maintaindb script or your own MSSQL tools to perform the database migration. My personal recommendation would be to use whatever tool you're most comfortable with. Either way, be sure to configure your new MSSQL database as described in Database Specific Steps for MSSQL.

There is another option for your migration, which would be to restore a backup of your current TeamCity to your new instance. This process would include the migration of both the data directory and the database. It would still be necessary to move the artifacts manually, as they are not included in the scope of TeamCity backups. You can see what is included and not included in TeamCity backups in our documentation in TeamCity Data Backup.

0

Eric Borchardt I was referring to this post.  https://teamcity-support.jetbrains.com/hc/en-us/community/posts/360003574200-migrating-to-a-new-server-and-new-database

So we were thinking of migrating the database first.  Configure the existing TeamCity server/data directory to point to the new database, then move the server/data directory to the new host, which will be pointing to the new database.

0

That post is quite dated and refers to old documentation. You could look at Move TeamCity Installation to a New Machine in our latest documentation, but really what you are describing sounds more in line with the process in Create a Server Copy with All Data. This is because the steps for Moving TeamCity Installation to a New Machine are intended for cases where the existing data directory and database will not be moved/migrated. Whereas, the process for Create a Server Copy with All Data includes the steps for moving/migrating the existing data directory, database, artifacts, etc...

0

Awesome.  Yes.  The Server Copy looks more inline to what we will be doing.  We do need to keep all the data from the original installation on the new server.  TeamCity is used heavily in our organization and the amount of projects is large.

Thanks for the information.

0

Please sign in to leave a comment.