Forum SquashTM

I hope this message finds you well.

I'm currently looking for a way to migrate our Squash TM data from version 2.1 to version 11.0.0, ideally without having to deploy an instance for each intermediate version, as this would be very time-consuming.

The current database engine is MariaDB 10.5.29-MariaDB-0+deb11u1

The target database version is 11.8.2

The existing Squash TM and Maria DB instances are a bare-metal deployment

The new instance is a Dockerized setup.

I'm looking for a quick and efficient solution, as the tool is heavily used during office hours the migration window is limited to 6 pm to 7 am to avoid impacting teams.

I’ve read the official documentation as well as some related articles. However, the documentation only covers upgrades of one or two major versions at a time and doesn't provide guidance for migrating across multiple major versions like from 2.1 to 11.0.0.

If anyone has experience with this type of migration or can suggest a more efficient solution, your help would be greatly appreciated.

Kind regards, Beladric.

Hello,

Here is what you can do to ensure a smooth and safe upgrade from Squash v2.1 to Squash v11.0.0:

The most important step is to create a full backup (dump) of your current instance. This will allow you to restore the original state in case any of the upgrade scripts fail or do not execute as expected : https://tm-en.doc.squashtest.com/latest ... e-database

Secondly, we strongly recommend performing this upgrade in a pre-production environment. This is just as crucial as the backup, especially given the significant version gap. It also gives you the opportunity to validate the overall behavior of the instance in v11 before applying the same process to your production environment.

With that in mind, here are the steps to follow:
1) Update MariaDB

You will need to update Maria DB to version 10.7 or higher before starting the upgrade process and have at least Java version 21: https://tm-en.doc.squashtest.com/latest ... requisites

2) Database upgrade

You must manually execute all database upgrade scripts sequentially up to version 8.1, using a database user with full administrative privileges.

In your case, this means running the following script: At this point, you can either continue to run the scripts manually or delegate the scripting process to an automated system: https://tm-en.doc.squashtest.com/latest ... ersion-900

Before continuing with the upgrade and as a mariadb user, you must run the commands described here: https://tm-en.doc.squashtest.com/latest ... -10.x.html for sequence management.

At this stage, you will still have the following scripts left:
When running the scripts manually, always be vigilant: if an error is detected, do not continue with the upgrade under any circumstances. Instead, start again from the saved dump: https://tm-en.doc.squashtest.com/latest ... sions.html

Also pay attention to the available disk space; you will need to check that it is no more than 40% full so that the v11 script runs correctly (this point will be added to the v11 release note shortly, as the version has not yet been officially shared).

3. Upgrading the application

Once your database is running version v11.0.0, you will need to download the latest version of the application, as well as the v11 plugins (and only those in this version, as a number of plugins present in v2.X have since been integrated into the core) and transfer your existing configuration to the squash.tm.cfg.properties file.
Here is the link to the Docker documentation: https://tm-en.doc.squashtest.com/latest ... stall.html + https://tm-en.doc.squashtest.com/latest ... on-upgrade

Regards,
Xavier, Squash Support Team

Greetings,

I hope this message finds you well.

I would like to thank you for the quick response. I applied the process you described and everything is working well. I just want to highlight an issue I'm facing during the migration. The scripts are located in the squash container, but to use them we need to have the container running. However, in my case, if I apply migration scripts from the squash container while it is running, it causes SQL errors, maybe because the squash container tries to perform operations in parallel. So the solution I found is to get the scripts from the squash container, push them to the MariaDB container, stop the squash container, and only after that apply the migration scripts.

Once again, many thanks for your help.

Kind regards,
Bealdric

I want to thank you for responding so quickly. I used the procedure you outlined, and everything is operating smoothly. I just wanted to draw attention to a problem I'm having with the migration. https://tm-en.doc.squashtest.com/latest ... e-database