EasyUC
English
Aurora

Choose appearance

Software, updates and licence files are available in the customer portal. Go to downloads

Installing updates

How an EasyUC update runs from 4.8.7 on, how the services behave meanwhile and the way back.

Applies to: EasyUC 4.8.7 Last updated: October 2026

Before the update

  • Check the requirements for 4.8.7: EasyUC 4.8.5 or later, EasyUC Manager 1.15.0 or later, K3s 1.34.0 or later, all nodes amd64 and in Ready state. Bring older systems to 4.8.5 first.
  • Have the package file easyuc-<version>-amd64.eucpkg ready and compare the checksum of the download.
  • Check the free disk space on all nodes. The Manager shows the limit after the upload.
  • Plan a maintenance window. The whole application is unavailable for 5 to 10 minutes during the installation. Allow about 1 hour 45 minutes for the failure case.
  • Recommended: create your own full backup and a VM snapshot, see Backup and restore.

Important

The Manager backs up the database itself before the installation. This backup is used for the reset to the previous version and does not appear in your list of backups. It does not replace a backup of your own.

Procedure

  1. Upload the package file

    Open the EasyUC-Update page in the Manager and drop the file onto the area. An interrupted upload can be resumed.

  2. Wait for check and preparation

    The Manager checks signature and content and shows the version, the release notes and the state of the nodes. It then distributes the image to all nodes in the background. This takes about 15 minutes per node. EasyUC keeps running normally meanwhile.

  3. Start the installation

    Choose Installieren…, enter your Manager password and confirm with Jetzt installieren.

  4. Installation runs

    The Manager backs up the database, switches to the new version, runs the database migrations, restarts the services and checks each service individually. This takes 10 to 20 minutes.

  5. Check the status

    Under Versionen you see the installed version and the previous one you can reset to.

What happens internally

The package file contains a single image for all application components and carries a signature. The Manager does not accept packages without a valid signature. The data services MariaDB, Elasticsearch and RabbitMQ are not replaced by a normal EasyUC update.

How an EasyUC update runs Five steps: upload the signed package file, the Manager checks it and distributes the image to all nodes, it backs up the database, the initialisation job runs the migrations, all services restart together and are unavailable for 5 to 10 minutes. MariaDB, Elasticsearch and RabbitMQ are not replaced. 1 Package signed file (.eucpkg) 2 Preparation check, distribution to all nodes 3 Backup database, before the switch 4 Init job migrations, search indexes 5 Services restart together 5–10 min downtime MariaDB, Elasticsearch and RabbitMQ are not replaced by a normal update.
How an update runs from 4.8.7 on. The data services are not replaced.

Behaviour during the update

Every service runs as one instance, and all services restart together. From the switch until all services are ready again, the whole EasyUC application is unavailable. Expect 5 to 10 minutes.

acd-media, teams-sbc and teams-ps restart once with 4.8.7. Active calls via Teams and ACD are disconnected. With later updates these services only restart when their content has changed.

If the installation fails, the automatic reset extends the interruption. As a guideline for this case, allow about 1 hour 45 minutes.

Warning

Plan updates in a maintenance window that also covers the failure case. Active calls via Teams and ACD are disconnected, and interfaces and services are unavailable during this time.

Going back to the previous version

The Manager keeps the images of the last two versions on all nodes. A reset always includes the database, to the state immediately before the switch.

  • Automatic: if the installation fails during migration, restart or check, the Manager resets program and database to the previous version. Under Versionen you can then start a new attempt.
  • Manual: after a successful installation you reset to the previous version under Versionen, as long as its images are on all nodes. The dialog names the data state that is restored. The Manager takes a safety copy first.
  • Data written to the database after the backup is lost by the reset. The Manager does not reset search indexes, files on the application volume or the other settings of the installation.
  • If the reset fails as well, EasyUC stays suspended until the state has been clarified. In that case contact our support. A VM snapshot remains useful as an additional way back.

Updating the Manager itself

The Manager is updated separately from EasyUC. EasyUC 4.8.7 requires Manager 1.15.0 or later. Once 4.8.7 is installed, you must not take the Manager back to a version below 1.15.0. Older Managers do not know the shared image and would make the running installation unusable.

You receive the Manager update and its instructions with the release. When it is applied, the following happens:

  1. The Manager's custom resource definition is updated.

  2. The Manager restarts.

Updates without internet access

The package file contains everything the update needs. You upload it to the Manager in the browser; access to registry.easy-uc.com is not needed. The procedure is the same with and without internet access.

The package is a full package of about 1.6 to 2.2 GB. The Manager accepts packages up to 4 GiB.