Installation, updates & backup
Rolling EasyUC back to the previous version
Automatic and manual rollback after an EasyUC update, with scope and limits.
In EasyUC: Manager → EasyUC-Update → Versionen → Auf <version> zurücksetzen
What it is for
The Manager keeps the images of the last two versions on all nodes. This lets it return to the previous version after an update. That happens automatically when an installation fails after the switch, and manually on request in the Versionen area.
If the update brought database migrations, the database is always rolled back as well, to the state immediately before the switch. Before a manual rollback the Manager creates a safety copy of the current state. Version 4.8.7 brings 13 new database migrations; a rollback from 4.8.7 therefore includes the database.
Prerequisites
- A version installed through EasyUC-Update. Installations made with the former YAML path do not appear under Versionen.
- The images of the previous version are present on all nodes. If they are missing, the page shows "Zurücksetzen nicht möglich: …".
- The modules have not been extended since the update. The previous version has no images for modules activated later; rollback is then blocked.
- A login to the Manager and the Manager password.
- A maintenance window. EasyUC is suspended during the rollback.
Step by step: roll back manually
Fields and options
| Field / action | Meaning and use |
|---|---|
| Nur die Programmversion | Data is kept. Only selectable when the update brought no database migrations. All services restart. |
| Programmversion und Datenbank | The database goes back to the state immediately before the installation. Changes since the update are lost. |
| Restored | MariaDB with both databases including licence data, and the image and version entries of the EasyUC configuration. |
| Not rolled back | Elasticsearch indices, RabbitMQ queues, files on the volume of the admin API and the remaining settings (modules, presence, backup, replicas). |
| Feld / beim Update / jetzt (bleibt) | Table of settings that were changed since the update and are kept during the rollback. |
| Stand vor dem Zurücksetzen | Name of the safety copy the Manager creates before a manual rollback. |
| Erneut installieren | Starts a new installation attempt with the existing package after an update was rolled back. |
| Status in the Versionen list | wird installiert, installiert, zurückgenommen, fehlgeschlagen, abgelöst. |
Check the result and troubleshoot
- The previous version is shown again at the top right under Installiert; the Versionen list shows the update as "zurückgenommen".
- Automatic rollback: the run ends with "Installation fehlgeschlagen – vorheriger Stand wiederhergestellt." Below it, "Automatisches Zurücksetzen (Code und Datenbank)" is shown with the reason.
- "Zurücksetzen nicht möglich: …": the page names the reason, for example missing images of the previous version.
- "Die EasyUC-Module wurden seit dem Update geändert. … ein Zurücksetzen ist deshalb gesperrt.": restore the module selection from the time of the update or contact support.
- "Fehlgeschlagen – Eingriff nötig." during a rollback with database: EasyUC stays suspended until the state has been clarified. It does not restart automatically on half-restored data. Contact EasyUC support and state the backup names shown.
- The backups of the EasyUC update are internal slots. The restore area does not offer them. Regular backups are still found on the Sicherung page.
- After 4.8.7 has been installed, the Manager must not be rolled back to a version below 1.15.0. Older Managers do not know the single image.