This article details how to upgrade LuciadFusion to a newer version in a multi-node setup.

Upgrading a multi-node setup

Before upgrading, read through the release notes and look for incompatible changes, fixes, and additions that affect how LuciadFusion interacts with other systems in your setup. Adapt your setup if needed.

We recommend that you try the upgrade in a test environment first, before you perform the upgrade on the instances in a production environment.

Follow these steps to upgrade LuciadFusion in a multi-node setup:

Step 1

Before installing the new version, back up your current configuration and data. See the article Tips on backing up your deployment setup for more information. With a backup, you can revert to the previous version of LuciadFusion if something goes wrong during the upgrade.

Step 2

You must stop all LuciadFusion instances that are part of the same multi-node setup. Because a LuciadFusion upgrade can introduce changes to the database schema, you must upgrade all instances to the newer version at the same time. LuciadFusion doesn’t support running different versions within the same multi-node setup. Also make sure that all jobs have stopped or finished when you stop all LuciadFusion instances, or that only one instance in the multi-node setup has the property enabled. See guideline 2 of the multi-node setup guide for more information about why this is necessary.

Step 3

Upgrade a single instance to the newer version and then start it. You may need to build a new deployment version of LuciadFusion for that. The article Build the LuciadFusion server application for deployment shows you how to do that. When it starts up, this LuciadFusion instance takes care of any changes to the database schema. Once the LuciadFusion instance has finished starting up without any errors, you are clear to proceed.

Step 4

Upgrade all other instances and start them one by one. Once you started up all instances without problems, you have successfully upgraded a multi-node setup.