Upgrade version

Overview

The current topic addresses the upgrade of installations already attached to an external database.

It is important to note that once you have linked a TSS installation to a database server, you will remain linked to this particular database server instance in the future upgrade operations.  If you are looking to upgrade a current TSS and target a different database server for your upgraded version than the one linked to your current TSS, please jump directly to the last section.

The upgrade process must begin by the upgrade of your primary node, as the database will be copied and upgraded only from this node. Then, the upgrade can be done on secondary nodes in any order.

Upgrade on primary node (redundancy identity = 1)

Firmware upload

Once you have selected the TSS version you want to upgrade, you will be asked to upload the new TSS firmware to which you want to upgrade. The "Use external database" checkbox will only be checked if the version you decide to upgrade has been linked to an external database.

Database connection

There is no possibility to change the database connection details during the upgrade process. This information, database server and credentials, will be assumed the same as the the version you wish to upgrade.

Database compatibility verification and initialization options

Once your firmware is uploaded, the upgrade process will check the connectivity with the database server. Two main options are available, depending whether you want the database user attempting to create the destination database for the upgraded TSS version or not.

1. There is no target database (following the database naming convention described here)  on the database server: The upgrade process will attempt to create the target database and to copy the original data into it before applying the necessary migration operations. This scenario requires the database user to have been granted privileges for creating database on this database server.

2. There is an empty target database on the database server. The upgrade process will only copy the original data into it, and apply the migrations operations on it. This scenario does not require the database user to be able to create database on this database server.

Upgrade on secondary node (redundancy identity from 2 to 6)

Firmware upload

The upgrade process on secondary nodes only requires to upload a TSS firmware version, matching the one deployed on your primary node.

Database connection

There is no possibility to change the database connection details during the upgrade process. This information, database server and credentials, will be assumed the same as the the version you wish to upgrade.

Database compatibility verification

The upgrade of a secondary node does not attempt to apply any migration. Nevertheless, the upgrade process will check that the target database exists and contains a compatible schema.

Upgrading a primary node and targeting a new database server instance

Some administrators may want, at some point, want to deploy an upgraded version of TSS and target a different database server instance.

We describe here a short scenario of how it could be achieved:

Given a TSS running a version A, attached to database server DS1, we want to deploy a version of TSS B (B >= A), attached to database server DS2:

1. An administrator proceeds to backup the database attached to the TSS A on DS1.

2. He then restores this backup on DS2 and ensures to give a database name compatible for the future TSS B.

3. The administrator can now start an installation of a new TSS firmware B and target the external database DS2

The installation process will detect that the target database is running with a schema in version A and upgrade it to the version B before finalizing this new deployment.