TeamCity provides several ways to back up its data:
maintainDBcommand-line tool: Same as via the UI. To include all data, use the tool when the server is stopped.
Restoring data from backup is performed using the
We strongly urge you to make the backup of TeamCity data before upgrading. Note that TeamCity server does not support downgrading.
TeamCity allows backing up the following data:
<TeamCity Data Directory>/libdirectory)
The data to be backed up can be configured using the backup scope options when using the TeamCity Web UI or via additional parameters for the maintainDB command-line tool.
The following data is not included into backup:
build artifacts (because of their size). These include explicit build artifacts and internal artifacts storing coverage report, finish build parameters, settings digest, etc. If you need the build artifacts, please also backup content of artifacts directories manually.
<TeamCity Home>, including used server port number which are stored in
<TeamCity Data Directory>that do not fall into previously mentioned items.
The recommended approach is either to perform the backup process described under Manual Backup and Restore or run a backup from the web UI regularly (e.g. automated via REST API) with the "Basic" level - this will ensure backing up all important data except build artifacts and build logs.
Build artifacts and logs (if necessary) can be backed up manually by copying files under
.BuildServer/system/artifacts and, prior to TeamCity 9.0,
.BuildServer/system/messages. See TeamCity Data Directory#artifacts for details. If logs are selected for backup, TeamCity will search for them in all artifact directories currently specified on the server.
Note that for large production TeamCity installations, exporting and importing of data from/to the database may not be an optimal solution and maintaining database backup via replication might be a better option; e.g. see the corresponding documentation for MySQL database.
Installation and Upgrade: Upgrade