Creating Backup from TeamCity Web UI

Backup file

Specify the name for the backup file, the extention (.zip) will be added automatically. By default, TeamCity will store the backup file in the <TeamCity Data Directory>/backup directory. For security reasons, you cannot explicitly change this path in the UI. To modify this setting, specify an absolute or relative path (the path should be relative to TeamCity Data Directory) in the <TeamCity Data Directory>/config/backup-config.xml file. For example:

<backup-settings>
  ...
  <general>
    <backup-dir path="C:/TC-Backups"/>
  </general>
  ...
</backup-settings>

add timestamp suffix

Check this option to automatically add time stamp suffix to the specified filename. This may be useful to differentiate your backup files, if you don't clean up old backups.

note

• If the directory where backup files are stored already contains a file with the name specified above, TeamCity won't run backup: you will need either to specify another name, or enable time stamp suffix option, which allows you to avoid this.

• Time stamp suffix has a specific format: sorting backup files alphabetically will also sort them chronologically.

Backup scope

Specify what kind of data you want to back up. The contents of the backup file depending on the scope is described right in the UI when you select a scope. Note that the size of the backup file and the time the backup process will take depends on the scope you select.

To reduce the resulting file size and the time spent on the backup, select the "basic" scope, which includes server settings, projects and builds configurations, plugins and database. However, you'll be able to restore only the settings which were backed up.

For the full backup suitable for most of the needs, it is recommended to use the Custom scope with all the items selected except for "build logs" and then backup the <TeamCity Data Directory>/system/artifacts location as a usual file system.

Build artifacts are not included into the backup due to their size. It is recommended to either back up the artifacts directories separately or use a redundant storage for the artifacts. Build logs are stored as a part of build artifacts, so there is no need to back up the build logs if you implement a separate backup of the artifacts locations.