The second, and easier mechanism is to use the TeamCity Admin UI. sh file and is quite simple to use, if you want to back up everything (configuration, database, build logs, personal changes) you would run it using the following switches:īy default the backup will be created in the \backup directory with the following file name: TeamCity_Backup_.zip, where the timestamp is in the YYYYMMDD_HHMMSS format. The tool can be found in \bin directory and exists in the form of a. There are two main mechanisms for backing up the TeamCity database the first is using the maintainDB tool – this gives you command line control of the back up process. To perform a migration you need to backup (and restore) both of these data repositories. In order to perform a migration, you first need to understand how TeamCity is architected, especially how TeamCity stores its data in two separate repositories the Data Directory for server settings, build artefacts, logs & configuration, based on the file system and a second, containing build information, configuration & statistics which is stored in a database (HSQLDB, Microsoft SQL Server, MYSQL, PostgreSQL, Oracle). This step by step guide is going to cover how to migrate to a new Windows Server instance running Microsoft SQL Server.
Luckily, due to the way that TeamCity has been designed, all of these scenarios are supported.
If you've been using TeamCity for a number of years, there will come a time where the server it's running on will reach its end of life and your TeamCity instance will need to be moved to a fresh server.Īs part of this migration process, you may decide to change OS from Linux to Windows or persistence mechanism from the internal HQL data store, or an Oracle Database to SQL Server or MySQL. By Howard van Rooijen Co-Founder 30th July 2013
0 kommentar(er)
