Hi Kristian, Hi Artur,
I would like to make a contribution here so that other people can learn from my experiences.
The original upgrade procedure via upgrade.sh has not gone so smoothly for me at least twice in the past and needed to be improved. In a production system with growing user numbers, I became more cautious and we stayed at 20.10.8 for a long time.
I would have liked to have seen the advice mentioned by Artur to do the installations side by side in the home directory earlier, but it has now motivated us to upgrade to 20.10.11.1 by installing them in parallel in /home/openbis/openbis-20.10.11.1, which worked perfectly.
We saved the list of files from the neighboring thread (How to upgrade a running installation?) and copied them into the new installation.
Unfortunately, it was only a few days later that we noticed that the inline images in the MULTILINE_VARCHAR fields were no longer being loaded.
Other than the data in the DataStore those are stored in the application folder /home/openbis/openbis-20.10.11.1/data/file-server and therefore have to be moved alongside the afromentioned files.
If there is a better way to handle the storage of inline images, I would be glad to have that mentioned elsewhere.
Greetings,
Volker